SSR / Pre-rendering
Checks if the page is server-rendered or statically pre-rendered.
What this check measures
We compare the raw HTML response to the fully-rendered DOM. A large gap means JS-only content — a problem for crawlers and slow connections.
Why it matters
Pure client-rendered pages have worse initial paint, worse SEO, and are invisible to AI crawlers. SSR or SSG solves all three.
How our audit detects it
Fetch raw HTML, compare body text length to rendered DOM text length. Ratio under 20% = client-rendered.
Typical findings
- error_outlineLess than 10% of content in raw HTML.
- error_outlineOnly skeleton/loader visible without JS.
How to fix
Migrate to a framework with SSR or add static pre-rendering. Next.js, Remix, Astro are all good options.
Copy-paste fix prompt for your stack
Lovable · Cursor · Bolt · v0 · Replit · Windsurf · Claude Code · Base44
Frequently asked questions
Can I mix SSR and SPA?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
HTTP Status Codes
Checks that pages return proper status codes — 200 for live, 404 for missing, 301 for moved.
TechnicalNo Client-Side Redirects
Checks that redirects happen server-side, not via JavaScript.
TechnicalViewport Meta Tag
Checks for <meta name="viewport" content="width=device-width, initial-scale=1">.
TechnicalHTML lang Attribute
Checks that <html> has a lang attribute matching the page language.