Photo: Bokeh / Tomedia. Large Cathedral Dome Over Cityscape.
I have a fairly ordinary expectation of a website. When I press a button, I would like something to happen. Preferably the thing the button said it would do, and preferably before I press it again because I assume the first attempt didn’t register.
We can make this sound more complicated by opening a performance report. There will be abbreviations, coloured scores and a list of things somebody now has to fix. Underneath that, a lot of the work comes back to whether the person can use the page without fighting it.
A site that appears quickly can still respond badly once you start using it. Watching the homepage arrive is only part of the test.
Three fairly recognisable annoyances
Google’s current Core Web Vitals cover loading performance, responsiveness and visual stability. The measurements are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. The official guide explains the measures and links to the tools used to investigate them.
You have probably encountered the problems without knowing their names. The main content takes ages to appear. A control doesn’t respond promptly. Something arrives late and moves the link you were about to press.
That last one is particularly annoying because the page can look ready before it has finished rearranging itself. You have already decided what to do, and the website changes the position of the thing you wanted. It can turn a fairly easy task into a small argument with a rectangle.
I would start the investigation with the actual interruption. Which part of the page was slow? What action felt delayed? What moved? A score tells you where to look; it doesn’t automatically tell you which change will help the person trying to use the site.
Everything you add has to run somewhere
Images, fonts, scripts, advertising, analytics and little widgets all have a cost. Individually, somebody presumably had a reason for adding them. Collectively, they can leave a relatively simple page doing a remarkable amount of work.
The first useful question is whether the page still needs all of it. There isn’t much satisfaction in carefully improving the delivery of a component nobody uses. If the business cannot explain why a third-party widget is there, find out before treating it as a permanent requirement.
Then look at the material you do need. An enormous image displayed in a small space deserves attention. So does a page that waits for optional features before making its main content useful. A developer should investigate the cause before applying a collection of performance plugins and hoping they agree with each other.
I would also test more than the one page everybody remembers to show in meetings. Product pages, articles and enquiry forms can load different components. Improving the homepage doesn’t establish that the rest of the site behaves the same way.
A good score still needs a useful page
Google says Core Web Vitals are used by its ranking systems, while making clear that good results in the reports don’t guarantee top rankings. A fast page still needs to answer the search. I wouldn’t promise somebody a position change because a performance score turned green.
There is already a practical reason to do the work. Someone who has chosen your website should be able to read it, select a product or finish an enquiry. We don’t need to invent an exact ranking reward to justify making those things work properly.
Record what changed and repeat the same task afterwards. Keep an eye on it when the next widget, campaign or redesign arrives. Performance work is fairly easy to undo one apparently harmless addition at a time.
The performance sections of The Big Book of SEO on Ephemera cover loading speed and Core Web Vitals in more detail. Buy it for the wider reference. Then go back to the page that annoyed you and find out what it was waiting for.



