Tell us what needs to change. We will help you scope it.
Start a project →A fixed two-to-four-week sprint on your WordPress, WooCommerce, Shopify or Laravel site. We find what slows LCP, INP and CLS, fix it in priority order, and measure the result the same way we measured the baseline.
A fixed sprint on your existing site. We fix what moves the field numbers: images, fonts, scripts, apps and plugins, caching and server response. Then we compare field data and lab traces taken under the same conditions.
Each area is marked included, excluded or optional in the proposal.
CrUX field data for your origin and key URLs, plus lab traces on the templates that matter: home, product, category, post and checkout.
Formats, sizes and lazy loading, with the LCP image loaded first. Video and embeds load only when needed.
Self-hosted files, fewer weights, preloads and fallback faces sized so text does not jump when the font swaps.
Tag managers, chat, reviews, pixels and test tools listed with their cost, then delayed, trimmed or removed with your sign-off.
What each one loads on each template. We remove or replace the heavy ones and record why.
Long tasks traced in Chrome, heavy event handlers split up, and main-thread work cut on the pages people click most.
Page and object caching, CDN rules and server response time checked. Hosting changes are recommended, never forced.
Space reserved for images, banners, ads and embeds, so content stays put while the page loads.
A sample with illustrative findings. Yours lists your templates, your numbers and the test conditions.
| # | Finding | Evidence | Fix | Status |
|---|---|---|---|---|
| F-01 | Hero image loads late on product pages | Lab trace: LCP image requested after two scripts | Preload, correct size, AVIF and WebP | Fixed |
| F-02 | Review widget blocks the main thread | Long tasks after tapping add to cart | Load the widget when it scrolls into view | Fixed |
| F-03 | Four font weights, no fallback sizing | Layout shift when the font swaps on mobile | Two weights, size-adjusted fallback | Fixed |
| F-04 | Chat script on every page | Third-party bytes in the waterfall | Load on interaction, product pages only | Approved |
| F-05 | Removed app still injects code | Theme code search and network log | Remove leftover snippets | Fixed |
| F-06 | Slow server response on cart | Server response time across five lab runs | Hosting change, recommended | Open |
A speed claim is only as good as its method. These rules apply to every sprint.
Everything stays in your accounts. You keep the reports and the change log.
Field and lab numbers for each key template, with the test conditions written down.
Every issue with its evidence, fix, owner and status, ranked by impact per hour.
Theme, plugin, app and server changes tested on staging, then released in a quiet window.
The same tests rerun under the same conditions, with field data tracked through the 28-day window.
Rules for images, fonts, scripts and new apps, so the gains survive the next change.
Fixes go to staging first. Nothing reaches the live site without a test and a way back.
Field data pulled, key templates traced in the lab, and scripts and apps listed with their cost. Output: the baseline report.
Baseline agreedEach finding sized by impact and effort. You approve which scripts, apps and plugins can change.
Fix list approvedFixes built and tested on staging, then released in small batches so each change can be measured.
Each batch acceptedLab tests rerun under the baseline conditions, field trend tracked, keep-it-fast notes handed over, and a check-in booked after the 28-day window.
Before and after report deliveredNot a Lighthouse score. The numbers Google actually uses: field data from Chrome users over the last 28 days, plus a lab run to explain them. With fixes in plain English, sorted by what moves the needle.
Check your URLThree doors next to this one.
Updates on staging first, restore drills, monitoring, a monthly report.
S06Keep the rankings and content that work. Replace what doesn't.
S09Stores that load fast, check out cleanly and reconcile every order after a migration.
It depends on who builds the templates. On a site we design and build, the launch guarantee applies. If a template we built misses Core Web Vitals at launch, we fix it at no cost. A speed sprint on an existing site guarantees the method, not a pass. You get a baseline, ranked fixes, and a before and after measured under the same conditions. Field data depends on your visitors' devices and networks, which no one controls.
Field data comes from real Chrome users and is collected in the CrUX report over 28 days. Lab data is a controlled test on one device and network. Google looks at field data, and lab traces explain why the field numbers look the way they do.
The three Core Web Vitals: LCP for loading, INP for responsiveness and CLS for visual stability. We also track server response time and total script cost, because they drive the first two.
Yes, within the platform's limits. Shopify controls hosting and checkout, so the work focuses on the theme, apps, images, fonts and third-party scripts. Leftover code from apps you removed is a common find.
Yes. On WordPress and WooCommerce we also tune plugins, caching, database queries and hosting. On Laravel we look at queries, caching, asset builds and server setup as well as the front end.
Not without your sign-off. We list every third-party script with what it costs and who uses it. You decide what stays, and we load the rest later or only on the pages that need it.
Lab results show up as soon as a fix ships. CrUX field data covers a rolling 28 days, so the full effect takes about a month to appear. We book a check-in after that window.
CrUX only reports sites and pages with enough Chrome visitors. If yours does not qualify, we rely on lab traces under fixed conditions and say so plainly in the report.
Page experience is one of many ranking signals, so we don't promise ranking changes. A faster site is easier to use, especially on phones. Ongoing SEO campaigns are run by our sister agency BizAttic.
You get keep-it-fast notes for images, fonts, scripts and new apps or plugins. Under a monthly care plan, we run lab tests after every deploy and review field data each week.
