Core Web Vitals, front-end and server-side optimization, caching, and scaling under ad traffic
01 / The problem
What it looks like from your side
Your pages load slowly on a phone, or the site struggles every time a campaign sends traffic.
Speed work goes wrong when it starts with a plugin. It goes right when it starts with a measurement: which pages are slow, for which visitors, and why.
What I look at:
Front end. The image that paints last, fonts that block text, scripts that load before they're needed, and tracking pixels loaded twice.
Server. Slow database queries, uncached pages, PHP workers running out, and hosting that can't keep up.
Caching. Page, object and edge caching (Cloudflare) set up so carts, checkouts and logged-in pages stay correct.
Scale. What happens when a campaign sends ten times the usual traffic: load tests, queues and the limits of the current host.
Each fix is measured before and after, so you see what changed and nothing is done on faith.
02 / Signs
Signs you need this
03 / Method
What I do, step by step
01Measure: field data, lab runs and server profiling on the pages that matter
02Find the real causes: images, fonts, scripts, queries, hosting
03Fix in order of impact, measuring each change
04Set up caching that stays correct for carts and logged-in users
05Load-test before the next campaign
04 / Deliverables
What you get
Before and after measurements for each fix
A caching and hosting setup you can keep
A short performance budget to protect the gains
The number I report at the end
LCP and INP at p75 on mobile, server response time, behaviour under load