Quick start · Websites · 2 weeks
Speed optimisation. Two weeks to pass Core Web Vitals.
- Length
- 10 business days.
- You get
- The fixes applied, before and after field data.
- Cost
- Fixed, agreed in writing before we start.
- Clients rate us
- 4.7 / 5 from 23 Google reviews
Who does what
You give us the site. We give it back faster.
You hold
- Access to the CMS, the hosting and the DNS
- A staging environment, or we set one up
- Sign off on the changes before they go live
Codeeo holds
- Field data baseline and a fix list in the first two days
- Images, fonts, scripts, caching and hosting fixed on staging
- Third party tags audited and the slow ones moved or removed
- Everything deployed with the after measurement
What gets done
The fixes that move the three numbers.
- Largest Contentful Paint
- Server response, caching, image formats and sizes, critical CSS and the fonts that block the first paint.
- Interaction to Next Paint
- Long tasks, heavy scripts and third party tags split, deferred or removed so taps respond.
- Cumulative Layout Shift
- Reserved space for images, ads and embeds, and the late loading elements that push content around.
- Hosting and delivery
- CDN, caching rules and compression configured, with the edge cache tested rather than assumed.
- The after report
- Field data before and after, page by page, with what to keep doing so it stays fast.
How the two weeks run
Baseline, fix on staging, measure live.
Every quick start runs on the same rule: a written scope and a fixed cost before day one, a named lead, and a report you own whether or not you continue with us.
Days 1 and 2: baseline
Field and lab data pulled, the causes named, the fix list agreed.
Days 3 to 7: fixes on staging
Images, scripts, fonts, caching and hosting, tested page by page.
Days 8 and 9: deploy
Changes go live with your sign off, monitored for regressions.
Day 10: the after report
Field data compared to the baseline, with the upkeep notes.
Is this the right start?
Is speed optimisation the right start?
Tick what describes you
The verdict updates as you go. Nothing is recorded.
Or, if you
- You are not sure speed is the main problem.Start with a website audit
- The slow part is the checkout specifically.See the checkout teardown
Questions about the speed optimisation
Everything goes through staging and your sign off.
Other quick starts
Not the right question? There are eight more.
- 015 daysWebsite auditTechnical, speed and conversion report
- 022 weeksProduct scopingScope, timeline and a fixed cost
- 031 weekPlatform fit reviewWhich platform, and what it will cost to run
- 043 daysCheckout teardownWhere the basket is losing orders
- 055 daysVisibility auditWhere your buyers are searching, and who is winning
- 061 weekCodebase reviewWhat you have, and what it will cost to carry
- 075 daysTechnical SEO reviewCrawl, index, structure and schema, fixed or listed
- 083 daysConversion teardownWhy visitors leave without enquiring, and the fixes
Start it
Start the speed optimisation.
A reply within one business day with the scope and the fixed cost in writing.
- 1
A reply within one business day
From the lead who would run it, with two or three questions.
- 2
The scope and cost in writing
What is in, what is out, the fixed cost and the start date.
- 3
Access and start
Read only access on your accounts, and the work begins.