Is your Shopify store slow? We measure, fix and re-measure every Core Web Vitals metric — LCP, CLS and INP — one at a time, with the result written into the contract.
Prefer email? hello@shopindev.com
Our Lighthouse score went from 42 to 98. That is not just a number — the same ad budget now brings twice the sales.
Largest Contentful Paint below 1.5 seconds on mobile home and product pages — guaranteed in writing.
A performance score of 95 or above after optimization, or your money back. It has never been triggered.
LCP, CLS and INP all in the 'good' range, visible in your Search Console report within weeks.
Klaviyo, Yotpo, review and chat widgets audited for their real cost, then deferred or removed.
WebP and AVIF, responsive srcset, correct lazy loading and full use of the Shopify CDN.
Before-and-after comparison, monthly monitoring and regression alerts if a new app slows you down.
Lighthouse, PageSpeed Insights, WebPageTest and real-user data. Every issue listed and prioritised by impact.
Image optimization, lazy loading, font-display, deferred third parties — typically a 30%+ score jump.
Critical CSS, code splitting, Liquid query optimization and bundle-size reduction.
Field data via Core Web Vitals, Search Console confirmation and a conversion-impact report.
A slow Shopify store is rarely slow because of Shopify. This is the order we work in, and what we measure to prove it worked.
Google ranks on field data from real Chrome users, reported in Search Console over a rolling 28 days. We start there, use Lighthouse only to iterate quickly, and judge success by the field numbers moving — LCP under 2.5 s, INP under 200 ms and CLS under 0.1 are the thresholds that count.
On most stores the largest element is the hero or first product image. Preloading it, giving it fetch priority, never lazy-loading it and serving it at its displayed width usually moves LCP more than any other single change.
Interaction to Next Paint suffers when long JavaScript tasks block the main thread. Review widgets, chat, popups and analytics are the usual culprits. We measure each app's real cost, defer what is not needed for the first interaction and remove what nobody uses — including code left behind by apps uninstalled months ago.
CLS comes from content inserted into space nobody reserved: images without dimensions, late banners, review stars, cookie bars. Fixing it is mostly declaring sizes and aspect ratios in the theme.
Our engagements carry a written target — Lighthouse 95+ and LCP under 1.5 s — and we report before and after on the same pages, so the improvement is measured rather than claimed.
Performance decays with every new app, tag and unoptimised campaign image. Monitoring with an alert on regression turns optimisation from a one-off cost into something that lasts.
Three causes cover most cases: a bloated theme with 20+ apps each loading 100KB of JavaScript; unoptimised images served at full resolution; and third-party scripts loading synchronously. A proper audit separates them.
The standard engagement is 4–5 weeks: audit, quick wins, deep optimization, verification. A two-week sprint version exists for urgent cases.
Google uses them as a ranking signal, especially on mobile. More importantly they move revenue: stores with LCP under two seconds convert measurably better than those above four.
Only if it is watched. Adding apps or updating the theme can undo the work, which is why our retainer includes monitoring with an automatic alert when performance regresses more than 10%.
