Read more about the different throttling methods and the impact they have. This is more realistic, but tests also take more time and show more variance between individual test results. Other tools like DebugBear throttle the local network connection at the operating system level, delaying each network packet as it arrives on the test device. Here the browser introduces a delay to each network response. If you run Lighthouse in Chrome DevTools you can choose between simulated throttling and browser-level "applied" throttling. This is the default setting for Lighthouse. PageSpeed Insights loads the page on a fast connection without any throttling, and then simulates how the page might have loaded on a slower connection. However, there are multiple different ways of throttling the connection. For mobile devices, this connection uses a bandwidth of 1.6 Mbps and 150ms server round-trip time. To achieve realistic and consistent results, Lighthouse uses a throttled network connection to test pages. If you run Lighthouse on your own computer, then the test results will always show how a user in your location would experience the website. Web.dev tests used to always run in the US, but now match the PageSpeed Insights behavior.ĭebugBear tests pages from a server in South Carolina by default, but can run tests from 10+ locations. PageSpeed Insights picks the server to run the test from based on your current location.
If you live in the UK, opening a website that's hosted on a server in London will be faster than opening one that's hosted in New York.
0 kommentar(er)
