Skip to content
PROBLEM · SOLVED BY PROGRAMMATIC WEB DEVELOPMENT · SEO & ORGANIC GROWTH

Slow site. The fix is rarely "buy faster hosting."

A slow site costs rankings, leads and bounce rate — but the cause is usually pagebuilders, image weight and third-party scripts, not hosting. Here's the fix order.

2.5s
Target LCP after Core Web Vitals fix
4
Common symptoms
2
Pillars that fix it
3
Verticals where this hits hardest
90
Day rolling cycle to fix
Symptoms

If any of these sound familiar, this is your problem.

If two or more of these are happening at once, you almost certainly have the underlying problem — not the symptom you came in to fix. The diagnosis below explains why.

01

PageSpeed Insights shows mobile in the red

02

Largest Contentful Paint over 4 seconds

03

Bounce rate spiking on mobile, fine on desktop

04

CMS-builder pages with 60+ requests and 5MB+ payloads

Root cause analysis

Four underlying causes — ranked by frequency.

The visible symptom is rarely the actual problem. These are the causes we find most often when we run the diagnostic on operators with this exact pattern.

  1. 01

    Mobile Core Web Vitals failure

    LCP over 2.5s, INP over 200ms, CLS over 0.1 on the converting page. Google ranks against this; users bounce regardless.

  2. 02

    Render-blocking dependencies

    A theme or plugin is loading 600KB of CSS and JS in the head before first paint. Half could be deferred without breaking anything.

  3. 03

    Hosting that can’t handle peaks

    Shared hosting under launch traffic queues requests behind one another. The site does not scale because it cannot.

  4. 04

    No build pipeline

    Every change is hand-edited live. No staging, no version control, no rollback. One bad change takes the booking page down for hours.

Why it happens

The root cause — in plain English.

Three culprits in this order. One: page builders (Elementor, Divi, WPBakery) add 2-4MB of unused CSS and JS that loads on every page. Two: hero images shipped at 2400×1600 unoptimised, which alone tank Largest Contentful Paint. Three: third-party scripts — Hotjar, FB Pixel, GA, chat widget, cookie banner — each adding render-blocking time. Hosting matters last; speed problems are 80% front-end weight.
How we diagnose it

The first three things we check.

We run Lighthouse on the top five commercial pages and rank fixes by impact-vs-effort. The unblock list is almost always the same: convert hero images to AVIF/WebP at correct dimensions, defer third-party scripts to load on interaction, remove unused CSS via critical-path inlining, and switch the page builder layouts to native blocks where the page is fixed-template. We hit Core Web Vitals green inside 2-3 weeks without changing host.
The cost of waiting

A 1-second improvement in mobile load time is worth ~7% in conversion — for a site doing 10,000 monthly visitors at 2% conversion that's £1,400-£8,000 a month depending on order value.

First action this week: Run PageSpeed Insights on your top three landing pages and screenshot the diagnostics — the "opportunities" list ranked by ms-saved is your first sprint.

Book the 30-min diagnostic →
Free 2-page diagnostic

Send your domain. We’ll send back a 2-page diagnosis.

Specific to your stack, scoped to this problem. Three quick wins. A tailored band for the work it would take. No call required.

No card required · Your data stays private · One reply, then nothing unless you ask

The fix roadmap

What we ship in the first 30, 60 and 90 days.

A productised cycle on this problem follows the same rhythm: audit, build, ship, compound. Below is the cadence by phase — same pattern whether you start with DWY coaching, an embedded sprint, or a full DFY retainer.

Phase 01 · Diagnose

Find the actual cause

Written audit pack within the first two weeks. Tracking, attribution, content depth, technical foundations — scored red, amber, green with named owners and dated next steps.

Phase 02 · Foundation

Fix what blocks every other fix

Server-side tracking live, schema deployed, GA4 events firing correctly, CRM routing tested. Foundations ship before campaigns — no exception, no shortcut.

Phase 03 · Ship

Weekly delivery, on cadence

Pages, posts, schemas, ad creative, email sequences. One weekly drumbeat, every Friday in your portal. Three cycles before we stop iterating on what we shipped.

Phase 04 · Compound

Read the signal, double down

Cycle review with named numbers. Keep what shipped value, kill what didn’t, propose the next 90 in writing. Walk-away rights at every cycle boundary.

Tools we use

Industry-standard, never proprietary.

Every tool below is one you can sign into yourself, take with you when we’re done, and keep running without us. We don’t run black-box dashboards on top of your data.

Hosting on managed WordPress / Vercel / DigitalOcean
Cloudflare for edge + caching
Lighthouse CI for performance budget
WP Rocket or Litespeed Cache
Wraith or Backstop for visual regression
Sentry for runtime errors
FAQ

Six honest questions about this problem.

If yours isn’t here, drop it in the contact form and we’ll answer in writing within a working day.

How long until we know if this is actually fixed?

Time-to-signal canon is 60–90 days. Some shifts (tracking fixes, schema deployment, speed-to-lead automations) move numbers in week one. The compounding signal — the steady week-on-week climb you can chart on a single line — lands in cycle two, around day 60. By cycle three you can read the rate of climb and forecast.

What’s the smallest viable engagement we can start with on this?

Either a £750 standalone audit (5–7 working days, written) or a £3,000 two-week embedded sprint against a fixed scope. Both credit against the first cycle of a DWY or DFY retainer if you sign within 30 days. Neither requires a long-term commitment.

Why is the “cost of waiting” number so high?

It’s the median we see across operators we’ve audited in your size band. The mode is lower; the right tail is much higher. A 20-minute discovery call gets you a tighter range specific to your spend and stack — in writing, no obligation.

We have an in-house team already. Do we still need this?

Not necessarily. If two or more of the symptoms above are showing, weekly coaching at £750/month (the Coach plan) often gets your team unblocked without a full retainer. We tell you which way is right for your team in the discovery call — and we tell you in writing if the answer is “you don’t need us.”

Do you work with our existing agency, or do we have to switch?

We work with both. About 40% of our DWY engagements run alongside an incumbent agency — we coach the in-house team, the agency keeps shipping. We’re open about scope. If the existing agency is the actual problem, we’ll say so in writing and let you decide.

How do you measure success on this specific problem?

Three numbers, every cycle: the headline metric this problem affects (CPL, conversion rate, organic enquiries — whichever applies), pipeline value attached server-side, and one downstream commercial signal that maps to your buyer journey. We don’t lead with vanity metrics like rankings, impressions or share-of-voice — they’re leading indicators, not commercial outcomes.

Three ways to fix this

Read the playbook, get coached, or have us ship the fix.

You can solve this yourself with the playbook below, get a senior practitioner reviewing your work each week, or hand the whole pillar over on a productised retainer. Whichever you pick, the canon is identical.

DIY · Self-serve

Read the playbook

If you have an in-house team with the bandwidth to run an audit and ship the fix yourselves, the playbook is free.

From £0

144 free playbooks · templates £49+

The full diagnosis, the audit checklist, the deliverable templates, and the 90-day roadmap. Same canon we use on retainer.

  • 50+ page playbook for the pillar that fixes this
  • Audit checklist — the 8–10 things to check first
  • Deliverable templates — GA4 spec, briefs, schemas
  • Quarterly office hours — bring your work, get reviewed
Open the playbook →
DWY · Done with you

Coach us through it

For teams that have hands but want a senior practitioner reviewing the work each week and unblocking quickly.

From £750 / mo

Coaching · cohort · sprint

Weekly 1:1 or team coaching, a custom course built around this exact problem, plus optional embedded sprints.

  • Weekly 90-minute coaching with a named practitioner
  • Custom course built around fixing this exact problem
  • Embedded sprints — we sit in your tools 1–2 weeks
  • Audit pack with named owners and dated steps
See coaching plans →
Most chosen
DFY · Done for you

Ship the fix on retainer

We run the pillar that fixes this, end-to-end. Fixed scope, weekly delivery, server-side tracking from form-fill to closed-won.

£1,500 – £6,000+ / mo

Foundation · Compound · Architect

The bands above. We diagnose in week one, ship the first fix in week two, and run the cycle on rolling 90-day terms with walk-away rights.

  • Productised pillar with named owner and dated 90-day roadmap
  • Server-side tracking from form-fill to closed-won
  • Weekly delivery — no scope creep, no surprise invoices
  • You own everything — tools, data, accounts, content
Book a discovery call →
Ready to fix it

Book the 30-min diagnostic.

Bring one number you want moved and one constraint you cannot break. We’ll spend the first five minutes on those, the next twenty on the playbook that fits, and the last five on whether we’re the right studio for you.

Operating across the Weir family network — Josh Weir·Mark Weir·Weir Digital Media·CMW Consultants