Development / Performance
What Actually Makes a Website Fast (and Why It Affects Rankings)
Quick answer
Website speed is measured by Google through three Core Web Vitals: Largest Contentful Paint (how fast the main content loads), Interaction to Next Paint (how quickly the page responds to clicks and taps), and Cumulative Layout Shift (how much the layout jumps around while loading). Pages that pass all three tend to rank better, because Google uses them as a direct ranking signal and because faster pages simply keep visitors around longer.
"Make the site faster" is one of the most common requests an agency gets, and one of the vaguest. Speed isn't a single number — it's a handful of measurements, and each one is caused by a different set of technical decisions. Here's what actually moves them.
The three metrics that matter
Largest Contentful Paint (LCP) measures how long it takes for the biggest visible element — usually a hero image or headline — to render. Google's target is under 2.5 seconds. LCP is usually slowed down by unoptimized images, slow server response times, or render-blocking CSS and JavaScript loaded before the main content.
Interaction to Next Paint (INP) measures how quickly the page responds after a click, tap, or keypress. Google's target is under 200 milliseconds. INP suffers most from heavy JavaScript that locks up the browser's main thread — think large frameworks doing unnecessary work on every interaction.
Cumulative Layout Shift (CLS) measures how much visible content shifts position while a page loads. Google's target is under 0.1. CLS is almost always caused by images or ads without a reserved size, or web fonts that swap in and reflow the text around them.
What actually causes slow sites, in order of impact
- Unoptimized images. A single unresized hero photo can outweigh every other asset on a page combined. Modern formats (WebP, AVIF) and proper sizing fix most of this instantly.
- Too much JavaScript. Heavy front-end frameworks loaded for a mostly-static marketing page add download weight and processing time the page doesn't need.
- Unreserved space for dynamic content. Ads, embeds, and web fonts that load in without a placeholder cause the layout shifts that hurt CLS.
- Slow hosting or server response. No amount of front-end optimization fixes a server that takes seconds to respond to the first request.
- Render-blocking resources. CSS and JavaScript loaded in a way that forces the browser to wait before showing anything at all.
Why this affects rankings, not just user experience
Google has used Core Web Vitals as a ranking factor since 2021, meaning speed has a direct, if modest, effect on where a page lands in results — on top of its well-documented indirect effect: slow pages have measurably higher bounce rates, and visitors who leave before content loads never get the chance to convert. For AEO and GEO specifically, a fast-loading page is also more likely to be crawled and processed reliably by the bots that power answer engines and AI assistants, which tend to time out on especially slow or heavy pages.
The practical fix list
For most sites, four changes account for the majority of the improvement: compress and correctly size every image, remove JavaScript libraries the page doesn't actually need, set explicit width and height on images and embeds, and choose hosting with a fast time-to-first-byte. This is the audit Webnety runs at the start of every build and redesign — see our web development service for the full technical checklist.