A fast site pays you back every month. Visitors stay, ad clicks turn into enquiries, search engines crawl more of your pages, and your team stops fighting the server before every campaign. Slow sites do the reverse, and the cost grows quietly because nobody sees the visitors who left before the page appeared.
What to measure first
Google reports three Core Web Vitals for real visitors: Largest Contentful Paint (good is 2.5 seconds or less), Interaction to Next Paint (good is 200 milliseconds or less) and Cumulative Layout Shift (good is 0.1 or less). Field data from PageSpeed Insights tells you what customers experience. A lab score on your own fast laptop tells you far less.
Add one more number: time to first byte. If the server needs more than about 600 milliseconds to start answering, every other fix fights uphill.
The order of fixes that pays back first
- Images. Resize to the displayed size, serve WebP or AVIF, and lazy-load everything below the fold. This alone often halves page weight.
- Caching. Page caching for CMS sites and long browser-cache headers for static files remove most repeated work.
- Third-party scripts. Chat widgets, tag managers and heatmaps each add requests. Remove what nobody reads.
- Database and code. Slow queries and heavy plugins show up as high time to first byte.
- Hosting tier. Move up only after the first four are done, otherwise you pay more for the same waste.
When the plan is the bottleneck
| Signal | Likely cause | Next step |
|---|---|---|
| High time to first byte at quiet hours | Slow code or database | Profile queries, add object cache |
| Slowdowns only during campaigns | CPU or process limits | Isolated resources on a cloud server |
| Fast pages, slow checkout | Uncached dynamic requests | Cache everything except cart and account |
| Simple brochure site, mild delay | Heavy theme | Trim the theme, stay on web hosting |
Make speed a habit
Re-test after every release and every new plugin. Keep a budget, for example "home page under 1.5 MB", and treat a breach like a bug. Pair speed work with HTTPS and a clean redirect setup, covered in SSL installation and Google rankings. If you suspect the plan itself, the slow site checklist walks through the layers in order.
Frequently asked questions
Does page speed affect Google rankings?
Yes, as one signal among many. Relevance still leads, but among similar pages the faster experience tends to hold visitors longer.
Is a CDN enough to fix a slow site?
A CDN speeds up static files. A slow database or an overloaded server still delays the HTML itself.
How often should I test?
After each release or plugin change, and monthly against field data so you see real trends.
Do I need a bigger plan to be fast?
Not before you trim images, caching and scripts. Upgrade when a measured limit, such as CPU during peaks, blocks you.




