Skip to main content
HostTracker
HostTracker
website monitoring service
Status pages Instant check Price
Login Register

Website speed test

If you need to run a website performance test, a hosting speed test, a page speed test, or some other type of performance and stability check, this tool has you covered

Examples: 300+ locations worldwide · results in about 10 seconds

You've used today's checks

Start the 30-day trial Already have an account? Log in
{{error.message}}

Unlock the full report

30-day free trial · cancel anytime

Loading plans…
See all plans & pricing
Recommended
{{ plan.name }}
{{ money(priceMo(plan)) }}/mo
  • 1 website · all monitoring types
  • {{ plan.maxTaskCount == null ? 'Unlimited' : plan.maxTaskCount }} monitored sites
  • All check locations in the report
  • TLS, headers & timing details
  • Scheduled reports
  • REST API access
Start the 30-day trial
Billed only after your trial · Compare all plans

Need this every few minutes? Page speed monitoring re-runs the same real-browser load from the locations you choose and alerts you when load time crosses your budget.

Why it is important to test website speed

According to statistics and research data, a site load speed must be around 2-3 seconds. So to check page speed is especially vital if the resource’s development highly depends on SERP ranking, because the longer loading slowdowns are, the higher chance the site ratings will significantly drop, causing financial and reputational losses for business.

Find out more

Real-time page speed test

With our powerful tool you will be able to easily test website speed as well as separate website page speed or even loading speed for performance and determine where the problem is without any delays. Our site speed checker provides a constant monitoring of the hosting and website loading speed with up-to-the-minute updates. As a result it will greatly help webmasters with maintaining stable performance of the resource

Find out more

Worldwide website speed checking

HostTracker platform allows to check website speed from different locations to check location-related slowdown issues. It allows to improve the website loading speed situation for particular groups of users if there are problems on a regional scale. It is possible to run site speed test multiple locations around the world to provide worldwide coverage for website speed monitoring and network optimization and implementation of CDN services

Find out more

User-friendly site speed test tool

HostTracker platform is user-friendly and it is easy to start using the provided website speed testing tool from the get-go. Its dashboard is highly intuitive and relatively easy to navigate so website speed tool setup and configuration interface is easily understandable even for novices. With such a simple and functional design it will be easy for everyone to set up and check website speed

Find out more

Web page speed test tool features

Our platform provides access to automated monitoring of speed test website. Users get an instant notification system for the test page speed tool and other checks. This system informs about any emergency situations occurring in the process of website test speed checking. It sends a message via messenger app, email service or SMS. Logging and in-depth analytics for the website page speed test tool and possibility to browse through the history of pagespeed checks. We also provides possibility to perform mobile page speed test

Find out more

Want to see this trend over time, not just once? Set up page speed monitoring

Key takeaways

  • This tool loads the page in a real browser from the location you pick and records every request the page makes, with the time each one took to download and execute.
  • You can test as a desktop or as a mobile device, and the waterfall shows which resource, script or third-party request is holding the page up.
  • You choose the city the test runs from, or let it pick one at random, so you can compare how fast the page loads in different parts of the world.
  • It is free, needs no login and no credit card.
  • For continuous checks, see the page speed monitoring page.

Frequently asked questions.

It is the same page load measured from more than one place, so you can see where the page loads slowly instead of guessing from a single result. Each run of this tool loads the page in a real browser at one checkpoint - in the city you pick, or a random one when you leave All world selected - as a desktop or as an emulated mobile device. Run it from a few regions and compare the times. To repeat it automatically, page speed monitoring runs the check on a schedule and alerts you when load time crosses your budget.
Enter the page address, choose a device and a location, and click Check. A real Chromium browser opens the page with an empty cache and no cookies, records every request the page makes and waits until the network goes quiet, for up to 20 seconds. The report then shows how many requests succeeded or failed, two load times, a waterfall of every request, the slowest resources, screenshots taken while the page loaded, and the browser's CPU and memory use.
One bar per request, on a shared time axis that starts with the first request. Each bar is split into phases: Queue (waiting inside the browser), Proxy, DNS, Con (opening the connection), SSL (the TLS handshake), Send, Head (waiting for the response headers) and Body (downloading the content). Two vertical lines mark the load times from the summary. A staircase of bars usually means requests that can only start after an earlier one finishes; a single long bar is one slow resource.
Start with the Top 10% slowest resources table. It ranks requests by their time without the browser queue, then by size, and shows each one's status, size, start and end. Statistics by domain tell you whether the time goes to your own server or to third-party hosts such as analytics, ads or chat widgets, and Statistics by content type show whether scripts, images or stylesheets carry the weight. Failed resources and console errors are listed separately.
Usually for one of a few reasons, and the report shows which:
  • the server answers slowly - a long Head phase on the first request
  • the page is heavy - large images or scripts with long Body phases
  • too many requests, or requests that wait for each other
  • a slow third-party host, visible in Statistics by domain
  • scripts keeping the browser busy - high CPU usage during the load
If the first request is the slow one, start with checking server response time.
Your own browser keeps most of the site in its cache, so a reload fetches only a few files, and you may sit close to the server. This test starts every run with an empty cache and no cookies, the way a first-time visitor arrives, and it runs from the checkpoint you choose, so distance, a slow route or a struggling CDN edge in that region shows up in the times. Test from the regions your visitors come from and compare the DNS, Con and SSL phases.
Mobile emulation changes the browser, not the connection. The test takes the chosen device's screen size, pixel density, touch support and user agent, while the network stays the same as for a desktop run, which uses a 1024 x 768 window. So the difference comes from what your site sends to that device: a separate mobile page, other image sizes, more or fewer scripts. Run both tests from the same location, then compare Total requests and the size columns.
Download time runs from the first request to the moment the browser fires the page's load event. Page load time without XHR runs until the last request that is not a background XMLHttpRequest call has finished, so images and scripts that arrive after the load event still count. If the page has not reached its load event after 20 seconds, the test stops and reports a timeout instead.
Below the summary, a scale from 0 to 100% places your page load time against the load times of other sites checked with this tool. The marker shows roughly what share of them loaded more slowly than your page. Treat it as a sense of scale; comparing with your own earlier runs from the same location and device tells you more about whether a change helped.
Run it after every change that can affect load time - a deploy, a new plugin or theme, a new third-party script, a move to another host or CDN - and compare with a run made before the change from the same location and device. Load times also drift with traffic and with third-party hosts you do not control, which an occasional manual test can miss; a scheduled monitor catches that drift as it happens.

Part of HostTracker's website monitoring software.