If leads are dropping because your pages feel slow, performance-led build standards fix the root issue. This starts with clean code and measurable targets — not plugin patches.
We've seen too many businesses pour money into Google Ads, only to lose those clicks to a three-second load time. The ad did its job. The site didn't.
A slow site doesn't just feel sluggish. It costs you leads — silently, every day.
Core Web Vitals: the targets we build to
Google's Core Web Vitals aren't abstract scores. They measure three things that matter to every visitor.
LCP under 2.0 seconds. Largest Contentful Paint — how quickly your main message appears. Google wants 2.5s. We build for under 2.0s.
INP under 150ms. Interaction to Next Paint — how responsive the page feels when someone clicks. Google wants 200ms. We build for under 150ms.
CLS under 0.08. Cumulative Layout Shift — how much the page jumps around while loading. Google wants 0.1. We build for under 0.08.
Why these targets matter commercially
LCP is first impressions. If the key message loads late, people leave before you even get a chance to make your case. When someone clicks through from a Google search or an ad, and the page takes three seconds to show something useful — they're back on Google before your hero image finishes loading.
INP is responsiveness. If buttons, forms, or menus lag, people stop trusting the page. Click a "Get Quote" button and nothing happens for half a second? That's doubt creeping in. Doubt kills conversions.
CLS is stability. If content jumps around while someone tries to read — a button moving under their thumb, a paragraph shifting as an image loads above it — you lose leads. Not because your offer is bad. Because your site feels unpredictable.
How we achieve it
Clean HTML, CSS, and PHP. Controlled asset budgets. Explicit image dimensions with width and height attributes so the browser reserves space before the image loads. Proper preload strategy for LCP assets — the hero image or headline that needs to appear first.
That keeps rendering clean and removes the hidden drag that bloated templates introduce. No plugin loading its scripts on every page. No theme CSS with 6,000 lines of unused rules. No JavaScript frameworks pulling in 200KB for a contact form.
We're not doing anything clever. We're just not doing the things that break performance in the first place.
Common drag points we remove
These are the four things we fix on almost every performance audit. They're not complex. They're just rarely done.
-
Huge hero files loading before important page content. A 4MB hero image pushes everything else down the queue. Convert to WebP, resize to actual display dimensions, and suddenly 3.5MB disappears.
-
CSS and scripts that block rendering when they shouldn't. Deferred loading for non-critical assets. Inlined critical CSS for above-the-fold content. The browser paints what matters first.
-
Theme or builder bloat shipping code the page never uses. When you install a theme, you get every feature it offers — whether you use them or not. We ship only what the page actually needs.
-
Layout jumps caused by missing dimensions or late-loading assets. Every image gets explicit width and height. Every embedded element gets reserved space. The page stays still while it loads.
The commercial impact
Faster pages reduce friction and wasted ad spend. Visitors reach your offer faster. Forms respond faster. Conversion paths feel stable — no "did I click that?" uncertainty.
A 1-second improvement in load time can lift conversions by 7%. For a site generating 30 leads per month at £500 average value, that's roughly £1,050 in additional monthly revenue — £12,600 per year — from one performance pass. And that improvement compounds. A faster site ranks better, which brings more traffic, which means more conversions.
Technical foundations including Core Web Vitals are built into every site we create. Not as an add-on. Not as an "SEO package." As the baseline.
How we deliver it
Performance work isn't a one-click fix. Sometimes it's five small improvements that finally remove the drag and make the site feel quick again. Here's our process.
-
Audit current site and establish baseline. We run PageSpeed Insights, Lighthouse, and manual checks. We find out exactly what's slowing things down and by how much.
-
Agree page-level targets. Not "make the site faster" — measurable numbers. LCP under 2.0s on the homepage. INP under 150ms on the contact form. Specific, testable, accountable.
-
Rebuild priority pages with pass/fail criteria. Start with the pages that drive the most revenue. Homepage, service pages, contact form. Fix them. Measure again.
-
Share before/after reporting. You get baseline and after-launch numbers for Core Web Vitals, page weight, and key conversion paths. Plus straight notes on what changed, what still needs work, and what to tackle next.
Quick answers
How long does a performance rebuild take?
For a small site (5–10 pages), typically 1–2 weeks. Larger sites are scoped page by page, starting with the highest-traffic pages. Most of the heavy lifting — image optimisation, code cleanup, caching setup — applies across the entire site.
Will a faster site actually bring more enquiries?
Yes, but it depends on what else is happening. A faster site holds attention longer, which means more visitors reach your call to action. If your site isn't getting traffic in the first place, speed alone won't fix that. But if you're spending money on ads or marketing and losing visitors to load time, a performance rebuild pays for itself quickly.
Do I need a full rebuild or can you just fix the slow bits?
Sometimes the slow bits are fixable in isolation — oversized images, missing caching, a few bloated plugins. Other times the platform itself is the bottleneck, and patching it is like putting a faster engine in a car with square wheels. We'll tell you honestly which route makes sense after an audit.