Framework · Nuxt
Website audit for Nuxt sites
Payload size, useSeoMeta gaps and image handling in Nuxt 3 sites.
Free scan takes 30 seconds. Want the whole site? Get the Deep Audit – $29
In every report
- Lighthouse on a mobile device: LCP, INP/TBT, CLS, page weight
- 20+ technical SEO checks on every crawled page
- Automated accessibility audit
- AI copy and conversion review with ready-to-paste rewrites
- Nuxt-aware findings and a prioritised 30-day plan
Why Nuxt sites lose rankings and conversions
Nuxt 3 sites are usually fast to first paint thanks to server rendering, and then pay for it in hydration: the serialised payload embedded in the HTML can reach hundreds of kilobytes when pages fetch large API responses with useFetch or useAsyncData, and every component that is not wrapped in <ClientOnly> or lazily loaded ends up in the initial bundle.
SEO gaps are typically about consistency. useSeoMeta or useHead is called in some pages and not others, the default title template in nuxt.config applies everywhere else, canonicals are rarely set on dynamic routes, and Open Graph images are missing on the pages that get shared most. Nuxt Image and Nuxt Fonts solve the image and font problems well, but only when they are installed and used instead of plain <img> tags and Google Fonts links.
WebVitalist measures the production build on a mobile device – after Nitro caching and route rules have done their work – and checks every page it crawls for metadata, structure and speed, so you see what visitors and crawlers actually receive.
Checks
What we check on Nuxt
On top of the standard technical, performance, accessibility and copy checks, the report looks for the problems specific to Nuxt.
- 01 Hydration payload size (__NUXT__ data), client bundle and Total Blocking Time
- 02 useSeoMeta / useHead coverage: pages with default titles or no description
- 03 Canonical and Open Graph tags on dynamic routes
- 04 Images served without Nuxt Image (no srcset, oversized originals)
- 05 Fonts loaded from external stylesheets instead of Nuxt Fonts
- 06 Route rules: static, ISR and SWR caching and their effect on TTFB
- 07 Sitemap and robots output from Nuxt SEO modules
- 08 Heading structure and link text in layouts and content pages
Fix Pack · $149
How the Fix Pack works for Nuxt
Fixes are provided as Vue and TypeScript: useSeoMeta calls with titleTemplate, canonical links via useHead, <NuxtImg> and <NuxtPicture> props, routeRules in nuxt.config.ts for caching, and JSON-LD via useHead script entries. Each snippet names the page or layout it belongs to.
FAQ
Nuxt questions, answered.
Do you support Nuxt 2 as well as Nuxt 3?
Both are detected. Fixes are written for Nuxt 3 by default; for Nuxt 2 the report uses the head() component option and nuxt.config equivalents.
Can you audit a Nuxt Content site?
Yes. Content-driven pages are crawled like any other, and the report flags Markdown-driven heading problems and missing frontmatter-based metadata.
Why is my Nuxt site slow if it is server-rendered?
Server rendering fixes first paint, not interactivity. Large data payloads and eagerly hydrated components delay the point at which the page responds to taps. The report measures both and shows which pages carry the heaviest payloads.
Other platforms