PageSpeed: Document Request Latency

Pages with resources that redirect, have a slow server response, or do not apply text compression. These can all contribute to latency and reducing page speed.

This audit is a consolidation of three previously separate audits in Lighthouse – Avoid Multiple Page Redirects, Reduce Server Response Times (TTFB) and Enable Text Compression.

How to Analyse in the SEO Spider

To populate this filter the PageSpeed Insights API must be connected via ‘Config > API Access > PSI’.

View URLs with this issue in the ‘PageSpeed tab’ and filter and use the lower ‘Lighthouse Details’ tab to click on the issue on the left-hand side, and see details of the document request latency on the right-hand side.

Bulk export the pages and resources via ‘Reports > PageSpeed > Document Request Latency’.

What Triggers This Issue

This issue is triggered when –

1. Pages contain resources that undergo redirection, causing an additional trip across the network and potentially delaying the loading of the resource by hundreds of milliseconds.
2. Where the browser has had to wait for over 600ms for the server to respond to the main document request. Slow server response times are one possible cause for long page loads.
3. When pages include text-based resources, such as CSS and JavaScript files, that are not compressed, leading to reduced page speed.

How To Fix

Avoid redirects, ensure a fast server response, and enable text compression to improve page load performance.