Speed is a Google ranking signal. It is also a much weaker one than most agencies imply — a fast page about nothing will not outrank a slow page that answers the question. The real cost of a slow site is paid elsewhere.
What Core Web Vitals measure
Three metrics, each describing a different frustration:
- Largest Contentful Paint — how long until the main content appears. Under 2.5 seconds is the target.
- Interaction to Next Paint — how quickly the page responds when tapped. Under 200 milliseconds.
- Cumulative Layout Shift — how much the page jumps while loading. Under 0.1.
They are measured on real visits, not in a lab, so a result from your office fibre connection is not the number Google uses.
The stronger argument
Ranking aside, slow pages lose people before they read anything. A visitor who leaves before the page renders costs you the enquiry regardless of what position you held in the results. On mobile connections outside city centres, the gap between a 1-second and a 5-second page is the difference between a lead and a bounce.
What actually moves the numbers
In rough order of impact for a typical business site:
- Images. Almost always the largest thing on the page. Serve modern formats, size them for the space they occupy, and set explicit width and height so the layout does not jump.
- JavaScript. Every kilobyte is downloaded, parsed and executed. Sites assembled from a dozen third-party scripts are slow because of the sum, and no single script looks guilty.
- Render-blocking resources. Fonts and stylesheets loaded before anything paints. Self-host fonts and give them a real fallback so text is readable while the webfont loads.
- Server response time. If the server takes a second before sending a byte, nothing downstream can recover it.
- Third-party tags. Analytics, chat widgets, pixels and heat maps. Each is small; ten of them are not.
Rendering strategy matters more than micro-optimisation
A site that ships HTML the server already rendered starts ahead of one that ships an empty page and assembles content in the browser. That single architectural choice usually outweighs every tweak applied afterwards — and it helps crawlers, which see content immediately rather than waiting on JavaScript.
Measure the right thing
Use field data — the Core Web Vitals report in Search Console — for what real visitors experience, and lab tools like Lighthouse to find causes. Optimising a lab score while field data stays poor is a common and expensive mistake.
Where BK IT fits
Most speed problems are engineering problems, which is why our SEO work sits with development rather than beside it. Related reading: SEO for Saudi businesses.
Ask us for an assessment if you want to know where your site stands.