Desktop & mobile render.
Your homepage as a real browser draws it, on a laptop and on a phone, plus the four mobile-usability checks. It captures itself, it's free, and it's homepage-only.
Two screenshots of your homepage — one on a laptop, one on a phone — taken from a real render, not from a cached thumbnail. Underneath them sit four mobile-usability checks. It's the quickest way to catch a homepage that looks fine on your monitor and falls apart on a phone.
You'll find it on the SEO & AI Visibility → SEO Score tab, under Device rendering. It's free — it's folded into the audit and costs no credits.
What you're looking at
The renders come from Google Lighthouse, run at each device size. That matters: this is the page as a headless browser actually draws it, so if a cookie banner covers your hero, or a font never loads, or a hero image is still blank when the page settles — you see exactly that. Desktop and mobile are captured in parallel, so the two shots are of the same moment.
The desktop render is usually the one you already know. Look hard at the phone: it's the layout most of your visitors get, and it's the one people never check.
Homepage only, captured for you
Two things people ask, so here they are plainly:
- There's no page picker. We render your homepage and nothing else. You can't point it at a product page or a blog post. If you want another page rendered, use Google's own PageSpeed Insights.
- There's no capture button. The first time you open the SEO Score tab, the section captures itself. After that the images are stored, so the section loads instantly on every later visit and doesn't re-render.
Because it's stored, the shot you're seeing is from when it was captured — it doesn't silently re-take itself every time you redesign your site. Run a fresh audit if you want it brought up to date.
The four mobile checks
The mobile render also gives us Lighthouse's mobile-usability audits. We surface four of them, and each one that fails comes with the fix:
- Responsive viewport — the page has a viewport meta tag, so it scales to the screen instead of showing a zoomed-out desktop layout. This is the one that makes a site look broken on a phone, and it's a one-line fix.
- Legible font sizes — no text so small that a visitor has to pinch-zoom. Aim for at least 16px body text.
- Tap targets sized well — buttons and links aren't too small or too close together. Make them at least 48px and space them out.
- No unsupported plugins — the page doesn't rely on something a phone can't render (Flash, for example). Rare now, but fatal when it happens.
Here's the viewport tag, since it's the one people are missing:
<meta name="viewport" content="width=device-width, initial-scale=1">
A check passes at a Lighthouse score of 0.9 or better — so “passed” means comfortably fine, not scraped through. Clear all four and the section shows a green Mobile-friendly badge; otherwise it tells you how many are left to fix.
When the render comes back blank
The screenshots depend on Google's PageSpeed service, and it isn't always in the mood. The section tells you which of these happened, and offers a Try again link:
- “Performance data isn't switched on yet” — the PageSpeed key isn't configured on our side. Nothing you can do; it isn't your site. Contact support if it persists.
- “Google is rate-limiting right now” — try again in a minute.
- “That page took too long to render” — a heavy homepage can exceed the render window. This is itself a finding: if Lighthouse struggles, so do your visitors. Check Core Web Vitals.
If only the desktop shot is missing, we already retried it once for you before showing anything — the desktop render is the one that most often times out on a heavy page. A second failure usually means the page is genuinely slow.
If Lighthouse didn't return its checklist, we fall back to the single viewport signal we picked up during the crawl — so you'll see one check instead of four. Re-run the audit and it usually comes back complete.