Most of your customers are on a phone, and every extra second costs you enquiries. Google uses page experience as a ranking signal too. I don't throw a cache plugin at it and hope. I measure what is slow, fix that, and show you the before-and-after.
PageSpeed's red score is a symptom. I split the problem the way Google does.
Time to first byte. If this is slow, PHP, the database, or the server is the bottleneck. A CDN will not save a sluggish origin.
Largest Contentful Paint: usually a hero image, a page-builder section, or a webfont. This is what visitors feel.
Clicks that feel dead (heavy JavaScript, live chat widgets) and layout jump. I only chase these if they're actually failing.
After years of plugins, photos, and "just one more builder block", Irish small-business sites tend to share the same pile-up:
width/height, no WebP.A backup, then the work: compress and lazy-load images, cache + CDN where it helps, remove or replace the heavy plugins, and tune the host configuration. Design does not change.
You get the same tests re-run afterwards. If I look at the site and don't think I can improve it meaningfully, I tell you before you pay.
A one-time tune-up starts at €250. Larger sites and shops may cost more; you get a fixed quote first. Keeping it fast afterwards is the €49/month plan, not a second speed project.
We had our WooCommerce store cleaned up, sped up, and properly optimised — page load times dropped significantly, and the checkout experience is much smoother.
Usually not. I measure TTFB separately from LCP. If the host really is the problem, I'll say so and can move the site — I don't push hosting changes that aren't needed, and I don't earn a commission from your host.
No. Caching, images, and plugin cleanup are behind the scenes.
The same Core Web Vitals tests as before, with before-and-after figures in plain English.
Core Web Vitals are a ranking signal, and slow pages lose people before they read anything, which hurts you twice.