Page speed
What is page speed?
Page speed is the time it takes for a web page to load its content and respond to a visitor. It is not a single number: a page can show its first image in one second yet stay unresponsive for three more. That is why speed is described through several user-centred metrics rather than one stopwatch value.
It matters for three reasons. Visitors leave slow pages, search engines treat speed as a ranking signal through Core Web Vitals, and every extra second of delay lowers conversion rates, especially on mobile connections.
How page speed is measured
Modern tools measure what the visitor actually experiences. The main metrics are:
- TTFB (Time to First Byte): how long the server takes to start answering. Good values are under 800 ms.
- LCP (Largest Contentful Paint): when the main content becomes visible. Target: 2.5 s or less.
- INP (Interaction to Next Paint): how fast the page reacts to clicks and taps. Target: 200 ms or less.
- CLS (Cumulative Layout Shift): how much the layout jumps while loading. Target: 0.1 or less.
Lab tools such as Lighthouse give a controlled test, while field data from the Chrome UX Report and Search Console shows what real users get on real devices. Field data is what Google uses for ranking.
What slows a page down
Most slow pages share the same causes: oversized images, too many third-party scripts (chat widgets, trackers, tag managers), render-blocking CSS and JavaScript, unoptimised web fonts, heavy sliders or videos above the fold, and a slow or distant server. Each element adds requests and bytes the browser must download and process before showing the page.
Mobile makes everything worse. A page that feels instant on a fibre-connected laptop can take six seconds on a mid-range phone with a weak signal, so testing must always include mobile conditions.
Page speed vs site speed vs perceived performance
| Concept | What it covers | How it is measured |
|---|---|---|
| Page speed | One URL: load and interactivity | LCP, INP, CLS, TTFB per page |
| Site speed | The average across many pages | Aggregated field data, site-wide reports |
| Perceived performance | How fast the page feels to a visitor | Visual progress, skeletons, instant feedback |
All three matter. A page can be technically fast but feel slow if nothing appears until everything is ready, and a page that shows content progressively can feel faster than its raw numbers suggest.
How to improve page speed
Start with the biggest wins, in this order:
- Compress images and serve modern formats such as WebP or AVIF, with correct dimensions.
- Use lazy loading for images and videos below the fold, but never for the main hero image.
- Minify and defer CSS and JavaScript, and remove unused code.
- Limit fonts to the weights you really use and preload the critical ones.
- Serve assets through a CDN and set sensible browser cache headers.
- Audit third-party scripts and remove any that do not pay for themselves.
Measure before and after each change. Optimising blindly often moves the problem rather than solving it.
Common mistakes
Teams often chase a perfect Lighthouse score instead of real user data, lazy-load the hero image (which delays LCP), stack several analytics and chat tools, or ignore mobile. Another frequent error is optimising the homepage only, while the templates that bring organic traffic, such as blog posts and landing pages, stay heavy.
Page speed at BeBranded
We design and build websites with speed as a requirement from the start: lightweight layouts, optimised media, clean code and a CDN-backed hosting setup. Our website service includes performance checks against Core Web Vitals before launch, so your site loads fast on mobile and keeps its SEO potential.