TL;DR: The Quick Read
Most Shopify speed agencies sell apps that only compress images and minify CSS, never touching the dead code left behind by uninstalled apps. Judge agencies by documented LCP-in-seconds results, not PageSpeed scores out of 100. We ranked six agencies against a public five-point rubric, ourselves included.
- Demand seconds, not scores: a PageSpeed score can hit 95 while checkout still lags, per Google's own Core Web Vitals documentation, which treats LCP as the metric tied to real user experience.
- Ask if they work in theme.liquid: app-only fixes can't remove the exact kind of dead code that dropped one brand's LCP from 5.4s to 1.4s, detailed in the CPG brand case study.
- Check for ghost script removal by name: a specific process for finding orphaned code from deleted apps, not a generic "app audit."
- Get your own store measured first: see exactly what slow LCP is costing you with a Shopify Speed Optimization diagnostic before hiring anyone off this list.
A merchant told us once that they'd already tried two speed apps. Neither made any difference. They assumed speed optimization just didn't work for their store.
It hadn't failed. It had never actually been attempted.
Most Shopify speed apps work entirely within the boundaries Shopify allows an app to touch. They compress images. They minify CSS. They preload fonts. What they cannot do is decide whether an old script buried in theme.liquid should exist at all. They can't understand your business logic, and they definitely can't see three years of app-installation history sitting in your Snippets folder like sediment.
In this store's case, abandoned app code was still loading JavaScript on every single page. A speed app could delay some of that execution. It could not determine whether the files were necessary in the first place. That's the entire irony sitting at the center of this keyword. You search "shopify speed optimization agency," and half the agencies that show up are selling you a tool that adds more of the exact problem it claims to fix.
The Irony Nobody in This Space Admits
Every "speed optimization" listing on Google right now leans on the same handful of claims: Core Web Vitals optimization, image compression, app audits, before-and-after PageSpeed scores. Almost none of them show a real LCP number in seconds. They show a score out of 100, which is a different thing entirely.
A PageSpeed score is a composite benchmark generated under lab conditions. It's useful for spotting opportunities. It is not a user-facing metric. Customers don't experience "a score of 90." They experience how long it takes to see something meaningful on the screen, how fast the page responds when they tap, and whether the layout jumps under their thumb while they're trying to check out. A PageSpeed score can climb from 70 to 95 while the checkout still feels sluggish. You can also improve real load time dramatically without chasing a perfect Lighthouse number at all.
Google's own Core Web Vitals documentation treats Largest Contentful Paint, not a synthetic score, as the metric tied most directly to whether a page feels loaded to a real visitor. That's the number we use to rank every agency in this list, including ourselves.
The Ranking Criteria (Applied to Everyone, Us Included)
Before naming a single agency, here's exactly what each one is scored against. This is the same rubric a skeptical Shopify Plus ecommerce director should hold any agency to, and it's designed so no agency, ours included, gets to grade its own homework without showing the receipts.
1. Documented LCP improvement, in seconds, tied to a named engagement. "Faster load times" is not evidence. "5.4s to 1.4s" is.
2. Liquid-level work versus app-only fixes. Does the agency open your theme code, or do they install a subscription and call it done?
3. Ghost script removal as a named, explicit service. Not "app audits." A specific process for finding dead code from uninstalled apps.
4. iOS Safari and real-device testing. Desktop Chrome hides checkout failures that only surface on a physical phone.
5. Third-party verifiable proof where available: Clutch reviews, published case studies, named clients.
Here's a criterion we won't compromise on, even if it means ranking a competitor above us: does the agency explain why the store is slow before recommending how to fix it? Diagnosis matters more than the fix. The same 5-second LCP can have completely different causes on two different Shopify stores. One might need image optimization. Another might need a Liquid refactor. A third might have 800 milliseconds of JavaScript execution time from third-party apps nobody remembers installing. Applying the same checklist to every store isn't optimization. It's pattern matching, and it's exactly what separates the agencies below that actually diagnose from the ones that just apply the same five fixes to everyone.
Ranked: Shopify Speed Optimization Agencies in 2026
A disclosure up front: Webulux is our own agency, and it ranks first below. We're not going to pretend otherwise, and we're not going to hide it in fine print. What we are doing is applying the same five criteria to ourselves that we apply to everyone else, using only numbers we can actually show you.
1. Webulux
Webulux is built entirely around the premise that speed problems are diagnostic problems first, not app-shopping problems. We don't start an engagement by opening the theme's image folder. We start by opening Chrome DevTools, throttling to Fast 4G, and watching the network waterfall to see what the browser is actually doing before it renders anything a customer can see.
That process is what found 847KB of dead JavaScript on a CPG brand's storefront, abandoned code from apps deleted years earlier that was still executing on every page load. Removing it took LCP from 5.4 seconds to 1.4 seconds and moved the store's conversion rate from 4.3% to 10.1% on the same $15,000 monthly ad spend. The full breakdown, including exactly what the ghost scripts were and how they were traced, is in the CPG brand case study.
Two more engagements follow the same pattern. A gadget brand's LCP dropped from 6 seconds to under 1 second after we stripped a bloated app stack and rebuilt the storefront's Liquid architecture. A lab-grown diamond brand's product pages dropped from 4.8 seconds to 1.3 seconds by fixing how the theme's templates rendered before a single image was ever touched.
What they optimize: theme.liquid architecture, ghost script removal, JavaScript execution order, Core Web Vitals across LCP, INP, and CLS. We explain the full diagnostic-first philosophy in what Liquid bloat actually does to your LCP, since compressing an image on a page with twelve scripts queued ahead of it recovers maybe 200 milliseconds. Removing the scripts recovers seconds.
Best for: Shopify Plus stores spending real money on paid acquisition where a slow storefront is directly suppressing return on ad spend, and where a "we'll look into speed" answer from a previous vendor was never followed by a number.
Why we rank first: every claim above is tied to a published case study with a named before-and-after LCP number, not a composite score. Full methodology is on the Shopify Speed Optimization service page.
2. Fuel Made
Fuel Made has been Shopify-exclusive since 2010, which makes them one of the longest-standing specialists in this space. Their positioning blends conversion rate optimization with speed work rather than treating them as separate disciplines, and their agency history gives them real depth in Shopify Plus migrations.
What's public: long operating history, confirmed Shopify Plus partner status, and a CRO-plus-speed service bundle that signals they think about performance as a conversion lever, not just a vanity metric.
What's not disclosed: no public LCP-in-seconds numbers tied to named engagements, and no explicit description of a ghost script identification process. Their public case studies lean toward conversion and revenue metrics rather than the underlying technical mechanism, which makes it hard to independently verify whether their speed work happens at the app layer or the Liquid layer.
3. Netalico
Netalico focuses on Shopify Plus technical migrations and performance work, which puts them in a similar lane to Webulux: engineering-first rather than design-first. Their specialization in migrations suggests real comfort working inside theme architecture rather than staying at the app-store surface.
What's public: Shopify Plus specialization, technical migration experience, and a performance-focused service line distinct from general design work.
What's not disclosed: no published before-and-after LCP figures we could independently verify, and no stated methodology for identifying dead code left behind by deleted apps. Migration work strongly implies theme-level competence, but the public materials don't connect that competence to a documented speed outcome.
4. Eastside Co
Eastside Co is a UK-based agency with over 500 Shopify builds behind them, which is real volume and a real signal of production experience across a wide range of store types. That breadth is a genuine asset for brands wanting a single vendor comfortable across design, build, and post-launch support.
What's public: high build volume, UK market presence, broad Shopify build experience.
What's not disclosed: at 500+ builds, the portfolio skews toward launches rather than deep post-launch performance remediation. No public LCP targets or ghost-script-specific case studies were available to verify against the rubric above. High build volume is not the same signal as documented speed-recovery work on an existing, live storefront.
5. Craftberry
Craftberry has been Shopify-exclusive for 11-plus years and counts On Running among their named clients, which is a serious credibility signal in this space. Long tenure with a single platform usually correlates with deep familiarity with exactly the kind of legacy code accumulation this article is about.
What's public: over a decade of Shopify-exclusive focus, a named enterprise client in On Running, and long-term platform depth.
What's not disclosed: no published LCP-in-seconds case studies, and no explicit description of how they audit for leftover app code versus simply auditing currently-installed apps. Given their tenure, they've almost certainly encountered ghost scripts on client stores. It's just not documented publicly as a named service or outcome.
6. Command C
Command C, based in North Carolina, positions specifically as a Shopify CRO specialist, which puts speed work inside a broader conversion framework rather than treating it as an isolated technical task. That framing is closer to how we think about the discipline: speed as a conversion lever, not a scoreboard number.
What's public: explicit CRO specialization, Shopify-focused positioning, US-based team.
What's not disclosed: as a boutique specialist, their published case study library is thinner than the larger agencies on this list, which makes independent verification against the LCP rubric harder. Worth asking the diagnostic-first question directly on a discovery call before assuming either way.
The Question That Separates Real Agencies From Speed-App Resellers
If you only ask one question on a discovery call with any agency on this list, including us, ask this: "Have you seen a case where a client insisted a speed app already failed, and the real reason it failed was something a speed app is structurally incapable of fixing?"
A real conversion engineer has a specific story ready. Abandoned app code still loading JavaScript on every page view, invisible to the merchant because Shopify's dashboard shows "app uninstalled" while the theme files still reference it. A speed app can defer some execution. It cannot determine whether an old script should exist at all. That's like reorganizing boxes inside a truck without realizing half the cargo shouldn't be there in the first place.
If the agency's answer immediately jumps to a tool name instead of a diagnostic story, that's the tell. The merchant's original conclusion after two failed speed apps was "speed optimization doesn't work." The actual conclusion should have been: "automation can't remove technical debt it doesn't understand."
What "Working at the Liquid Level" Actually Means
This phrase gets thrown around loosely in agency pitches, so it's worth being concrete. Working at the Liquid level means opening theme.liquid, the Snippets folder, and Section files directly, tracing which included files execute on every page regardless of whether they're needed, and rewriting or removing them. It means running a DevTools Performance recording during an actual checkout flow to identify main-thread Long Tasks, the specific JavaScript execution blocks longer than 50 milliseconds that Google's own documentation on Long Tasks confirms will freeze an Add to Cart button even after the page visually appears loaded.
Working at the app level means installing a tool from the Shopify App Store, letting it run its own diagnostic, and applying whatever fixes that tool is permitted to make within Shopify's app sandbox. Both can produce some improvement. Only one can find and remove the specific category of problem that speed apps are structurally blind to.
Baymard Institute's research puts average ecommerce cart abandonment above 70%. Not all of that is price hesitation. A meaningful share is a browser that stopped responding at the exact moment a customer tried to buy, which no app marketplace tool can diagnose because it never looks past what Shopify's app permissions allow it to touch.
The Diagnostic Sequence We Run on Every Engagement
For merchants wanting to understand what "real" speed optimization work looks like before hiring anyone, here's the sequence, in order, that separates diagnosis from guesswork.
Step one: measure real user performance before touching anything. Core Web Vitals, Shopify Analytics, and conversion data establish where slow performance is actually costing revenue, not just where a page happens to be slow.
Step two: profile the browser. Open DevTools Network and Performance tabs together. Measure JavaScript execution time, Long Tasks blocking the main thread, third-party request count and origin, and waterfall dependency chains. The goal is answering one question: what is the browser actually spending its time doing?
Step three: audit theme architecture. theme.liquid, app embeds, snippets, section rendering, duplicate assets, inline JavaScript, unnecessary CSS. This is where hidden technical debt actually lives, and it's the layer app-based speed tools never touch.
Step four: prioritize by execution cost, not file size. A 20KB script executed synchronously can be more expensive than a 300KB image delivered efficiently. This single mindset shift separates real speed engineering from checklist optimization.
Step five: implement and validate. Remove ghost scripts, defer third-party JavaScript, reduce Liquid complexity, then re-run every baseline measurement. If technical metrics improve but conversion doesn't move, the work isn't finished. That's not a rare outcome. It's a signal to look at checkout-specific friction next.
Get Your Free LCP Audit
The ranking above is public and repeatable. Any of these agencies, including us, can be checked against it. If you'd rather have your own store measured against the same criteria before spending a dollar with anyone, we'll run the diagnostic ourselves: real DevTools waterfall, a theme file audit, and an honest LCP number tied to what it's costing you every month.
Get a Free LCP Audit
See what your speed is costing you. We open your theme, run the DevTools waterfall, and hand you a real LCP number, not a score, before you touch a single image file. Free. 48 hours. No automated scans.
Get My Free LCP Audit →