Hi, @scotttrinh. We have a known issue where there is slow fetching of uncompressed versions of URLs (no gzip/deflate request headers). I believe this is the reason for the slow requests.
The User-Agent header sent to Netlify for the HTTP requests which returned the x-nf-request-id
header 21072030-814a-4cdf-9183-1eda287e2420-1276341
indicates that this request was made by an automated monitor. It had a user agent similar to this (only an example - this isn’t the User-Agent):
user-agent: url-scanner/2.0
I also checked other requests for this User-Agent (the actual one).
I mention this because, depending on the domain being checked, that same `User-Agent is always fast for some other domains hosted at Netlify. However, for your domain is it always 6 seconds or longer.
I suspect there is a setting to request the compressed site version at this is occurring for other sites using the same monitor. Would you be willing to please check if there is a way to change the monitor to requested the compressed version of the URL? This might resolve the timing issue with the monitor service in the meantime while the open issue at Netlify remains.
Again, it is less than ideal that the uncompressed version loads slowly and we do have an issue filed for this. That issue is now cross-linked with this community topic and we’ll post an update here if/when this issue is resolved.
Please note, while the monitor is showing a slow page load, this is not indicative of the page load speed a person’s web browser would experience. A browser will send a request header similar to this:
accept-encoding: gzip, deflate, br
These HTTP requests for people visiting the site (not bots) are unaffected by this issue.
If possible, adding this header above to the automated monitor should cause the monitor to get the fast page load just like a browser would.
If there are other questions about this, please let us know.