Framework · SvelteKit
Website audit for SvelteKit sites
Already fast by default – make sure metadata, images and prerendering keep up.
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
- SvelteKit-aware findings and a prioritised 30-day plan
Why SvelteKit sites lose rankings and conversions
SvelteKit sites are usually among the lightest we measure, so performance findings are more specific: a load function that fetches too much and serialises it into the page, images served as plain <img> without srcset because @sveltejs/enhanced-img is not installed, or a heavy third-party embed pulling the score down on one landing page.
The SEO side is where SvelteKit projects most often fall short, because the framework provides nothing by default. Titles and descriptions live in <svelte:head> and are easy to forget on nested routes, canonicals are almost never set, there is no built-in sitemap, and dynamic routes that should be prerendered are rendered on demand instead, adding TTFB on every request.
WebVitalist crawls the deployed site, checks every route it finds for head tags and structure, and measures it with Lighthouse on a mobile device.
Checks
What we check on SvelteKit
On top of the standard technical, performance, accessibility and copy checks, the report looks for the problems specific to SvelteKit.
- 01 svelte:head coverage: routes with missing or inherited titles and descriptions
- 02 Canonical and Open Graph tags, especially on dynamic [slug] routes
- 03 Prerender and ISR configuration versus TTFB on content pages
- 04 Images without srcset or enhanced-img processing
- 05 Serialised load data size and its effect on HTML weight and hydration
- 06 Sitemap and robots.txt endpoints and whether they list every route
- 07 Third-party scripts and embeds on landing pages
- 08 Heading structure, link text and accessible names in layouts and components
Fix Pack · $149
How the Fix Pack works for SvelteKit
Fixes are delivered as Svelte and TypeScript: <svelte:head> blocks with title, description, canonical and Open Graph tags driven by page data, a sitemap.xml +server.ts endpoint, prerender and config.isr settings per route, enhanced-img usage for hero images, and JSON-LD snippets. Every fix names the route file it belongs to.
FAQ
SvelteKit questions, answered.
Do you support Svelte 5 and runes?
Yes. The audit looks at the rendered site, so the Svelte version does not matter for the findings. Code fixes are written in Svelte 5 syntax.
Which adapters do you detect?
We detect the hosting (Vercel, Netlify, Cloudflare, Node) from response headers, and the performance findings account for edge caching and prerendering behaviour on that host.
My SvelteKit site already scores 95+ on Lighthouse. Is the audit still useful?
Usually the value then lies in the SEO and copy sections: missing canonicals, weak titles, thin pages and conversion issues that Lighthouse does not measure.
Other platforms