Shopify Document Request Latency: Fix the PageSpeed Warning (2026)

Quick Fix with Thunder

What Document Request Latency Measures

The document is the first HTML response for the page. Before the browser receives it, it cannot discover your theme CSS, hero image, preload hints, product images, app scripts, or fonts. That makes the first request the gatekeeper for the entire load.

Chrome's document request latency insight points to three broad issues: redirects, slow server response, and missing compression. Screaming Frog also describes it as a newer consolidation of older Lighthouse audits around redirects, TTFB, and compression.

On Shopify, compression and hosting are platform-managed. Your useful levers are storefront configuration, theme code, app behavior, and URL hygiene. Treat the warning as a diagnosis prompt, not a reason to move off Shopify.

What You Cannot Control on Shopify

This distinction matters. Generic advice about upgrading servers, changing databases, or adding nginx rules is not Shopify advice. Focus on the work that changes the initial storefront response and the resources discovered immediately after it.

Step 1: Remove Redirect Chains

Redirects are the easiest document latency fix because each hop delays the real HTML. Common Shopify chains look like this:

http://example.com
  -> https://example.com
  -> https://www.example.com
  -> https://www.example.com/en
  -> https://www.example.com/en/collections/all

Fix the source link so it points directly to the final canonical URL. Update ad URLs, email links, navigation menus, sitemap URLs, and old campaign links. Shopify's URL redirects are useful for SEO preservation, but they should not sit in the path for your most important landing pages.

Use the Shopify 301 redirects speed guide to audit and clean old chains without breaking inbound links.

Step 2: Audit Geolocation and Currency Redirects

Currency, language, and market-selection apps often redirect the first request based on IP, cookie, or browser language. That can create a slow document request even if Shopify's platform response is fast. The worst pattern is redirecting every new visitor before showing any HTML.

Prefer banners or selectors over automatic redirects where possible. If you must redirect, make sure it happens once, lands on a canonical URL, and does not bounce between app logic and Shopify Markets.

Step 3: Move Third-Party Scripts Out of the Head

Scripts in theme.liquid do not usually delay the HTML bytes themselves, but they can make the document look slow in PageSpeed because they are discovered immediately and compete with critical resources. Move non-critical widgets below the first render and defer scripts that are not needed for the initial viewport:

<!-- Before: blocking script in head -->
<script src="https://example-widget.com/widget.js"></script>

<!-- After: defer and load only where needed -->
{% if template.name == 'product' %}
  <script src="https://example-widget.com/widget.js" defer></script>
{% endif %}

For deeper cleanup, use the third-party scripts guide, network payload guide, and main-thread work guide.

Step 4: Simplify Heavy Liquid Before the First Byte

Shopify renders Liquid server-side. Most Liquid is fast, but giant nested loops, broad collection scans, dynamic menus, and app snippets that compute too much on every request can make the document slower. Look for homepage sections that loop through huge collections, render hidden carousels, or include product cards that are not visible above the fold.

{%- comment -%}Avoid rendering dozens of hidden cards on first load{%- endcomment -%}
{%- for product in collection.products limit: 8 -%}
  {% render 'card-product', product: product %}
{%- endfor -%}

Lazy-render below-the-fold sections where possible, limit loops, and remove old app snippets left behind after uninstalling apps. If you are not sure where the theme is slow, start with our Shopify Liquid optimization guide.

Step 5: Debug with DevTools and WebPageTest

In Chrome DevTools, open Network, disable cache, reload, and click the first document request. Compare Redirect, Waiting for server response, and Content Download. If Redirect is high, clean URLs. If Waiting is high only in one region, retest from another location. If Content Download is high, inspect document size and compression assumptions.

WebPageTest is useful because it shows connection timing, redirect hops, and repeat-view behavior. Pair those results with the speed test results guide so you do not overreact to one noisy PageSpeed run.

Manual Fix vs Thunder Fix

FAQ