Book a call Free rebuild

Speed Index

November 8, 2022 Updated November 16, 2026 2 min read

Performance glossarySpeed Index is a lab metric for how quickly the visible content of a page fills in while it loads. Lower is better.

Speed Index measures how quickly the visible part of a page fills in while it loads. Rather than marking a single moment, it looks at the whole loading sequence: a page that shows most of its content early scores better than one that stays blank and then appears all at once, even if both finish at the same time. Lower is better, and it is expressed in seconds or milliseconds.

The metric was introduced by WebPageTest, and it is one of the five metrics in the Lighthouse performance score shown in PageSpeed Insights.

How it is calculated

The test tool records a video of the page loading and measures, frame by frame, how visually complete the viewport is compared with the final result. Plotting completeness over time gives a curve that rises from 0 to 100 percent. Speed Index is the area above that curve: the longer the page spends looking incomplete, the larger the area and the higher the score.

Because it needs a recording of the page, Speed Index is a lab metric. It is measured in tools such as Lighthouse and WebPageTest, not collected from real visitors, and it is not a Core Web Vital.

What it is good for

Speed Index sums up perceived loading speed in one number, which makes it useful for comparing versions of a page, or competing pages, under identical test conditions. It overlaps with First Contentful Paint and Largest Contentful Paint, which are now the main loading metrics, and adds a view of how progressively the page renders between them.

It has limits. It treats all pixels equally, so a large block of background color filling in early can flatter it, and carousels or animations that keep changing can blur the point at which the page counts as visually complete.

How to improve it

  • Respond quickly from the server, with page caching, so rendering can start sooner.
  • Remove render-blocking CSS and JavaScript from the head: defer scripts, and load only the CSS needed for the first screen up front.
  • Deliver the main content in the HTML instead of building it with JavaScript after the page loads.
  • Use font-display: swap so text appears in a fallback font while web fonts load.
  • Optimize and correctly size images near the top of the page, and do not lazy-load them.
  • Avoid sliders and animated intros that hold back the first meaningful view.

Source: Chrome for Developers: Speed Index.

WP Services

WordPress services at revolutionary pricing.

Productized WordPress services, from builds to care, delivered by Seahawk and tracked in one app. For the WordPress lovers.