Shopify Liquid streaming: what the 29% first-byte improvement means for your theme

Shopify has changed how eligible Liquid storefront pages reach a shopper’s browser. Its 22 September 2026 performance report says time to first byte fell by about 29% at the 75th percentile for the median store. The practical question for merchants is whether their theme turns that earlier response into something customers can see sooner.

Shopify reported smaller improvements of 2–6% in first contentful paint and largest contentful paint. The headline figure therefore should not become a promise that every page finishes loading 29% faster. These are Shopify’s rollout measurements, not results from an independent test of your store. Read Shopify’s performance report.

What your theme needs to qualify

The platform sends the beginning of a page while it is still assembling the remaining sections. That lets the browser start fetching resources earlier. Eligible pages receive streaming automatically; merchants do not need to install an app.

According to Shopify’s platform documentation, pages currently need JSON templates and an unmodified {{ content_for_header }} output inside the document’s head. Pages using older .liquid templates do not yet qualify. Neither do theme previews or the theme editor.

For a custom theme, ask the developer to check the layouts used by your main product and collection pages. A homepage-only check could miss the pages receiving your paid traffic.

The useful change is in resource order

Shopify’s first-paint resource guide recommends placing critical stylesheet links, font declarations and other initial-view resources before content_for_header. Resources listed afterwards arrive later and cannot use the same head start.

Ask for a dependency review before rearranging code. Scripts that immediately read Shopify.* can break if moved too early, and changing stylesheet order can alter which styles win. Keep the required header output intact rather than wrapping or filtering it.

A sensible brief for your developer is small: identify the critical resources, check their dependencies, make the smallest justified change, and review the affected pages. This does not justify a wholesale theme replacement on the strength of a platform benchmark.

Measure the storefront people actually use

Shopify’s testing guidance separates real-user measurements from controlled lab tests. Use your Web Performance Dashboard to establish a baseline by page type and device, use lab tools to investigate changes, then confirm the result in visitor data.

Record product and collection page performance before any theme work. After normal preview checks for layout and behaviour, verify the streaming effect on the live theme; preview performance cannot establish whether streaming helped. Keep largest contentful paint, interaction responsiveness and layout stability in the review alongside first-byte timing.

The decision to approve more optimisation work should rest on the remaining customer-visible problem: slow product imagery, delayed content or unstable pages. An improved first-byte number is useful evidence, but it is only one part of that decision.