Hi, @TORQ, and thank you for reporting this, which I believe is the same issue reported here:
It is important to note, this only affects uncompressed HTTP requests which many command-line tools (wget, curl, etc) use by default. As people’s web browsers will always request compressed versions of assets, this won’t affect real visitors, only certain “bots”, scripts, and/or automated monitors.
Please feel free to test this with compression enabled and I don’t think you will see any delays. For example, without compression:
$ time wget -q https://5e1c73420f92978cbf1a5f68--torq-dot-tech.netlify.com
real 0m6.389s
user 0m0.018s
sys 0m0.010s
And with compression:
$ time wget -q --header='Accept-Encoding: gzip' https://5e1c73420f92978cbf1a5f68--torq-dot-tech.netlify.com
real 0m0.148s
user 0m0.020s
sys 0m0.010s
We have this topic cross-linked to the open issue and we’ll follow-up here with an update if/when the issue with uncompressed requests is resolved. Be assured though, your site visitors will be unaffected in the meantime.
If there are any questions, we’re happy to answer.