Pingdom Tools: the website speed test explained
Page Speed & TTFB Test
Free, no sign-up. We only fetch the public URL you enter.
Short answer
Pingdom Tools is the free website speed test from Pingdom, a SolarWinds product, at tools.pingdom.com. You enter a URL, pick a test location and get a performance grade, load time, page size, number of requests, improvement suggestions and a waterfall chart that shows every file the page loads with its DNS, connect, SSL, send, wait and receive times. Use it to find heavy or slow files, too many requests and slow third parties; run it several times from the location nearest your visitors. The free test above is an independent alternative for the server part: DNS, connection, TLS, time to first byte and HTML download from Germany.
- Free, no sign-up: grade, load time, size, requests, waterfall.
- Choose a test location close to your audience.
- The waterfall shows which files and servers slow the page down.
“Tool ping dom”, “pingdom tools”, “pingdom speed test”: many people look for the same thing, the free speed test that Pingdom has offered for well over a decade. It is popular because it is simple: one URL, one click, and you see how long a page takes, how big it is and which files slow it down. This page explains how to use Pingdom Tools, how to read each part of the result, especially the waterfall, how it differs from Google PageSpeed Insights and other testers, and how to check your server’s response time with the free test above. This page is independent and not affiliated with Pingdom or SolarWinds.
What Pingdom Tools is
Pingdom is a website monitoring service owned by SolarWinds. Next to its paid uptime and synthetic monitoring, it offers a free website speed test at tools.pingdom.com, widely known simply as Pingdom Tools. The test loads a page in a browser from a location you choose and records every request, how long each step took and how large each file was.
It does not need an account and is often the first tool web developers, agencies and site owners reach for when a page feels slow, because the results are easy to understand and to share.
How to run the test
Enter the full URL of the page, including https and the correct hostname, because a redirect from http or from a different hostname adds time and changes the result. Select the test location closest to most of your visitors; the service offers locations in several regions of Europe, North America, South America, Asia and Australia. Start the test and wait a few seconds.
- Enter URL Full address with https
- Pick location Close to your visitors
- Start test Page loads in a real browser
- Read results Grade, size, waterfall
Run the test at least three times and compare. The first run may hit empty caches on your server or CDN, which makes it slower than what returning traffic experiences. Testing an important page after every major change gives you a simple history.
Reading the summary: grade, load time, size, requests
The performance grade is a score based on established web performance best practices, such as compressing files, using browser caching, avoiding redirects and reducing requests. It is a guide, not a goal: a high grade does not guarantee a fast page, and a lower grade can be acceptable for a rich page.
Load time is the time until the page has finished loading in the test browser. Page size is the total weight of all files transferred, and requests is the number of files. As rough orientation, pages under two seconds feel fast, and pages above three megabytes or a hundred requests usually have room for improvement.
Reading the waterfall chart
The waterfall lists every request in the order it started, with a bar showing its phases: blocked, DNS lookup, connect, SSL handshake, send, wait and receive. Wait is the time the server needs to start answering; receive is the download time. Colours and icons mark the response codes, redirects and errors.
200 / DNS 22 · SSL 48 · Wait 410 ms 200 /css/main.css Wait 38 · Receive 12 ms 200 /img/hero.jpg 980 KB · Receive 640 ms 301 /fonts/inter.woff2 redirect → CDN 200 tag-manager.js third party · Wait 310 ms
Look for patterns. A long wait on the very first request, the HTML document, means the server is slow to generate the page. Long receive times on images mean files are too large. Many requests to different domains, each with its own DNS and SSL phase, point to third-party scripts. Redirects show up as extra requests before the real file. Red entries are errors, often missing files that still cost time.
Content and requests by type and domain
The breakdowns by content type and by domain show where the weight comes from. If images dominate, compression, modern formats such as WebP or AVIF, correct dimensions and lazy loading below the fold help most. If scripts dominate, remove unused libraries and question every tracking or chat tag. A long list of third-party domains is a common cause of slow and unpredictable pages.
Improvement suggestions
The test lists suggestions with their own grades, such as adding expires headers, compressing components with gzip or Brotli, reducing DNS lookups, avoiding URL redirects, making fewer HTTP requests or using a CDN. Fix the items with the lowest grades that affect the most files. Many can be solved with server configuration, a caching plugin or a CDN.
- Compress text files with gzip or Brotli
- Set long cache lifetimes for static files
- Resize and compress images, use modern formats
- Remove redirects and unused scripts
- Serve static files from a CDN
Pingdom Tools vs. PageSpeed Insights
Pingdom Tools measures how long a page takes to load from a chosen location and shows every file. Google PageSpeed Insights focuses on user-centric metrics, the Core Web Vitals, from real Chrome users plus a simulated mobile test with Lighthouse. Pingdom is better for seeing which files and servers are slow; PageSpeed Insights is better for understanding how Google and real users experience the page. Use both.
Checking the server part with the free test above
The free test on this page focuses on the first request, the one that decides when everything else can start. It measures DNS lookup, TCP connect, TLS handshake, time to first byte and the time to download the HTML from a server in Germany, without loading images or scripts. If time to first byte is high, front-end optimisation alone will not make the page fast; caching, hosting or application changes will.
Typical problems the test reveals
Some patterns appear again and again. A hero image of several megabytes uploaded straight from a camera. Dozens of small icon files instead of one sprite or an icon font. A slider loading every slide on page load. Fonts loaded from three different services. Tracking, chat, consent and A/B testing scripts that together outweigh the page itself. A redirect chain from http to https to www before the first byte arrives. Each of these is visible in the waterfall within seconds and usually easy to fix.
Testing the right pages
Do not test only the homepage. Product pages, category pages with many images, blog articles with embeds and the checkout often load very differently. Test a representative page of each template, and the landing pages that receive paid traffic, because every second there costs money directly.
Why results differ between tools
Speed tests differ in location, browser, connection speed, device emulation, whether they wait for all files or only for visible content, and how they treat caching. A page can load in 1.2 seconds in one test and 3.5 seconds in a mobile lab test. Compare results within one tool and one location over time, rather than between tools.
From a single test to continuous monitoring
A speed test shows one moment. Performance changes with updates, traffic and third-party services. Pingdom’s paid plans and other monitoring services check pages on a schedule and alert on slowdowns. monitordefend measures each website’s server response time every five minutes alongside uptime and emails you when it exceeds your threshold; it does not record waterfalls or full page load times.
Frequently asked questions
What is Pingdom Tools?
The free website speed test from Pingdom (SolarWinds) at tools.pingdom.com. It shows a performance grade, load time, page size, requests, suggestions and a waterfall chart.
Is Pingdom Tools free?
Yes, the speed test is free and needs no account. Pingdom’s monitoring services are paid.
Which test location should I choose?
The one closest to most of your visitors. Distant locations add network latency to every request.
Why is my load time different every time?
Caches, server load, network conditions and third-party scripts vary. Run several tests and compare the typical value.
What is a good load time in Pingdom Tools?
Under two seconds is fast for most pages; above three seconds is worth investigating.
Is the test on this page Pingdom?
No. It is an independent test that measures DNS, connection, TLS, time to first byte and HTML download time from Germany.
What does “wait” mean in the waterfall?
The time between sending the request and receiving the first byte of the answer, mainly server processing time.
Related pages
Watch your response time around the clock
Start for free and set up your first check in minutes.
Start for free