How to fix Lighthouse page speed FAILED_DOCUMENT_REQUEST error? - pagespeed

I'm trying to improve my websites page speed, Often when I'm using Chrome Lighthouse Audits i got this error:
Lighthouse: FAILED_DOCUMENT_REQUEST. Lighthouse was unable to reliably load the
page you requested. Make sure you are testing the correct URL and that the
server is properly responding to all requests. net::ERR_ACCESS_DENIED.
IMG URL-> https://i.imgur.com/Qenyvqj.png
I tried to figure what is the problem but i didn't find answer.
My websites hosted on AWS, including valid SSL and the page speed is standing between 85-95.
Any ideas?
I tried to find some good answers in Stackoverflow, Incognito mode, Audits Chrome, Chrome Extention.. Still getting this error..

I had this problem and tried 1 day to fix it.
Apparently, the issue was with my MX domain records.
If you encounter this problem and land here looking for a result, do a DNS check for your domain before looking for blocked IPs from your servers and others.

Related

TTFB very long first time you access the website

I have an issue with a WordPress website I made: https://j-martini.com
Sometimes (generally the first time you access the website), the time before even HTML gets loaded can be very long (for example on this capture, 8s: https://postimg.cc/qgR0xqKm
I have no idea where the issue is coming from and since every time I test the website with tools such as GTmetrix I get a good result, I don't how to monitor the issue.
I contacted my hosting service, Scaleway, because I'm suspecting a slow server, but they're trying very bad to not help me at all. Even if it doesn't come for the server I kind of hoped that they could help me figure out where the problem is, but apparently not.
Any help would be very appreciated!

Error when accessing Firebase hosted sites saying "your computer or network may be sending automated queries"

I shared a link with someone to a firebase site that I was hosting, and it worked for some time, but then all of a sudden they said they were getting the message:
We're sorry... ... but your computer or network may be sending
automated queries. To protect our users, we can't process your request
right now. See Google Help for more information.
I was also getting it, and started checking my other firebase hosted sites and started getting the message on all of them. I didn't understand. I couldn't find a common link to understand why it was happening. So many sites linked it to a reCAPTCHA problem, but my sites don't use reCAPTCHA...
I found this link:
GitHub forum Link
The user recommended making sure the url started with "https". As soon as I typed my url with "https://" at the start, everything came up. At that point, I tried all the other URLs, and they worked too. This may be a rule for all Google-related sites.
I'm not sure if it's relevant that Chrome often trims the url in the "omnibox" or address bar, hiding the protocol, making it easy to miss when copying/pasting? E.g. :
Note, I tried accessing these pages without https (by typing "http://") but my browser now seemed to correct it and force it to be "https://", so I couldn't replicate the problem again.
I don't know exactly why it started, but I know that I wish I found this information sooner, because it was very frustrating, and the info out there wasn't helpful, except for the link I posted above. So hopefully, when someone like me searches for "firebase" and the error text "your computer or network may be sending automated queries", they might see this and possibly be saved a headache.

IIS 8.5 "Connection was reset" Error on Chrome When Posting, but Works For Get Requests

I have been working on an intranet site and recently users have been complaining that when they save a change they get "This site can’t be reached." The users are using Chrome exclusively as far as I can tell, and when I tested with Edge, I got no errors. So, I first tested on the web server, I was unable to recreate the issue. I tried on another server within the network and I was also unable to recreate the issue. I then tried my pc, which was connected through a VPN and was finally able to recreate the issue. What is weird is that this just started happening and I haven't updated the site in quite awhile. The can view most pages and the issue only seems to happen when posting to IIS. At this point, I am not sure where to start to troubleshoot this issue. Any help would be appreciated.
Edit: Updated the title to show the actual error I got.
Edit 2: Someone put me on to checking the httperr log and I see an error for the post request with client_reset as the error message. hope that makes the issue a bit more clear.
I found the issue with help from the network security firm the client was using. Once I was able to confirm the issue only occurred when clients who were using a VPN, he ran some tests. The issue was that the firewall was blocking posts that seemed suspicious. Now, this site has been running for years with no issues. My assumption is that they made some security changes and it caused this problem. What was odd, was that I tried a few fixes and they would work for a few times and then would stop working, such as using the site ip address versus the domain name. I hope this helps the next person.
Wade

Can't navigate through ASP.NET website while Jmeter recorder is running

The title pretty much says it all. When I'm running HTTP(S) Test Script Recorder, one particular page becomes unresponsive - when I click on something it just reloads. The recorder itself is working fine, it is recording every step. And the problem is not proxy related. I've successfully recorded other pages of the same website. When I'm not recording, there are no problems.
It's a .NET 3.5 project.
The page itself has a lot of forms, file uploads, etc, but as far as I know, it should not interfere with recording or even more - with browsing the page. When debugging the project, no breakpoints are hit, so I assume that something gets lost before reaching the server.
Browsers that I've tried: tried FF, Chrome, Edge, IE.
Tried recording the web locally and online. Same thing.
Played around (reinstalled and whatnot) with certificates, didn't help.
Has anyone encountered such a problem? What could be done to fix this? I'm more interested in finding the solution, than a way around (blazemeter, badboy). Any help would be very appreciated.
EDIT: I tried recording with blazemeter and it worked. But when looking at view results tree I noticed that the request path and parameters don't change, even when in the HTTP Request Sampler they are different. So there's no solution yet
This often happens to me and what I've found is that JMeter changes the root certificate in the bin folder every week. So usually the HTTP traffic is fine but certain HTTPS traffic won't work. So make sure that your browsers are seeing the latest JMeter certificate and not using an old one that doesn't exist anymore. On Windows, Chrome and IE use the certificates in Internet Options, while Firefox needs to have it added to it manually.
It turns out that in Test Script Recorder HTTP Sampler Settings choosing Type: Java was all that was needed. I suspect that the issue was related to file upload being involved.

asp.net site demo over webex, weird issues seen

Our customer experienced multiple errors on a demonstration to a customer of theirs.
The site is asp.net 3.5 based and has been running pretty well lately. They said 2 hours later site was ok again... (needless to say they are not happy)
The traces in the health log look very weird, it appeared to be as if incomplete pages were returning to the server for processing..
A fair of of the errors were errors generated by scriptresource.axd with bits of the page source showing up as part of the url... very very odd. I'd never seen this before...
I was talking to their lead tester who then told me this only happened during a webex (cisco sharing product) demo and was fine after...
Is it possible the webex session could have impacted the site http stream between client and server...
This is a known IE8 issue. I bet you will see Trident/4.0 for all "broken" requests in the user agent field. (Google for "IE8 4K bug")
You can either run a different browser or appply the latest IE8 patch (this issue has already been fixed)

Resources