As with any performance problem , the first step is simply to profile. There are a lot of great tools for profiling web pages.
On your own machine you can use the Chrome , Firefox and Edge profilers. These can give you an idea of how much time is spent in various stages of the page load, from network requests to JavaScript execution.
Sometimes performance will vary wildly from one browser to the next because of implementation differences. You can use these browser dev tools to emulate slower connections , so you can see what some of your users might be experiencing. Pretending to be on 2G is a fun one. Make sure you test your page with static resources both uncached and cached. You can also use tools like webpagetest to see what page loads are like from different browsers and different places around the world. On top of that, strongly consider logging page load times for your users.
But careful when interpreting results: these APIs measure many different stages of your page load. Make sure you figure out which event actually lines up with when the user can view or interact with your page. This user data will let you see the actual performance real users are experiencing and help you get a breakdown of where time is being spent. Logging will help you home in on problems by looking at which countries, browsers, and devices are suffering.
Some teams find it helpful to log performance metrics on every commit or run perf tests on every commit to identify degrading performance quickly. After your profiling, you probably have a good idea of which metrics you need to track and log for each commit: bytes of JavaScript, number of images, etc.
Your profiling information should already have revealed to you where to get started. There are lots of small changes that can speed things up: remove redirects , preconnect to the CDN , etc. For many web pages, the main thing you can do to make your website faster is load less stuff.
Google recommends you keep your page weight to 1 megabyte uncompressed. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 2 years, 10 months ago. Active 2 years, 5 months ago. Viewed 4k times. Improve this question.
Add a comment. Active Oldest Votes. Only removing the "cache" option for 'Clear-Site-Data' header should fix the problem. I also have no idea why. Improve this answer. You should also check the download speed of your internet connection. You can use an online speed checking tool such as SpeedTest. If you notice an unusually low download speed, soft-reset your router and see if that helps.
If you have any other applications that eat up large amounts of bandwidth, pausing them can help improve download speeds in Chrome. You can use the Resource Monitor on your PC to figure out network-intensive apps and services. To bring it up, right-click the taskbar and select Task Manager. Then, select More details , switch to the Performance tab, and choose Resource Monitor.
You should find a list of apps under the Network tab. If you have other devices connected to the same network, you should pause download activities in them as well. If you use a VPN , you end up trading network performance for privacy.
Even top-notch VPN service providers impact your internet speed. Try switching off your VPN and check if that makes Chrome perform downloads faster. That should help fix any bugs or glitches preventing Chrome from working optimally.
The browser does install new updates on its own eventually, but you can open the Chrome menu, point to Help , and select About Google Chrome to apply them even faster. Chrome extensions can create conflicts that result in slow file downloads. Try disabling them. To do that, select the Extensions icon to the top-right of the Chrome window and select Manage Extensions. Follow by turning off the switches next to each active extension.
If that helped improve the download speed, reactivate the extensions one by one until you figure out the one causing the issues.
0コメント