Error Codes Wiki

HTTP 103 Early Hints — Preloading and Link Header Configuration Issues

Informational1xx informational

About HTTP 103 Early Hints

Troubleshoot HTTP 103 Early Hints implementation errors including browser compatibility issues, incorrect Link headers, and preload failures. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: HTTP 103 Early Hints allows servers to send preload hints before the final response is ready. The server sends 103 with Link headers pointing to critical resources (CSS, JS, fonts). Browsers can start fetching these resources while waiting for the full response. Not all browsers support 103 Early Hints — check compatibility before relying on it. Early Hints are sent as an informational response before the final 200 response. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Browser not supporting HTTP 103 Early Hints (Safari, older browsers). Link headers in 103 response not matching the resources actually used in the final response. Proxy or CDN stripping the 103 intermediate response. Preloaded resources served with mismatched CORS or content-type causing browser rejection. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Verify browser support: Chrome 103+ and Firefox 102+ support Early Hints, Safari does not yet. Send 103 with Link headers for critical render-blocking resources: Link: </style.css>; rel=preload; as=style. Ensure preloaded resources match the actual resources in the HTML — mismatches cause double downloads. Configure your CDN to forward 103 responses: Cloudflare supports Early Hints natively. Use the Performance API to measure if Early Hints improve your Largest Contentful Paint (LCP). If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our HTTP Status Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.

Quick Answer

What is the benefit of HTTP 103 Early Hints?

Early Hints allow browsers to start loading CSS, fonts, and scripts before the HTML response arrives. This can improve LCP by 100-500ms, especially for pages with slow server-side rendering.

Overview

Troubleshoot HTTP 103 Early Hints implementation errors including browser compatibility issues, incorrect Link headers, and preload failures.

Key Details

  • HTTP 103 Early Hints allows servers to send preload hints before the final response is ready
  • The server sends 103 with Link headers pointing to critical resources (CSS, JS, fonts)
  • Browsers can start fetching these resources while waiting for the full response
  • Not all browsers support 103 Early Hints — check compatibility before relying on it
  • Early Hints are sent as an informational response before the final 200 response

Common Causes

  • Browser not supporting HTTP 103 Early Hints (Safari, older browsers)
  • Link headers in 103 response not matching the resources actually used in the final response
  • Proxy or CDN stripping the 103 intermediate response
  • Preloaded resources served with mismatched CORS or content-type causing browser rejection

Steps

  1. 1Verify browser support: Chrome 103+ and Firefox 102+ support Early Hints, Safari does not yet
  2. 2Send 103 with Link headers for critical render-blocking resources: Link: </style.css>; rel=preload; as=style
  3. 3Ensure preloaded resources match the actual resources in the HTML — mismatches cause double downloads
  4. 4Configure your CDN to forward 103 responses: Cloudflare supports Early Hints natively
  5. 5Use the Performance API to measure if Early Hints improve your Largest Contentful Paint (LCP)

Tags

early-hints103preloadperformancelink-header

More in 1xx Informational

Frequently Asked Questions

Early Hints allow browsers to start loading CSS, fonts, and scripts before the HTML response arrives. This can improve LCP by 100-500ms, especially for pages with slow server-side rendering.