First-screen checker for phone, tablet and desktop
Visitors decide in the first screen. Load your page in a real browser on three devices and see whether the H1 and your call to action are visible without scrolling, whether a pop-up or cookie wall covers them, and what AI crawlers miss because they do not run JavaScript.
Or ask your AI assistant
This check is the layout · render tool in the free OnPage.dev MCP server. Connect it to Claude, ChatGPT or Cursor once, then ask in your own words.
Check what visitors see first on our pricing page on phone, tablet and desktop, and fix what is below the fold.
layout · renderPhone: call to action below the foldlayout · renderCookie wall covers 80% on mobile
What gets checked
- Whether the H1 and the main call to action are visible without scrolling, on a phone (390 px), tablet (820 px) and desktop (1440 px).
- Pop-ups and cookie walls that cover the first screen. A compact cookie bar is fine; a full wall is not.
- Tap targets smaller than 44 px, text smaller than 12 px, sideways scrolling and layout shift while loading.
- The page loaded again with JavaScript off: text, title or canonical that only exist after JavaScript are invisible to GPTBot and ClaudeBot.
- Whether the first screen repeats what your Google title and description promise.
- Design and readability: text with too little contrast against its real background (WCAG AA), the element that makes the page scroll sideways, mixed button styles and uneven spacing between sections.
OnPage.dev has a small daily budget of browser time, shared by everyone. If it runs out, try again tomorrow, or use the same check in your AI assistant with its own browser.
Questions
Why three devices?
Most traffic is mobile, and Google indexes the mobile version first. But a call to action that fits on a phone can drop below the fold on a short laptop screen, so all three are checked.
Does a cookie banner hurt SEO?
A legally required, proportionate notice does not. A full-screen wall that hides the content hurts visitors and can hide text from crawlers that render the page.
More free tools
robots_txt · testllms.txt generatorGenerate an llms.txt for your website from its sitemap and home page in seconds.llms_txt · generateGoogle snippet checkerCheck if your title tag and meta description fit in Google on desktop and mobile, measured in pixels, and see where they get cut off.snippet · searchRedirect checkerCheck status codes and full redirect chains for up to 20 URLs at once, and verify each one ends at the right page.check_links · urlsOpen Graph checkerCheck how a page looks when it is shared on Facebook, LinkedIn, X, WhatsApp and Slack: every OG and Twitter tag, plus the real size and file type of the share image.snippet · socialSchema markup validatorValidate JSON-LD structured data before you publish: syntax, @context and @type, ISO dates, absolute URLs and Google’s required fields for rich results.schema · validatellms.txt validatorCheck your llms.txt against the llmstxt.org format: title, summary, sections, link format, size and whether the linked pages load.llms_txt · validateEntity graph checkerSee how your structured data tells AI and Google who is behind a page: Organization, author, publisher and sameAs profile links, with the fixes as JSON-LD.entity · graphRedirect map generatorPaste your old and new URLs and get a 301 redirect map with a confidence score per match, as _redirects, nginx, Apache or Next.js rules.plan · redirectsScreen reader checkerSee your page the way a screen reader and a browsing AI agent read it: landmarks, headings and every link, button and image with the name it gets, plus what is missing.accessibility · screen_readerSEO audit to Google SheetsScan a page and get every SEO finding as a Google Sheet with one formula, plus a ready Slack message and one task per issue for Notion, Linear, Jira or Asana.share · export