What Shopify's Page Speed Upgrade Actually Delivered

Quick Answer: Since June 2025, Shopify has been prefetching whatever your Chrome and Edge visitors are most likely to click next. In August 2026 they added a second layer that shortcuts asset loading on the current page. Both are automatic, and neither one shows up in the PageSpeed score you keep refreshing.

About forty stores. That is how many small Shopify shops I have audited in the last six months, and I can count on zero hands how many of the merchants knew that Shopify had already made their store 228 milliseconds faster on desktop Chrome last spring. Zero. Every conversation still opens the same way it did in 2024: "my PageSpeed score is 47, I don't know what else to try." My job for the first ten minutes is to explain why the number they are staring at has stopped telling them the truth.

What I check first, and what I stopped checking

The reflex is to open PageSpeed Insights and go through the flagged issues one by one. That still has its place. Before I do it on a live merchant call, though, I run three things:

1. Google Search Console > Core Web Vitals report. This is real Chrome-user field data, aggregated over 28 days. It is the number Google actually uses for ranking, and it is almost always kinder than the lab score.
2. WebPageTest with the "Cable" throttling profile, once on desktop Chrome and once with a real iPhone user agent. Same store, two very different pictures.
3. Chrome DevTools > Application > Background services > Speculative loads, then a walk around the site. This tells me whether Shopify's platform prefetching is actually firing for that theme.

The thing I stopped opening in the middle of an audit is the Online Store speed score inside Shopify Admin. That is because it is no longer there. Sometime in early 2026 Shopify removed the score from the admin surface. The r/shopify thread titled "Shopify quietly removed speed from the admin" collected all of one upvote before it was buried, which is roughly the level of noise this change made in the merchant community. If you have been wondering where your score went, the score went nowhere. Shopify just stopped showing it to you.

The two upgrades nobody told merchants about

In June 2025 Shopify shipped platform-wide use of the browser Speculation Rules API. In plain terms: while a shopper is looking at your collection page, Chrome quietly starts fetching the product page it thinks they are about to click. When they click, the HTML is already cached. The click-to-first-paint experience feels instant. Shopify chose the browser's "conservative" eagerness setting at first, which waited for a firm hover before starting the fetch.

In May 2026 they turned the dial to "moderate." Moderate begins prefetching after roughly 200 milliseconds of hover on desktop, and uses a viewport heuristic on mobile. Shopify ran an A/B test on real Chrome traffic across Liquid storefronts and published the median result: TTFB down 285 ms, FCP down 224 ms, LCP down 228 ms. Roughly one in ten measured navigations recorded zero TTFB, because the response was already fully in the cache when the click landed. There were no regressions at any percentile. That is a rare thing to be able to say about any shopify page speed change.

The mobile numbers are much smaller. On mobile the median TTFB shift was about 25 ms and the LCP shift about 24 ms. Browsers are more careful about speculatively fetching over cellular, and Shopify's rules respect that. If your traffic is mostly mobile, the June 2025 change is a nudge, not a leap.

Then, on August 28, 2026, Shopify quietly deployed the second layer: automatic Early Hints. This is a different mechanism aimed at a different part of the load. When a visitor requests a page, Shopify's edge sends a 103 interim HTTP response before the application server has finished generating the HTML, telling the browser "start preloading these render-blocking stylesheets and scripts now." By the time the HTML arrives, the browser has a head start on the files it would otherwise have to wait for. At the 75th percentile of eligible Chrome and Firefox pageviews, Shopify measured FCP 76 ms faster and LCP 100 ms faster. At the 90th percentile, LCP 145 ms faster.

The two mechanisms do not overlap. Early Hints shortens the current page. Speculation Rules pre-stages the next one. For a Chrome shopper walking from homepage to collection to product, the compound effect lands somewhere in the range of 300 to 330 ms of LCP that used to be there and is no longer. That is a real change to the shopify page speed you deliver in the browser, and it happened without a single admin notification.

Why the free upgrade never showed up on your PageSpeed score

I have this conversation four or five times a month, so let me put it on paper.

PageSpeed Insights and Lighthouse both simulate a cold, first-visit load on a throttled mobile device. Neither prefetching nor Early Hints changes what happens on a cold, first-visit load. Prefetching helps the second click and every one after. Early Hints helps the current page only if the browser both supports the 103 hint and gets it in time. Both benefits live in the real Chrome traffic your store is already serving, which is exactly what CrUX measures, and both are invisible to a synthetic lab test. This is why your shopify page speed lab score has not moved even though Shopify's real-user data shows measurable gains across the same population of stores. If you want to see the improvement, you have to look at the Core Web Vitals field data in Search Console, not at the number PageSpeed Insights returns.

This mismatch is the reason Shopify pulled the lab score out of the admin. The score was pointing merchants at the wrong problem in two directions. Their real users on Chrome were often faster than the score suggested, and their real users on Safari were often slower. A single number could not carry that story anymore, so they took the number away. I do not love the decision, because the lab number is still useful as a rough sniff test, but I understand it.

The Safari problem I keep having to explain

Every one of the improvements above is a Chromium story. Chrome, Edge, Opera, Samsung Internet: yes. Safari: no. Firefox: partial, with Early Hints preloads only.

Safari 26.0 shipped in July 2026 with 75 new features, and Speculation Rules support was not one of them. Safari 27 beta, announced at WWDC 2026, lists 525 fixes and no Speculation Rules either. The WebKit team's public position is that a bug fix is in the pipeline; that has been the position since June 2025. As of today it is still the position. If your customer base is heavily iPhone, and for most US and UK direct-to-consumer stores it is, then the June 2025 shopify page speed upgrade delivered close to nothing on your most valuable traffic.

This is the awkward bit I walk merchants through when they ask why their Meta ad campaign to iOS still looks slow. It looks slow because it is slow. That visitor is on Safari, opening your page cold from a tap on an ad. They receive no prefetch. They receive the preconnects that Early Hints sends, but not the preloads. Their experience is roughly what your PageSpeed score suggests. If you want a second pair of eyes on where iOS-specific damage is coming from in your store, that is exactly what help1's expert chat is for, and the first fifteen minutes are on us.

The apps I now uninstall on sight

Two apps I have removed from client stores repeatedly in the last three months: Prefetch Master: Speed Booster and Prefetch - Instant Page Speed. Both sold navigation prefetching as their pitch. Both show zero reviews on the Shopify App Store, which is the market's own quiet verdict. Since June 2025, Shopify does natively what these apps charge for, and does it with less runtime overhead than a third party can, because Shopify's implementation ships as a response header rather than as an app script that has to load, parse, and register listeners.

If you have an app with "prefetch," "speed booster," or "instant page" in the name, open its listing and read what it actually does. If the pitch is navigation prefetching, that is the platform's job now. Uninstall it, then check that the app has not left orphaned Liquid or JavaScript behind, which happens more than it should. If you want a broader sweep of which apps in your store are worth their script cost, help1's diagnostic app pulls a script inventory and flags the ones that no longer earn their place.

I want to be honest about a limitation here. I have not tested every prefetch app on the store, and there is a small chance that one of them adds meaningful prerender behavior on top of what Shopify does. If yours has an active support team and a real changelog since June 2025, ask them what they do that Shopify does not. If the answer is a shrug, delete it.

The one number that would tell you it is working

Open Chrome DevTools, go to the Application tab, and expand Background services on the left. Click Speculative loads. Then click around your own store the way a customer would. You should see a growing list of URLs with a status of Ready or Success. Ready means Chrome has cached the page and is holding it for the click. Success means the click landed on a cached response. If the list stays empty, either something in your store is overriding the Speculation-Rules header, or your session is stuck on a browser that does not support the API. That is the whole test.

None of this fixed the two problems I still see in nearly every audit: a 4 MB hero image marked loading="lazy", and a review-app script that fires render-blocking JavaScript in the head. Shopify did not restructure your asset loading. It did the parts it could do for everyone at once, and it left the parts that require reading your specific store to you. My last shopify page speed audit before writing this had a 42 Lighthouse score and a passing CWV grade in the same week. That is the shape of the gap in 2026. The platform is doing more than the score shows, and the store is still doing less than it could. Our earlier walkthrough of why lab and field scores drift apart on the same store covers the diagnostic mechanics if you want to work the split yourself.

Closing observation

The best platform improvements arrive like weather. There is no launch email, no admin badge, nothing on the dashboard that changes color. You notice the shift when you happen to look up from the score you have been staring at, and mostly you just keep shipping.