WordPress · 18 September 2026 · 6 min

WordPress speed: the checks that actually move rankings

A perfect lab score will not save a page that says nothing. A slow page will cap one that does.

Core Web Vitals are a tie-breaker and a conversion problem. They are not a strategy. On WordPress, the usual damage is still the same: a page builder nesting layouts, a slider nobody asked for, three font families, an unoptimised hero, and a plugin that injects a script on every URL.

Decide the budget before the theme

We agree a weight budget for the homepage and a product or service template before design sign-off. If a visual idea needs a megabyte of JavaScript, it does not ship. Block themes and a short plugin list beat a child theme of a multipurpose demo almost every time.

Measure the template people land on

Homepage lab scores are a vanity metric if the enquiry starts on a service page opened from a phone on a train. Check Largest Contentful Paint on those templates, with the cache warm and cold. Fix the hero image, the font loading, and render-blocking plugins before you buy another optimisation plugin.

Keep the editor free

A fast site that only a developer can update will rot. Patterns for heroes, proof bars, FAQs and calls to action let the team publish without inventing a new layout each Friday. Speed work includes that restraint.

After launch, updates and a quarterly speed check belong in a care plan. Themes drift. Someone will install a chat widget. Someone should be allowed to take it off.