Rebuilding a WooCommerce store around Core Web Vitals
A US homeware brand was paying for traffic that bounced on mobile. We rebuilt the front end around Core Web Vitals and a simpler purchase path — keeping the brand and the platform.
When the ads are not the problem
The brand sold homeware direct to consumers in the US and Canada. Desktop looked fine. On mobile, sessions were arriving and leaving: paid social was getting blamed, but session recordings pointed at the site. Pages took too long to become usable, the product page competed with itself for attention, and checkout asked for more than it needed to.
The team had already been through a visual redesign. The design was not the issue — the templates underneath it were heavy, and every marketing tool had been allowed to load everywhere.
The audit
We ran a template-level performance audit rather than a page-by-page checklist: which components appear on which template, what each one loads, and whether it blocks rendering. Alongside it we reviewed session recordings and the analytics path from landing page to add-to-cart to checkout.
The pattern was familiar. A large hero carousel loaded on every page. Font files were requested in several weights and formats. Widgets for reviews, chat and analytics loaded site-wide whether or not they were needed. The product page had competing calls to action above the fold, and the mobile menu carried the full desktop navigation.
What we changed
This was a template rebuild, not a new brand:
- Images moved to a modern pipeline with responsive sizes and lazy loading, with careful handling of the first visible product image.
- Typography was consolidated to fewer weights and self-hosted files.
- Third-party scripts were split by template, so a review widget loads on the product page and nowhere else.
- JavaScript was reduced on first view; non-critical behaviour loads after the page is interactive.
- Product pages were simplified around one primary action, with size and delivery information visible before the add-to-cart button.
- Checkout was tested on throttled mobile devices through every step, including guest checkout and address entry.
How we measured it
We measured on real mid-range devices and throttled connections, not only on a fast desktop. Each template was tracked separately so we could tell which change helped and which did nothing. Where field data was available we used it as the reference; lab measurements were used to catch regressions between releases.
The work was released template by template. The product page went first because it carried the most paid traffic, then category pages, then checkout. That made rollback simple and kept the team involved in each decision.
What changed for the team
The store is faster on the devices that matter, with fewer blocking requests and a shorter path from landing page to cart. The brand and the platform stayed; the hosting did not need to change.
The client can now edit pages without calling a developer, and the theme no longer loads every plugin’s assets on every template. Performance work is ongoing — templates are reviewed whenever a new app or campaign is added, because that is where regressions come from.
Ready for a store that sells while you sleep?
Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.