1 Answer
- Newest
- Most votes
- Most comments
0
In short, I don't think there's much that we can suggest here other steps to determine where the extra time is being taken.
There are several things that happen during page load:
- The browser/operating system does a DNS lookup for the website. This resolves to CloudFront. Part of this process is determining the closest CloudFront point of presence (POP).
- The ISP/internet routes the traffic to the POP.
- The browser sets up a TCP session which might be for HTTP (port 80) or HTTPS (port 443).
- If using port 443 the encryption parameters are negotiated.
- The browser requests the resource (the initial page) from CloudFront.
- If the resource is not in cache it is retrieved from the origin.
- The browser then repeats this process (steps 1-6) for all other resources that are specified in the initial page.
All of these things take time and additional time at each step can add up very easily. It's possible that JavaScript libraries may do additional work during steps 2-6.
You can troubleshoot the time take for (1) using nslookup
or dig
. You may need to clear the DNS cache on your hotspot or computer in order to do a valid test. Steps 2-6 can be tested using tools such as curl
or wget
. By testing on various networks and with different computers you may be able to determine where the problem is and go from there.
Relevant content
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
The problem was in IPv6 when I truned of it in cloudfront it worked fine.