Which page should we test?
Any public page. We fetch it once as a phone would, read the HTML and your robots.txt, and score 13 checks. Pages behind a login or a bot wall cannot be read, and we say so rather
Fetching the page as a
About 20 seconds · No sign-up, and the result is not held back for
Mobile readiness
Scored from one fetch with a mobile user agent. Tap-target spacing and real Core Web Vitals are not measured here. Use the checks below to investigate the rendered page and available
What to fix, in order
Not
What this fetch cannot measure
Tap-target spacing (needs a rendered layout)
Real-user Core Web Vitals: LCP, INP, CLS (needs field data)
Rendered font sizes from external CSS (needs a browser)
Every check we made
- Viewport meta tag set to the device width
- No fixed-width elements wider than a phone
- No inline text under 12px
- Pinch zoom not disabled
- Page language declared
- HTML under 100 KB
- Server responds within 800 ms
- 15 or fewer external scripts
- Every image carries width and height
- Page returns 200 over HTTPS
- Indexable: no noindex, not blocked by robots.txt
- Canonical URL declared
- Title and meta description present
Want the fixes done, not listed?
Our technical SEO service repairs crawl, render and speed defects on the live site and proves each one with a before-and-after read. Book a free 30-minute call and we go through this result
Why this matters
Most visits are on a phone.
Paste a URL. You get a score and a fix for each check this page can read. The method, including PageSpeed, is in the mobile-friendly test guide. The fixes are on technical SEO.
Questions
Mobile-friendly test, explained.
Is this the same as Google’s Mobile-Friendly Test?
How does the test work?
What does the score mean?
Why can it not measure tap targets or Core Web Vitals?
Does a pass here mean my page ranks on mobile?
Do you store the URL or the result?
Want the full picture?
Book a free 30-minute call. We review it live with you, and you leave with what to