Page Speed Checker: Free Website Speed Test

A page speed checker shows how long a web page takes to fetch and what the page is made of. Enter a URL in this free page speed checker and you get a load time in seconds, a Fast, Average or Slow rating, the total page weight, and a sortable list of every CSS, JavaScript, image and other file with its size and status.

What Is Page Speed?

Page speed is the time it takes for a web page to deliver its content to a visitor. It depends on the size of the HTML document, the number and weight of files the page pulls in, and how quickly each one responds.

Most pages are not one file. The HTML points to stylesheets, scripts, fonts, images and other assets, and each one needs its own request. A page with a small document but 60 slow requests can feel slower than a heavier page with 15 fast ones. That is why this tool reports both a total time and a file-by-file breakdown.

Speed matters for two reasons. Visitors leave pages that stall, and Google has said that page experience, including speed-related signals, is part of how it evaluates pages. Speed alone will not outrank relevant content, but a slow page makes every other SEO effort work harder.

How to Check Page Speed of a Website with This Tool

You can check the speed of any public page in a few clicks, with no account needed. Follow these steps:

1. Open the tool and click the field that shows the placeholder https://example.com.
2. Type or paste the full address of the page you want to test, such as a blog post, product page or home page.
3. Submit the form with the main button and wait while the page and its files are fetched. Pages with many resources take longer to finish.
4. Read the headline result: the load time in seconds and the status badge (Fast, Average or Slow).
5. Review the summary cards: the number of CSS, JS, image and other files, Total Page Weight, Total Resources and HTML Document size.
6. Open the resource tabs (CSS, JS, Images, Other) and click the Size or Load Time (s) column headers to sort the heaviest or slowest files to the top. Use the export option to save the table as a CSV file.

Test the exact URL you care about. The tool keeps the protocol you enter, so test the https version of your page if that is what visitors use.

Worked Example: Reading a Slow Result

Say you test a blog post and the tool returns a load time of 9.2 seconds with a red Slow badge. The cards show 4 CSS files, 9 JS files, 22 images and 3 other files, which makes 38 resources. Total Page Weight is 3.4 MB, and the HTML Document is 85 KB.

The HTML is not the problem. At 85 KB it is a small share of the 3.4 MB total, so the weight is coming from assets. You open the Images tab and sort by Size. The top row is a hero photo at 1.8 MB that took 2.1 seconds to fetch. Two more photos are around 400 KB each.

The fix is clear. Resize the hero image to the width it actually displays, compress it, and serve a modern format. A 1.8 MB photo often drops to 150 to 250 KB with no visible change. That one edit removes roughly 1.6 MB, and the load time falls by about two seconds on its own. Run the test again to confirm the new numbers.

How Do You Read and Act on the Results?

Each result on the page points to a specific kind of fix. Start with the badge, then work down to individual files.

Load time and the status badge

The badge uses simple bands: 3 seconds or less is Fast, over 3 and up to 7 seconds is Average, and anything above 7 seconds is Slow. Aim for Fast. If you land in Average or Slow, the resource tables tell you where the time went.

Total page weight

Total Page Weight is the combined size of the HTML and the files that returned a successful response. There is no single official limit, but many teams try to keep a standard content page under roughly 1 to 2 MB. If you are far above that, look at images first, then scripts.

Resource counts

The cards for CSS, JS, images and other files show how the page is assembled. Many separate script files often mean extra requests. Consider combining files, removing unused plugins, or loading non-essential scripts later.

Per-file size, time and status

Every row lists a file name, its full address, its size, its load time and its HTTP status code. Time values are color coded: up to 0.5 seconds is good, up to 1.5 seconds is middling, and above 1.5 seconds is slow. Read the status code too:

• 200 range: the file loaded normally.
• 300 range: the file redirected. Point the page directly at the final address to save a request.
• 400 or 500 range: the file is missing or failing. Fix or remove the reference, because it wastes time and may break layout.

To investigate a status code further, run the address through a bulk HTTP status checker, which is handy when many files look broken.

Who Benefits From a Page Speed Check?

Anyone responsible for how a page loads can use this report. These are the situations where it earns its keep:

• Site owners and bloggers who want to know why a page feels sluggish before paying for a developer.
• SEO specialists who need a quick list of heavy or failing files to include in an audit.
• Developers who want to confirm that a release did not add oversized images or extra scripts.
• Agencies who export the resource list as a CSV and attach it to a client report.
• Store managers who add product photos regularly and want to catch unoptimized uploads.

It is also a fast way to compare two versions of a page. Test before and after a change and compare load time, total weight and file counts side by side.

Best Practices, Common Mistakes and Troubleshooting

Page speed testing gives the most useful answers when you test consistently and fix the biggest items first.

Best practices

• Test key pages, not only the home page. Templates for posts, categories and products often behave very differently.
• Sort each tab by Size and then by Load Time (s). Fixing the top three files usually beats polishing twenty small ones.
• Check whether text files are compressed with a GZIP compression checker, since compression can shrink HTML, CSS and JS considerably.
• Look at the response headers with an HTTP header checker to confirm caching and compression settings.
• Retest after every change and note the numbers so you can see real progress.

Common mistakes

• Entering a URL without the right protocol. If the page only works on https, enter the https address.
• Testing a page that redirects. Enter the final address, or the result may describe the wrong page.
• Judging from one run. Load time varies with how busy the site is. Test two or three times and look at the pattern.
• Ignoring failed files. A 404 stylesheet or image costs time and adds nothing.

If the result looks wrong

If you see an error instead of a report, check that the address is complete and public. Pages behind a login or firewall cannot be fetched. If the resource list looks shorter than expected, remember that files added later by scripts after the page loads may not appear. Also, files that are not regular web addresses, such as inline data, are not listed separately because they are already inside the HTML size.

What Does This Page Speed Checker Not Measure?

This tool reports fetch times and file sizes. It is not a full browser rendering test. Its load time adds up the time to request the page and each resource it found, so it is best used as a comparison and diagnosis tool, not as a measure of exactly what a visitor sees.

It does not report Core Web Vitals such as Largest Contentful Paint, which Google considers good at 2.5 seconds or less. It also does not simulate separate mobile and desktop devices or throttled connections. For those signals, use a page experience checker alongside this report. For a focused look at weight alone, the page size checker is a useful companion.

Because the numbers depend on conditions at the moment of the test, treat small differences, such as 0.2 seconds, as noise. Focus on large, repeatable gaps.

Find Out What Is Slowing Your Page

This free page speed checker turns a vague feeling that your site is slow into a ranked list of the files responsible. Enter your URL above, sort the resource tabs by size and time, fix the heaviest items, and test again. For more checks in the same area, browse the website audit and performance tools.