Page Experience Checker: Free Online Audit

The Page Experience Checker is a free page experience checker that audits any public URL for HTTPS, HSTS, a mobile viewport tag, compression, caching, page weight, response time, intrusive pop-up markup and image alt text. You enter a URL and get a percentage score plus a pass or fail note for every signal.

What Is Google Page Experience?

Google page experience is the set of signals that describe how a visitor experiences a page, apart from its written content. Google's Search Central documentation names Core Web Vitals (loading, interactivity and visual stability), secure HTTPS delivery, mobile-friendly display and avoiding intrusive interstitials among them. Google also says it has no single page experience ranking signal, so a strong result supports your SEO rather than guaranteeing a position.

This checker turns those ideas into nine measurable checks on the page's response headers and HTML. The score is a summary created by this tool, not a number Google reports.

Is this the same as landing page experience in Google Ads?

No. Landing page experience in Google Ads is a Quality Score status Google assigns to the destination pages of your ads. This tool does not return that rating. It does flag problems that commonly hurt a landing page, such as a missing viewport tag, no HTTPS or a slow response.

What Does the Page Experience Checker Test?

The tool runs nine checks against the URL you enter and follows redirects, so HTTPS is judged on the final address your visitors land on.

The alt text check needs images on the page to be measured.

How to Use the Page Experience Checker

1. Find the Website URL field at the top of the tool.
2. Type or paste the full address, for example https://example.com. If you leave off the protocol, https:// is added for you.
3. Click Check Page Experience. The button changes to "Checking..." while the page is fetched.
4. Read the Page Experience Score at the top. It is a percentage shown in green, amber or red.
5. Scroll through the signal list. Each row gives the signal name and a one-line detail explaining why it passed or failed.
6. Fix the failed rows, publish the change and run the same URL again to confirm.

Worked Example: A Blog Post With Two Failures

Say you check https://example.com/blog/running-shoes. The page loads over HTTPS, has a viewport tag, returns gzip-compressed HTML, sends a Cache-Control header, weighs 1.2 MB and shows no pop-up markup. It also has 12 of 14 images with alt text (about 86%).

Two rows fail. There is no HSTS header, and the response took 2.1 seconds, which is over the 1.5-second line. Seven checks pass and two fail, so the score falls short of a clean 100% and the two failed rows are your to-do list.

To fix HSTS, confirm every part of the site works on HTTPS, then add the header at your host or CDN. To fix the slow response, look at server-side caching, a CDN and heavy database work before the page is sent. Run the URL again afterward to see both rows turn into passes.

How Do You Read the Score and Fix Each Signal?

A score of 80% or higher shows in green, 60% to 79% in amber and anything below 60% in red. Treat green as "no obvious technical gaps," not as proof your page is fast or well designed.

HTTPS and HSTS

HTTPS should always pass. If it fails, install a certificate and redirect every HTTP URL to its HTTPS version with a 301. HSTS tells browsers to use HTTPS automatically on return visits, so add it once you are sure no part of the site still needs plain HTTP. You can confirm the header on the HTTP header checker.

Viewport tag

A missing viewport meta tag usually means mobile browsers will show a shrunken desktop layout. Add a standard responsive viewport tag to the head of the page. Passing proves only that the tag exists, so still open the page on a phone.

Compression, caching, weight and response time

A compression failure means no encoding header came back. Enable gzip or Brotli at your web server or CDN, then verify with the GZIP compression checker. The caching check passes if any of the three cache headers exists, so a value like no-store still passes even though it blocks caching. Review the actual value.

For page weight, a result over 3 MB usually points to oversized images or scripts. The Page Speed Checker lists each CSS, JS and image file, and the Page Size Checker shows the HTML size alone. On response time, web.dev guidance treats a time to first byte of 0.8 seconds or less as good, so 1.5 seconds including download is a fairly forgiving line.

Interstitials and alt text

An interstitial fail means the HTML contains dialog or visible modal, popup or overlay markup. Replace full-screen pop-ups with a small banner or an inline form. For alt text, describe meaningful images in a few words and leave decorative ones with an empty alt, though that lowers your ratio slightly.

Who Should Use a Page Experience Check?

Anyone who needs a quick technical read on a URL will get value from it.

• SEO auditors can triage a client page in seconds before a deeper audit.
• Developers can confirm a deploy did not drop HSTS, compression or the viewport tag.
• Marketers can sanity-check a campaign landing page before paying for traffic.
• Site owners after an HTTPS migration can confirm the final URL is secure and the headers survived the move.

Best Practices and Troubleshooting

Test the exact page that matters, not just your homepage. Templates differ, so check a product page, a blog post and a landing page separately.

• "Please enter a valid URL": look for spaces or typos in the domain.
• "Not reachable as a public address": localhost, staging sites behind a login and private network addresses cannot be tested.
• Response time changes between runs: speed varies with server load, so run it two or three times and judge the pattern.
• Pop-up passes but you see one: pop-ups added later by scripts may not exist in the raw HTML the tool reads.
• Compression fails but your CDN says it is on: the CDN may compress only for some requests. Compare with the gzip checker and your page source view.
• Redirect confusion: enter the version you want indexed, and use the final address shown in your results.

What Are the Limits of This Checker?

The tool reads one page's response and markup. It does not measure Core Web Vitals, rendered layout, field performance or real interstitial behavior. Google's "good" thresholds are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less, and you need Google PageSpeed Insights or the Chrome UX Report for those numbers.

It also checks a single URL at a time, and the 3 MB and 1.5 second lines are practical rules of thumb, not Google rules. Use the result as a fast technical checklist, then pair it with real-user data.

Run your most important URL through the checker above and fix the failed rows first. When you are ready to go further, explore the other tools in the Website Audit and Performance tools collection.