Google has confirmed for years that page speed is a ranking signal, and in my own client work, the sites that load fast consistently perform better in search and keep visitors around longer. It's one of the first things I check when a client comes to me with an underperforming site, and more often than not, the fix isn't a redesign — it's a handful of technical changes that most site owners never think about. Here's what actually moves the needle, in the order I usually tackle it.
Image format is the biggest quick win
Unoptimized JPG and PNG images are, by far, the most common reason a site loads slowly. Converting images to WebP typically cuts file size by 60 to 90 percent with no visible quality loss, because WebP uses more efficient compression than older formats while preserving detail. On one recent portfolio rebuild, switching every image to WebP took the total image weight from over 40MB down to under 1MB — the same visuals, a fraction of the download.
The impact compounds quickly. A page with ten unoptimized product photos might be pulling 15-20MB just in images before a single line of text renders. Convert those same images to WebP and compress them properly, and that number often drops under 2MB, which on a typical mobile connection is the difference between a two second load and an eight second one.
What Core Web Vitals actually measure
Google uses three specific metrics to judge whether a page feels fast to a real visitor, and each one catches a different kind of problem:
- LCP (Largest Contentful Paint) — how fast the main content loads, usually a hero image or heading. This is most affected by image size, server response time, and render blocking CSS or JavaScript.
- CLS (Cumulative Layout Shift) — whether elements jump around as the page loads, which happens when images or ads load without a reserved space, pushing content down mid read.
- INP (Interaction to Next Paint) — how quickly the page responds when someone clicks or taps, which mostly comes down to how much JavaScript is running and how efficiently it's written.
All three feed into how Google scores a page's overall user experience, and all three are things a visitor notices even if they've never heard the term "Core Web Vitals" — they just experience it as a site that either feels smooth or feels sluggish.
Simple steps that fix most speed problems
- Convert images to WebP and set explicit width/height attributes so the layout doesn't shift as they load
- Use
loading="lazy"on images below the fold, so the browser doesn't waste bandwidth loading content the visitor hasn't scrolled to yet - Minify CSS and JavaScript, and remove unused plugins on WordPress builds — every inactive plugin still adds weight to the admin, and many poorly coded ones load scripts on every page even when they're not needed there
- Host on fast infrastructure — Vercel and similar platforms handle caching, compression and global delivery well by default, without extra configuration
- Set a canonical URL and clean meta tags so Google indexes the right version of each page instead of splitting ranking signals across duplicates
- Audit third party scripts — analytics tools, chat widgets and font embeds are common hidden sources of slowdown that rarely get questioned once they're added
How I test a site's speed
Before touching any code, I run the site through Google PageSpeed Insights and check the Core Web Vitals report in Search Console if the client has access. That gives a baseline for both mobile and desktop, since mobile scores are almost always worse and matter more for ranking, given how much search traffic now comes from phones. From there, it's usually clear within minutes whether the bottleneck is images, unused code, or server response time.
Why this matters beyond rankings
A one second delay in load time measurably increases bounce rate — visitors simply leave before the page finishes loading, and that behavior itself becomes a negative signal that can hurt rankings further over time. Speed isn't just an SEO checkbox, it directly affects whether a visitor sticks around long enough to read your content, browse your products, or fill out your contact form. It's one of the first things I audit on every project I take on, because no amount of good design or copywriting matters if half your visitors never wait long enough to see it.