The secret is out.
Shopify just made Liquid storefronts significantly faster.
According to Shopify’s performance team, Time to First Byte dropped by around 29% at p75 for the median store, with a 21% improvement at p90.
And merchants didn’t need to rebuild their themes.
No migration.
No move to Hydrogen.
No headless rebuild.
No code changes required.
Shopify changed the infrastructure underneath the storefront.
Read Shopify’s technical announcement
And the bigger story isn’t really the 29%.
It’s what this says about the future of Liquid vs headless Shopify.
What Did Shopify Actually Change?
A Shopify Liquid page contains two very different kinds of work.
The <head> generally contains things such as:
CSS files
Font declarations
Preloads
Meta tags
Scripts
Connections to third-party resources
Then the rest of the page contains the sections, products, blocks, metafields and Liquid logic that need to be rendered.
Previously, the browser had to wait longer before it could begin working with that response.
Shopify has now changed the rendering process so that everything before {{ content_for_header }} can be sent to the browser earlier while Shopify continues rendering the rest of the page.
Instead of:
Shopify renders → browser waits → browser starts
you increasingly get:
Shopify renders + browser starts working at the same time.
The final HTML is effectively the same.
The browser simply receives useful information earlier.
That means it can start downloading CSS, fonts and other critical resources while Shopify is still finishing the page.
Shopify Reports a 29% TTFB Improvement
Across storefront pageviews, Shopify measured approximately:
29% lower TTFB at p75 for the median store
21% lower TTFB at p90
Shopify also measured improvements of roughly 2% to 6% in FCP and LCP, depending on the theme.
That distinction matters.
TTFB measures how quickly the response begins arriving. It isn’t itself a Core Web Vital.
Metrics such as Largest Contentful Paint are closer to what the customer actually experiences.
Google describes TTFB as a foundational performance metric because delays there can affect everything that happens afterwards.
Google’s guide to Time to First Byte
So Shopify isn’t simply making a benchmark number look better.
By getting useful resources to the browser earlier, it can give the browser more time to prepare the page customers are about to see.
This Isn’t Shopify’s Only Recent Performance Update
This update becomes more interesting when you look at what Shopify has been doing throughout 2026.
In August, Shopify improved its implementation of Early Hints.
Instead of depending only on resource hints added manually by theme developers, Shopify can analyze generated storefront HTML and identify critical resources automatically.
Shopify reported improvements of:
76ms faster FCP
100ms faster LCP
for eligible pageviews at p75.
Again, merchants didn’t need to change anything.
Shopify’s automatic Early Hints update
Shopify has also been improving speculative loading.
When the browser believes a shopper is likely to click a link, it can begin preparing that next page before the actual navigation happens.
Shopify’s Speculation Rules update
Look at all of these changes together and the direction becomes pretty clear.
Shopify isn’t abandoning Liquid.
It’s making Liquid faster.
And That Changes the Headless Conversation
For years, performance has been one of the arguments used to justify moving away from a traditional Shopify storefront.
The pitch often sounded something like:
Liquid is slow. Let’s go headless.
Build the frontend in React.
Use Next.js or Hydrogen.
Control the rendering.
Control the API calls.
Control everything.
There are absolutely situations where this makes sense.
We build and work with more advanced Shopify architectures at MoonImpact, and some projects genuinely require the additional flexibility.
If you’re considering that architecture, we’ve already broken down what changes when you move away from Shopify’s traditional theme layer:
Headless Shopify Development: What You Can Do With and Without Shopify Plus
But there is an important difference between:
“We need headless because our architecture requires it.”
and:
“We need headless because Liquid isn’t fast enough.”
That second argument is becoming much harder to make automatically.
A Good Liquid Storefront Can Already Be Very Fast
Liquid isn’t necessarily the reason a Shopify store is slow.
Very often, the problems are sitting somewhere else.
Too many apps.
Five different analytics platforms.
Huge JavaScript bundles.
Poorly optimized images.
Autoplay videos.
Third-party widgets.
Duplicate libraries.
Apps injecting scripts on every page.
Unnecessary tracking.
Badly structured Liquid loops.
Rendering functionality with JavaScript that could have been rendered directly in HTML.
Changing the frontend framework doesn’t automatically solve those problems.
You can build an extremely fast React storefront.
You can also build an extremely slow React storefront.
Headless is an architecture choice, not a magic speed button.
Shopify’s own theme performance documentation recommends focusing on things such as Liquid complexity, LCP images, JavaScript execution, critical resources and third-party scripts.
Shopify theme performance best practices
Theme Architecture Matters Even More Now
One detail from Shopify’s announcement is especially interesting for developers.
Not every theme received the same improvement in visible performance.
Shopify compared two of its themes: Dawn and Horizon.
TTFB improved substantially on both.
But Horizon converted more of that advantage into improvements in FCP and LCP.
Why?
Because more of its important first-paint resources were located before {{ content_for_header }}.
That allowed Shopify to send them to the browser in the first streamed part of the response.
The browser could then start working while Shopify continued rendering the page.
This means the platform improvement doesn’t make theme development irrelevant.
It actually makes good theme architecture more valuable.
Shopify now explicitly recommends loading critical first-paint resources before content_for_header where technically appropriate.
Platform Speed + Good Theme Development
This is where things become interesting for Shopify developers.
Shopify can improve the infrastructure.
But the theme still determines what happens after that.
A fast Shopify storefront is still about:
Lean Liquid
Efficient loops
Controlled JavaScript
Proper image loading
Minimal third-party dependencies
Smart font loading
Correct LCP prioritization
Careful app integration
Good mobile performance
At MoonImpact, that’s how we approach our Shopify Plus development work.
The goal isn’t simply to make a Lighthouse screenshot look green.
The goal is to build a storefront that stays maintainable and fast as more products, campaigns, apps and functionality are added.
Apps Can Still Destroy a Fast Theme
There is another part of the conversation that gets overlooked.
You can start with an extremely fast Shopify theme and gradually destroy its performance by installing applications that inject scripts everywhere.
That doesn’t mean Shopify apps are bad.
It means storefront applications need to justify the resources they load.
A product recommendation tool, motion experience, analytics integration or custom functionality can absolutely be worth the performance cost.
But that cost should be understood.
This is also why our Shopify app development work considers storefront performance as part of the implementation rather than treating the app and theme as completely separate systems.
Shopify itself recommends auditing storefront scripts and removing scripts that aren’t earning their performance cost.
So, Does Your Shopify Store Actually Need Headless?
Sometimes, yes.
You may have a sophisticated content platform.
You may need an unusual frontend architecture.
You may operate multiple commerce systems.
You may need extremely customized interactions.
You may be integrating Shopify into a much larger technology stack.
You may have requirements that simply don’t fit comfortably into the Shopify theme architecture.
Those are legitimate reasons to investigate headless.
But speed alone?
Before rebuilding your entire storefront, test what you already have.
Audit the theme.
Audit your apps.
Audit JavaScript.
Measure Liquid rendering.
Look at Core Web Vitals.
Check the LCP element.
Check what third parties are loading before the customer sees the page.
Optimize the existing architecture first.
You may discover that Shopify Liquid wasn’t the bottleneck.
Liquid Performance Still Depends on Your Code
Shopify’s platform improvements don’t mean developers can stop thinking about performance.
Shopify specifically warns about expensive Liquid patterns such as deeply nested loops, repeated metafield access and unnecessary product or variant iteration.
Small improvements compound on complex themes.
Shopify estimates that applying multiple Liquid optimization patterns on a complicated storefront can save 25–50ms of TTFB.
Shopify’s Liquid performance optimization patterns
So you effectively have two layers of optimization happening.
Shopify optimizes the platform.
Developers optimize what runs on top of it.
The better both become, the less sense it makes to replace the entire architecture simply because somebody said headless is faster.
Shopify Is Making the Default Stack Harder to Beat
And this may be the most important part of the update.
Shopify could focus entirely on Hydrogen and headless commerce.
Instead, it continues investing heavily in its native storefront stack.
That matters because Liquid gives merchants something developers sometimes underestimate:
simplicity.
The Theme Editor still works.
Sections still work.
App Blocks still work.
Marketing teams can change pages without deploying a frontend application.
Most Shopify apps integrate naturally.
The ecosystem works around the same architecture.
Deployment is simple.
Hosting is handled.
Infrastructure is handled.
Shopify keeps improving the platform underneath it.
If you can get excellent performance while keeping all of those advantages, the threshold for choosing headless becomes much higher.
The Bigger Update Isn’t 29%
The headline is:
Shopify Liquid storefronts now start loading 29% faster.
But that’s not the most important part.
The bigger message is:
Liquid isn’t going anywhere.
Shopify is continuing to improve the technology powering millions of its storefronts.
And every time Shopify makes the default architecture faster, the question changes from:
“Why aren’t we headless?”
to:
“What problem would headless actually solve for us?”
That’s a much better question.
Before rebuilding your entire Shopify architecture, make sure you’re solving a problem that actually exists.
Because sometimes the fastest architecture is the one you don’t need to replace.