Framework · Astro
Website audit for Astro sites
Zero-JS by default, but islands, images and content collections still need checking.
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
- Astro-aware findings and a prioritised 30-day plan
Why Astro sites lose rankings and conversions
Astro sites ship very little JavaScript, which is exactly why the remaining problems stand out. A single React or Vue island with client:load on every page can add more script than the rest of the site combined; content collections generate hundreds of pages from one layout, so a missing description in the layout means hundreds of pages without one.
Images are Astro’s biggest performance lever. The built-in <Image> and <Picture> components produce responsive, optimised output, but only for images imported from src or configured remote domains; anything in /public is served as uploaded, and a 4 MB hero PNG is a common finding. Fonts loaded from Google Fonts rather than self-hosted add a render-blocking request chain.
WebVitalist measures the built, deployed site on a mobile device and checks every crawled page for metadata, structure and speed – including the hundreds of pages a content collection generates from a single layout.
Checks
What we check on Astro
On top of the standard technical, performance, accessibility and copy checks, the report looks for the problems specific to Astro.
- 01 Island hydration directives (client:load vs client:visible / client:idle) and their JavaScript cost
- 02 Images served from /public without optimisation versus <Image> and <Picture>
- 03 Layout-level metadata: pages inheriting one title or missing descriptions
- 04 Canonical URLs and the site option in astro.config for absolute URLs
- 05 Sitemap and robots output from @astrojs/sitemap and content collection coverage
- 06 Fonts: external stylesheets versus self-hosted or Fontsource
- 07 View transitions and client router scripts on sites that do not need them
- 08 Heading hierarchy in Markdown and MDX content
Fix Pack · $149
How the Fix Pack works for Astro
Fixes are delivered as Astro components and config: a <BaseHead> component with title, description, canonical and Open Graph props, <Image> and <Picture> replacements for hero and content images, client directive changes for islands, astro.config.mjs site and integration settings, and JSON-LD components. Each fix names the layout or page file it belongs to.
FAQ
Astro questions, answered.
Does the audit work with Astro SSR and hybrid rendering?
Yes. Static, hybrid and server-rendered pages are all measured as deployed, and TTFB findings distinguish prerendered routes from on-demand ones.
Can you check content collection pages?
Yes. The crawler follows links into blog and docs pages generated from collections; since they share a layout, one metadata fix in the layout typically resolves findings across every page.
Do you detect Starlight documentation sites?
Starlight sites are detected as Astro. The checks apply normally, and the report notes where a finding is controlled by Starlight configuration rather than your own components.
Other platforms