Page Experience Checker
Google describes good page experience as fast, secure, mobile-friendly pages without intrusive pop-ups. This checker combines the signals in one report: whether the page uses HTTPS and HSTS, whether it loads insecure resources (mixed content), whether it has a mobile viewport, whether elements named like pop-ups or overlays are present, and the Core Web Vitals – LCP, INP and CLS – measured from real Chrome users through Google PageSpeed Insights.
- Encrypted connection
- No sign-up
- Free to use
How to use Page Experience Checker
- Enter the page URL.
- Click “Check page experience”.
- Read the page signals right away.
- Wait 20–60 seconds for Core Web Vitals.
Page Experience Checker features
HTTPS and HSTS
Secure delivery checked.
Mixed content
http:// scripts, frames and images.
Mobile viewport
width=device-width.
Pop-up hints
Overlay and modal elements found.
Core Web Vitals
Field data from PageSpeed Insights.
Safe fetching
Only public http(s) addresses are fetched.
When to use Page Experience Checker
- Monitoring key pages after releases.
- Explaining page experience to stakeholders.
- Finding mixed content after an HTTPS move.
- Checking whether CWV pass for real users.
Page Experience Checker FAQ
Where do the Core Web Vitals come from?
From Google PageSpeed Insights: the 75th percentile of real Chrome users over 28 days (the Chrome UX Report). Nothing is estimated by this tool. Pages without enough traffic show lab values instead.
Why are vitals sometimes unavailable?
PageSpeed Insights has a shared quota and may be busy, or cannot reach the page. The rest of the report still works; try again later.
How are pop-ups detected?
Only by element names such as modal, popup or overlay in the HTML. It cannot tell whether they cover content on load, so check the page yourself.
Is page experience a ranking factor?
Google says good page experience supports rankings, but relevance comes first. A great experience will not rescue an unhelpful page.
The parts of page experience
Core Web Vitals measure loading (Largest Contentful Paint), responsiveness (Interaction to Next Paint) and visual stability (Cumulative Layout Shift). A page passes when the 75th percentile of visits is good for all three.
Security signals are simpler: the page should be served over HTTPS, ideally with HSTS, and should not load scripts, styles or frames over plain HTTP, which browsers block. Images over HTTP are upgraded or warned about.
Intrusive interstitials – pop-ups that cover the content right after a visitor arrives from search – are the hardest to detect automatically, so the checker gives a hint rather than a verdict.
Privacy: the address you enter is fetched by our server only to run this check. The downloaded HTML is passed to your browser for analysis and is not stored, and the results are not saved on our side. Requests are rate-limited to keep the service fair for everyone, so if you check many pages in a row you may need to wait a few minutes.
Limits: pages are read up to 2 MB of HTML, redirects are followed up to eight hops and each request has a short timeout. Pages behind a login, servers that block automated requests and content added only by JavaScript cannot be analysed this way; for those, copy the page source from your browser and use the paste option where it is available.
Tip: fix the problems marked red first, because they matter most. Yellow warnings are worth reviewing but are often harmless in context, and blue notes are information. After a change, run the check again to confirm the result – search engines pick up the change on their next visit to the page.