最佳免费网页速度测试:选择哪个以及原因
比较免费网页速度测试:每个测试测量的内容、实验室与真实用户数据、账户限制,以及哪个网页速度测试最适合特定任务。
The best site for a speed test depends on what you want to learn. Some tests load your page once in a controlled lab and tell you exactly what's slow. Others report how fast the page was for real visitors. The good news is that the best ones are free. This guide compares them, with their limits as of November 2026.
Lab data vs field data
Before comparing tools, it helps to know the two kinds of speed data.
- Lab data comes from loading the page once in a controlled setup, such as a simulated mid-range phone on a throttled connection. It's repeatable and great for debugging, but it's one visit under one set of conditions.
- Field data comes from real visitors. Google's Chrome UX Report (CrUX) collects it from Chrome users who opt in, and it's what Google uses for Core Web Vitals. It only exists for pages and sites with enough traffic.
A page can score poorly in the lab and still pass Core Web Vitals in the field, or the other way round. Use lab tests to find problems and field data to judge real experience.
Which free website speed test is best?
PageSpeed Insights
Google's PageSpeed Insights is the best starting point. Paste a URL and you get a Lighthouse lab test for mobile and desktop, plus real-user Core Web Vitals from CrUX when the page or site has enough traffic.
- Cost: free, no account.
- Best for: seeing what Google sees, and getting specific fixes.
Our guide to Lighthouse vs PageSpeed Insights explains how the two relate.
Lighthouse in Chrome DevTools
The same Lighthouse audit runs inside Chrome on your own computer. Open DevTools, choose the Lighthouse panel and run a report. It's free and can test pages that aren't public yet, such as a staging site.
- Limits: results depend on your computer and connection, so they vary more than PageSpeed Insights.
- Best for: testing changes before you publish.
WebPageTest
WebPageTest loads your page in real browsers from locations around the world and records a filmstrip, a request waterfall and detailed timings. The free Starter plan needs an account and includes a monthly allowance of test runs (150 as of November 2026, and each test can use several runs).
- Best for: deep debugging, such as finding which request blocks rendering.
GTmetrix
GTmetrix runs Lighthouse-based tests with a waterfall and history. A free account is needed to run tests, and the free plan includes a limited number of tests and test locations.
- Best for: a readable report and a waterfall in one place.
Pingdom Website Speed Test
Pingdom's free speed test loads a page from a choice of locations and shows load time, page size, requests and a waterfall, without an account.
- Best for: a quick view of page weight and the slowest requests.
FeedPulse website speed test
Our free website speed test runs any URL through Google's PageSpeed Insights API on mobile and shows the Speed Index and performance score, with no signup. It also gives you an embeddable badge that shows your page's speed on your own site; the badge re-checks every 6 hours for sites using it, while one-off lookups stay cached for up to 14 days. It's a lab result from one run, not real-user data.
- Best for: a quick mobile check and a speed badge.
Free speed tests compared
| Tool | Lab or field | Account needed | Free limit (Nov 2026) | Waterfall |
|---|---|---|---|---|
| PageSpeed Insights | Both (field when available) | No | No set limit | No |
| Lighthouse in Chrome | Lab | No | Runs locally | No |
| WebPageTest | Lab, real browsers | Yes | 150 test runs a month | Yes |
| GTmetrix | Lab | Yes | Limited tests | Yes |
| Pingdom | Lab | No | No account needed | Yes |
| FeedPulse | Lab (via PageSpeed Insights) | No | No account needed | No |
Free plans change, so check the provider's site before relying on a limit.
Which speed test should you use?
- "Is my site fast enough for Google?" PageSpeed Insights, and look at the Core Web Vitals section first. For your whole site, Search Console's Core Web Vitals report groups your pages by status.
- "Why is this page slow?" PageSpeed Insights for the list of fixes, then WebPageTest or GTmetrix for the waterfall.
- "Did my change help?" Lighthouse in Chrome before publishing, then PageSpeed Insights after. Run each test a few times, because single runs vary.
- "Can I show visitors my site is fast?" Our speed badge.
What is a good website speed test score?
Lighthouse scores performance from 0 to 100. Google labels 90 or above as good, 50 to 89 as needs improvement, and below 50 as poor. The score is a summary of several lab measurements, so it's more useful to look at which measurement is dragging it down than to chase the number itself.
For real-user data, Google's Core Web Vitals thresholds for a good experience are:
- Largest Contentful Paint (LCP): 2.5 seconds or less. How quickly the main content appears.
- Interaction to Next Paint (INP): 200 milliseconds or less. How quickly the page responds when someone taps or clicks.
- Cumulative Layout Shift (CLS): 0.1 or less. How much the page jumps around while it loads.
A page passes Core Web Vitals when at least 75% of visits meet each threshold.
How do I test my website speed on mobile?
PageSpeed Insights tests mobile by default, using a simulated mid-range phone on a slower connection. Our website speed test also tests mobile. Mobile results are usually lower than desktop, and that's expected: most visitors to many sites use phones, so the mobile result is the one to improve first.
How often should I run a speed test?
Run one whenever you change something that affects loading, such as a new theme, plugin, image-heavy page or third-party script. Otherwise, a monthly check of your most important pages is enough. Because lab scores vary between runs, run the test two or three times and look at the typical result rather than the best or worst one.
Why speed test results don't match
- Different devices and connections. Mobile tests simulate a slower phone and network than desktop tests.
- Different locations. A test far from your server adds latency.
- Caching. A first visit is slower than a repeat visit.
- Normal variation. Lab scores move a few points between runs even when nothing changed.
Pick one tool and one setting for tracking, and compare like with like.
What slows most websites down?
Whichever test you use, the same handful of causes come up again and again.
- Large images. Photos uploaded straight from a camera or phone are often several megabytes. Resizing them to the size they're shown at, and using a modern format such as WebP or AVIF, is usually the biggest single win.
- Render-blocking CSS and JavaScript. Files that must load before anything appears delay the first view of the page. Load non-essential scripts later, and keep the CSS needed for the first screen small.
- Third-party scripts. Chat widgets, ad scripts, tag managers and embedded videos each add requests, and some are heavy. Remove the ones you don't use and load the rest after the main content.
- Slow server response. If the server takes a long time to send the first byte, everything else waits. Caching, a content delivery network or better hosting helps.
- Web fonts. Several font files, or fonts that hide text until they load, delay readable content. Use fewer weights and let text show in a fallback font first.
- No caching for repeat visits. Without cache headers, returning visitors download everything again.
PageSpeed Insights lists which of these apply to your page, with an estimate of the time each fix could save. Start with the fixes at the top of its list.
Does a faster speed test score improve rankings?
Core Web Vitals are part of the page experience signals Google's ranking systems use, but Google says it still ranks the most relevant content first. Speed usually acts as a tie-breaker between similar pages. The stronger reason to fix a slow page is that visitors leave before it loads. For practical fixes, see how to improve your Lighthouse score.
Related free tools and guides
- Free website speed test — mobile speed and score for any URL, plus a badge
- Lighthouse checker — all four Lighthouse scores
- Lighthouse vs PageSpeed Insights