Blog / seo wednesday
Site speed and SEO: what actually moves rankings
Speed is a tiebreaker in search, not a magic lever. Where hosting, caching, and images actually help, and when to stop optimizing.
Wednesdays on this blog are for SEO, and we are starting with the question we get asked most, probably because we are a host: how much does site speed matter for rankings?
Short answer: it matters, but less than the people selling speed optimization packages want you to believe. Here is the honest version.
Speed is a tiebreaker, not a lever
Google has used page speed as a ranking signal for years. But it sits well below relevance and content quality. A fast page with a thin, vague answer will lose to a slower page that actually answers the searcher's question. Every time.
Where speed does bite is at the extremes and at the margins. A site that takes eight seconds to load bleeds visitors before they ever see the content, and Google notices that behaviour. And when two pages are otherwise close, the faster one tends to win the coin flip. That is what a tiebreaker means: it decides close contests, it does not rescue weak content.
So the right mental model is a threshold, not a race. Get comfortably fast, then go write better pages.
Hosting sets the floor
Everything you do on the front end sits on top of one number: how long the server takes to produce the HTML. If that takes two or three seconds, no image plugin will save you.
We see this pattern constantly. Slow WordPress sites are usually slow because of an overloaded server, an ancient PHP version, or a database gasping under forty plugins. Fix those and the same site often loads in under a second with no other changes.
This is the part your host controls. Our shared hosting runs current PHP with server-level caching available, and sites that outgrow shared plans usually do better on a small cloud server than on any amount of front-end tuning. Whoever hosts you, ask them what your time to first byte looks like from their side. A good host can tell you.
Caching and images do most of the work
After hosting, two fixes deliver the bulk of the improvement for a typical WordPress site.
Page caching first. WordPress builds every page from scratch by default, running PHP and querying the database for each visitor. A caching plugin saves the finished page and serves it as a static file. That alone routinely cuts load times in half or better, and it costs nothing.
Images second. On most small-business sites, images are 70 to 90 percent of the page weight. Resize them to the size they are actually displayed at, compress them, and let them lazy-load below the fold. A 4 MB photo straight off a phone camera, scaled down by the browser to fill a 400-pixel column, is the single most common speed problem we see in support tickets.
Do those two things and most sites land somewhere respectable without touching anything else.
Diminishing returns start early
Here is the part the optimization industry skips: going from eight seconds to three is transformative. Going from 1.8 seconds to 1.4 is invisible. Visitors will not notice, and your rankings will not move.
Yet that second project costs more than the first, because the cheap wins are gone. You end up inlining critical CSS, self-hosting fonts, and arguing with a waterfall chart to shave 80 milliseconds. There are sites where that effort pays, mostly large stores where a small conversion bump multiplies across real traffic. A ten-page local business site is not one of them.
Once your pages load in a couple of seconds on a mid-range phone, the SEO work that pays is boring: clearer pages, better titles, content that matches what people search for. Speed stops being the bottleneck long before most people stop spending money on it.
If you suspect the slow part of your site is the server rather than the site itself, that is a question worth settling before you buy any plugin. Open a ticket with our support team and we will pull the server-side numbers with you.