How to Investigate a Slow First Response
Website intelligenceHow to Investigate a Slow First Response
When a page takes a long time to begin loading, investigate the request path before changing images or CSS. The first response is affected by the server and routing, which are different from the browser work that happens later.
Confirm the request is reaching the intended page
Check the requested URL, final URL and HTTP status. An unexpected redirect or access challenge can add delay before the actual page is reached.
Repeat the request under comparable conditions and note whether the delay affects one URL, a group of pages or the whole domain. This helps distinguish a page-specific issue from an infrastructure pattern.
Review SiteBoost response-time context
SiteBoost records response time and status where available. Use those values to identify pages that need a closer server-side investigation, and compare them with Lighthouse-based performance data separately.
If the server response is consistently slow, ask the infrastructure owner to inspect hosting, caching, database work, redirects and server logs. Do not assume the fix is to compress images when the delay occurs before the HTML arrives.
- Confirm final URL and status.
- Compare several representative URLs.
- Investigate caching and server work if the delay repeats.
- Use a browser trace for the later rendering stages.
Measure again after the server change
After changing server or caching configuration, repeat the request and rescan the same URLs. Record the conditions so the comparison is fair.
A faster first response is useful, but still review the rest of the page experience before calling the performance work complete.
