← Back to all tools

Find Out Why Your Website Feels Slow

You click a link, stare at a blank screen for a few seconds, and leave. Your visitors do the same thing. Speed is one of the few parts of a website that every visitor notices, even if they never mention it. This page speed checker tests a URL and shows how quickly the page loads, so you can find what is holding it back instead of guessing.

It’s one of the free helpers on Tool Hub Zone, and you can find more in our SEO tools section.

Steps to Test Your Page Speed

  1. Enter the full URL of the page, including https://.
  2. Run the test and wait for the results.
  3. Read the timings and any warnings, starting with the biggest problems.
  4. Fix one issue at a time, then test again to see what changed.

Test a few important pages, not just the homepage. A blog post or product page often behaves very differently.

Core Web Vitals in Plain Language

Google measures real user experience with three main signals, called Core Web Vitals.

Largest Contentful Paint (LCP). How long the biggest visible element, often a hero image or a headline, takes to appear. Google considers 2.5 seconds or less to be good.

Interaction to Next Paint (INP). How quickly the page responds when someone taps or clicks. It replaced First Input Delay as a Core Web Vital in 2024. A value of 200 milliseconds or less is considered good.

Cumulative Layout Shift (CLS). How much the page jumps around while loading. A score of 0.1 or lower is good. You have seen bad CLS when you go to tap a button and an ad pushes it away at the last moment.

Lab Data vs. Field Data

Results come in two flavors. Lab data comes from a test run under fixed conditions, which makes it great for debugging. Field data comes from real visitors on real phones and connections, which is what Google uses for Core Web Vitals. The two often disagree, and that’s normal. A fast result on your office Wi-Fi doesn’t guarantee a fast page for someone on a weak mobile connection, so treat a single test as a clue, not a verdict.

The Usual Causes of a Slow Page

  • Oversized images: The most common culprit. Shrink them with the Image Compressor and fit them to the real display size with the Image Resizer.
  • Old image formats: WebP is often lighter than JPG or PNG. Try JPG to WebP.
  • Heavy animated GIFs: A short video is usually far lighter. See GIF to MP4.
  • Too many scripts and plugins: Every extra script adds download and processing time, especially on WordPress sites with many plugins.
  • Slow hosting: If the server takes a long time to answer, front-end fixes can only do so much.
  • No caching: Without caching, the server rebuilds the page for every visit.
  • Layout shifts: Images and ads without set dimensions push content around as they load.

Quick Fixes That Usually Help

Start with images, since they are often the heaviest part of a page. Next, turn on caching and compression such as gzip or Brotli on your server. Load images below the fold lazily, and set width and height on every image to reduce layout shifts. Remove plugins you don’t use. A content delivery network (CDN) can also serve files from a location closer to the visitor. To see whether your server sends caching and compression headers, check them with the HTTP Header Checker.

Speed Is Part of Mobile Experience

Most people browse on phones, and Google uses the mobile version of your page for indexing. After improving speed, confirm your mobile setup with the Mobile Meta Checker. Speed is one ranking signal among many. A fast page with weak content will not outrank a helpful one, but a slow page can lose visitors before they ever read it. When the page is ready, write a strong snippet with the Meta Tag Generator, and find more guides on our blog.

Cross-Check With Other Tools

No single tool tells the whole story. Google PageSpeed Insights, Lighthouse in Chrome DevTools, and WebPageTest each measure things slightly differently. Use this checker for a quick look, then confirm bigger decisions with a second source. Scores also vary from run to run, so test two or three times before drawing conclusions.

Public Pages Only

The checker can test pages that anyone can open. Pages behind a login or staging sites blocked from outside access won’t return useful results. Our Privacy Policy explains how data is handled, and you can reach us through the Contact page with questions.

Frequently Asked Questions

What is a good page load time?
There is no single number, but Google treats an LCP of 2.5 seconds or less as good. Aim to show the main content quickly, not just finish loading everything.

Why is my mobile score lower than my desktop score?
Test conditions for mobile usually simulate a slower connection and a less powerful phone, so the same page often scores lower.

Does page speed affect SEO?
Yes, as one signal among many. Helpful content still matters most, but slow pages frustrate visitors and can hurt results indirectly.

Why do I get different results each time I test?
Network conditions, server load, and caching change between runs. Test a few times and look at the overall pattern.

What should I fix first?
Start with the largest images and any heavy scripts. Those usually give the biggest improvement for the least effort.