Chykalophia Docs

A plain-English explanation of what page speed means, how it is measured, and why different tools give different scores.

"Page speed" sounds simple — it is how fast your page loads. But in practice it is more nuanced than a single number. This guide breaks down what speed actually means and why different tools measure it differently.

Quick summary

Page speed is not one number — it is several measurements that together describe how fast your page feels to a visitor. The most important measurements are about when content first appears, when it becomes usable, and whether it moves around unexpectedly.

What "loading" actually means

When a visitor opens your website, several things happen in a sequence:

Their browser sends a request to your server
The server sends back the HTML file (the page's structure)
The browser starts reading that file and discovers it needs images, stylesheets, and scripts
The browser fetches all of those files
The browser puts everything together and displays the final page

"Page speed" describes how long different stages of this process take. A page can feel fast even if it takes three seconds to fully finish loading — as long as the most important content appears quickly.

The key speed measurements

Rather than one score, modern speed tools measure several things:

Measurement	What it means	Good target
First Contentful Paint (FCP)	When the first text or image appears	1.8 seconds or less
Largest Contentful Paint (LCP)	When the main content loads	2.5 seconds or less
Interaction to Next Paint (INP)	How quickly the page responds to clicks/taps	200 milliseconds or less
Cumulative Layout Shift (CLS)	How much the layout jumps around as it loads	0.1 or less
Time to First Byte (TTFB)	How long before your browser receives anything	0.8 seconds or less

Those are Google's own "good" thresholds, and the boundary counts as good — 2.5 seconds exactly is still a pass. TTFB is the odd one out: PageSpeed Insights reports it as an experimental measurement, and it is not a Core Web Vital, so treat it as a rough guide rather than a target you have to hit.

The three most important — LCP, INP, and CLS — are Google's Core Web Vitals. Google says its ranking systems do use them. There is no single "page experience" score to pass or fail, though, and good numbers on their own do not guarantee a top position in search results.

Why different tools give different scores

You may have checked your speed with two different tools and gotten very different results. This is normal.

Different tools measure speed in different ways:

Lab tests (like Lighthouse) load your page once in a simulated environment. They are consistent and good for debugging, but a single simulated load may not match what real visitors get.
Field data (like the Chrome User Experience Report) collects real measurements from real visitors. This reflects actual experience but varies by location, device, and connection.

Scores are also relative to other sites. Lighthouse turns each raw measurement into a score by comparing it against real-world performance data from the HTTP Archive, so what counts as "fast" shifts as the web gets faster. Google has changed how the individual measurements are weighted over the years, too.

Which tool should you use?

Google PageSpeed Insights is a good starting point — it reports both lab and field data for the same page, including the Core Web Vitals that Google's ranking systems use. See How to measure your site's speed for a full guide.

The difference between server speed and page speed

These are related but not the same thing:

Server speed (Time to First Byte) is how fast your hosting sends the first response. This is largely about your hosting environment.

Page speed is the full experience, including all the images, scripts, fonts, and other files the page needs. You can have a fast server but a slow page if the page is poorly optimized.

Why "100/100" is not always the goal

Tools like PageSpeed Insights give a score out of 100. A perfect score is impressive — but it is not the only goal, and chasing a perfect score sometimes means making compromises (like removing features your visitors value). Google's own Lighthouse documentation calls a perfect 100 "extremely challenging to achieve and not expected", and treats 90 and above as good.

A more useful question: "Are my Core Web Vitals in the green zone?" and "Is my site faster than my main competitors?" Read more in Performance: realistic expectations.

Common questions

Why does my site seem fast to me but scores poorly?

Your browser saves (caches) your site locally, so your own repeat visits are much faster. The simulated test does not have that head start. It also deliberately uses modest equipment: for its mobile score, PageSpeed Insights simulates a mid-tier phone on a mobile network, not a fast laptop on office broadband.

Does page speed include video?

Yes. A video set to play automatically (autoplay) adds a large download to the page. Embedded players from YouTube or Vimeo are not free either: by default the embed loads its player as soon as the page loads, not when someone clicks play. Google's own example puts a YouTube player at around 540 KB, against 3 KB for a clickable placeholder image that only swaps in the real player on interaction. Talk to us if you want video on your site and are concerned about speed.

What is a 'render-blocking' resource?

A render-blocking resource is a file — a CSS stylesheet or a JavaScript file — that the browser must download and process before it can show anything to the visitor. Think of it as a door the browser must open before drawing the page. Reducing render-blocking resources is one of the more effective speed improvements, and speed tools flag it specifically.

Need a hand?

If you're stuck, email support@chykalophia.com and we'll help. Include your website address and a screenshot if you can.

What is page speed?