Oversized images
A 4000px photo shown at 400px, or five hero images loading at once. Usually the single biggest win.
Home/Website Speed Optimization
Website speed work for real phones, not lab scores
A perfect lab score means little if the site still takes four seconds on a mid-range Android over 4G. Speed work is not about chasing a number: it is about the first screen appearing quickly, the layout not jumping, and taps responding. I measure on the devices your customers actually use, fix the biggest causes first, then measure again.
What usually makes a site slow
Almost every slow site I look at has the same five causes. Fixing them in order is cheaper than rebuilding.
Too much JavaScript
Page builders, chat widgets, sliders and tracking tags each add blocking work before the page responds.
Render-blocking CSS and fonts
Web fonts loading four weights from a third party, with no fallback, blocking the first paint.
No caching or CDN
Every visitor waits for the server to rebuild the same page. A cache and CDN remove that.
Layout shift
Ads, banners and late-loading images pushing content down as the visitor tries to tap.
What the work includes
- Baseline measurement — field data plus throttled mobile runs, recorded before anything changes.
- Image pipeline — correct dimensions, WebP/AVIF, compression, responsive sizes and lazy loading below the fold.
- Critical CSS — the first screen styled immediately, the rest loaded without blocking.
- JavaScript diet — removing unused libraries, deferring the rest, and replacing heavy widgets with light ones.
- Font loading — local or preloaded fonts, limited weights, and a fallback that does not shift the layout.
- Caching and CDN — page cache, compression, long-lived asset caching with versioned URLs.
- Core Web Vitals fixes — LCP element identified and fixed, CLS reserved space, INP kept under 200 ms.
- Re-measurement — the same tests repeated, with the before/after numbers written down.
How the work runs
Measure
Record mobile field data, lab runs and a waterfall of what loads first.
Fix the top causes
Images, fonts, scripts and caching — in order of impact, not order of convenience.
Verify
Re-run the same tests on the same connection profile and compare.
Keep it fast
Add lightweight checks so new content does not quietly undo the work.
How I measure
Field data first
Real-user Chrome UX data and Search Console Core Web Vitals decide what actually needs fixing.
Throttled mobile runs
Lighthouse and WebPageTest on a slow 4G profile — the conditions most visitors are in.
No score-chasing
A 100 in a lab tool is not the goal. A fast first screen and a stable layout are.
Questions clients ask
Will this improve my rankings?
Speed is a confirmed ranking input, but a small one next to relevance. The bigger wins are usually conversion and bounce rate.
How fast can my site get?
Most small business sites can reach a good mobile score. It depends on how much third-party script you are willing to remove.
Do you need to rebuild the site?
Usually not. Images, fonts, scripts and caching fix most of it. A rebuild only makes sense when the template itself is the problem.
Can you speed up WordPress with plugins?
Caching plugins help, but they hide causes rather than remove them. I fix the cause and use a cache on top.
How do you prove it worked?
The same tests, same device profile, before and after — plus field data once enough real visits have been recorded.
Send the URL and I will measure it
A short message with the site address is enough for a first read on what is slow and what it would take to fix.