At a glance
Engagement model
- Deliverables
- 10 defined outputs
- Pricing
- Fixed-fee audit, or audit plus implementation. Ongoing monitoring can be added monthly.
- Next step
- A short call, then a written proposal
- Baseline performance report with field and lab metrics for key templates
- Image audit and optimisation: correct dimensions, modern formats, responsive sizing, lazy loading below the fold
- JavaScript audit: bundling, code splitting, deferral and removal of unused libraries
The context
What speed optimization actually involves
Speed problems rarely have a single cause. A page can be slow because of a 4 MB hero image, a chat widget, four separate analytics scripts, a render-blocking font request and a hosting plan that throttles under load — all at once. Optimisation works when you measure, fix the largest contributors in order, and re-measure.
We start with real field and lab data, identify what is actually holding the page back, then implement fixes in the codebase and configuration. Every change is verified against the same measurements so you can see what moved and what did not.
Problems this solves
Visitors leave before the page renders
On a mid-range phone over mobile data, a heavy page can take several seconds to become usable. Slow first paint and layout shift are visible costs you are paying in bounce rate and paid-click wastage.
Core Web Vitals flagged in Search Console
Poor LCP, CLS or INP groups pages into a weaker experience category. Fixing the underlying causes is a technical job — the report tells you what is failing, not why.
Performance plugins that made things worse
Stacked caching and minification plugins often conflict, cause layout breakage or inject more JavaScript than they save. We rationalise the stack instead of adding to it.
Unmanaged third-party scripts
Tag managers, heatmaps, chat widgets and A/B tools accumulate quietly. Each one costs main-thread time and can delay interactivity for the visitors you most want to convert.
What you get
Deliverables, defined in advance
- Baseline performance report with field and lab metrics for key templates
- Image audit and optimisation: correct dimensions, modern formats, responsive sizing, lazy loading below the fold
- JavaScript audit: bundling, code splitting, deferral and removal of unused libraries
- CSS optimisation and removal of render-blocking resources
- Font loading strategy, including self-hosted fonts and preloading for critical files
- Caching and delivery configuration, including CDN and compression recommendations
- Third-party script review with deferral or removal recommendations
- Layout stability fixes: reserved media dimensions and reduced late-loading content
- Mobile-specific performance pass
- Before-and-after measurement summary with the changes documented
Why it matters
Business benefits
Better experience, measurable results
Faster loading reduces friction on every visit and every ad click — the improvement applies to all traffic channels at once.
A technical baseline you can maintain
You get a documented list of what was changed and why, plus monitoring guidance, so future updates do not quietly undo the gains.
Marketing spend goes further
Paid traffic lands on a page that renders quickly, which improves the return on the clicks you have already paid for.
Process
How the engagement runs
- Step 1
Measure
We collect lab data for representative templates and, where available, field data from real users, and note what is measured versus what cannot be observed.
- Step 2
Prioritise
Findings are ranked by effect and effort. Two or three changes usually deliver most of the gain; a long tail of micro-optimisations is listed but not oversold.
- Step 3
Implement and verify
Fixes are applied on a staging environment, checked for visual regressions, then deployed and re-measured with the same method.
- Step 4
Monitor
We recommend ongoing monitoring so regressions from new plugins, scripts or content are caught quickly rather than discovered months later.
What Core Web Vitals actually measure
Largest Contentful Paint (LCP) measures when the main content of the page has rendered — usually the hero image or headline. Cumulative Layout Shift (CLS) measures unexpected movement of content while the page loads, which is why elements shifting under a tapping finger is both an annoyance and a metric problem. Interaction to Next Paint (INP) measures responsiveness when someone clicks or types.
Each has distinct causes. LCP problems are typically server response time, render-blocking resources or an oversized hero image. CLS usually comes from images without dimensions, injected banners and late-loading fonts. INP problems are main-thread work from JavaScript. We address the cause rather than the symptom.
Where the gains usually are
In most audits the largest wins come from image weight, third-party scripts and unnecessary JavaScript shipped to every page. Replacing a 1.8 MB hero photograph with a correctly sized 120 KB modern-format version, deferring a chat widget until interaction, and removing a carousel library used on one page can transform the mobile experience — without changing the design.
We report honestly when the constraint is not the code: a low-cost shared host with slow server response cannot be optimised away in the front end, and the recommendation will be to change the hosting plan.
What we do not promise
- We cannot guarantee a specific Lighthouse score. Lab scores vary by device, run conditions and third-party scripts outside our control; we report measured before-and-after values instead.
- Performance work is not guaranteed to improve rankings. Speed is one factor among many, and we will not claim causation we cannot evidence.
- Third-party platforms you embed (CRM chat, review widgets, booking systems) may set their own performance floor. We will identify the cost and options.
How pricing works
Fixed-fee audit, or audit plus implementation. Ongoing monitoring can be added monthly.
Advertising spend, platform subscriptions and third-party licences are paid by you directly and are always shown separately from our fee.
See pricing approachQuestions
Speed Optimization FAQ
A focused audit is typically delivered within a week or two of access. Implementation depends on the platform and the number of templates, commonly one to four weeks. We confirm a timeline after the audit rather than before it.
Yes, provided we have access to the codebase, hosting and CMS (or a staging copy). Some platforms restrict what can be changed; if that is the case we say so and outline the achievable subset.
They last as long as the codebase and plugin stack are managed. New third-party scripts, larger images or a theme update can reintroduce the issue, which is why we recommend monitoring as part of a maintenance arrangement.
Start here
Ask about speed optimization
- Reply within one to two business days
- Written proposal with scope and fees
- No obligation and no pressure to proceed
Before you write
The more specific the context, the more useful the first reply. Useful things to mention:
- What the business sells, and to whom
- What is not working right now
- Any deadline or budget range already agreed internally
We do not publish guaranteed rankings, revenue projections or invented case results. If something cannot be judged without access to your accounts, we will say so.