PageSpeed Insights hands you a score and a long list. Most of the list is noise. Three measures, called the Core Web Vitals, describe what your customer feels, and they are where to start.
Largest Contentful Paint: when does it look ready?
This is the time until the biggest thing on the screen, usually a hero image or a heading, has appeared. Google treats up to 2.5 seconds as good. If it is slow, the customer is looking at a blank or half-built page.
Fix it by making the main image smaller and loading it first, not last, and by removing scripts that block the page from drawing.
Interaction to Next Paint: does it respond?
This measures how quickly the page reacts when someone taps. Under 200 milliseconds feels instant. Over half a second feels broken. The usual cause is too much JavaScript running at once, often from apps and tags.
Cumulative Layout Shift: does it jump?
Have you ever gone to tap a button and had it move? That is layout shift. A score under 0.1 is good. Images without set sizes, late-loading banners and fonts that swap are the usual causes.
The order we work in
- Measure on a real phone, on a mobile connection, not just in a lab report.
- Remove what the page does not need: apps, tags, unused code.
- Fix the main image and the fonts, because they decide what the customer sees first.
- Set sizes for everything that loads late, so nothing jumps.
- Measure again and keep a record.
We give every speed engagement a before-and-after reading from PageSpeed Insights or WebPageTest, so the result is on the record.
Photograph from Unsplash.





