Toolkit capability
Astro performance and accessibility
Improve Astro performance, accessibility, best practices, and SEO with measurable release gates on mobile and desktop.
Astro performance and accessibility
Make fast, accessible Astro output a repeatable result.
Astro creates a strong static-first foundation, but real scores still depend on images, fonts, third-party scripts, semantic HTML, metadata, caching, and the document actually audited.
What the process produces
06 concrete deliverables- 01Mobile and desktop PageSpeed runs
- 02Performance budget and regression evidence
- 03Accessible navigation and controls
- 04Image and font optimization
- 05Per-page metadata and social previews
- 06Cache and header verification
Capability and requirements
What this workflow does, and what it needs.
Required inputs apply to this workflow. Conditional tools apply only when the project, platform, or chosen service needs them. A missing optional integration does not block unrelated Go for Launch checks.
Required for this workflow
Inputs and evidence
- The exact staged production candidate and its canonical page list
- Mobile and desktop browser testing plus public PageSpeed access
- Permission to change assets, fonts, markup, styles, headers, and scripts that affect results
Only when applicable
Conditional tools and access
- A PageSpeed API key only when API automation or higher quota is needed
- Third-party dashboards only for services the audited site uses
- Cloudflare access only when its cache, header, or deployment configuration is in scope
Measure the right candidate
Confirm the final URL, status, title, canonical URL, expected content, and candidate identity. A perfect score on an error page or stale deployment is not evidence.
Optimize the full delivery path
Control asset dimensions, responsive images, font loading, third-party code, CSS ownership, immutable build assets, and edge headers. Validate the result on a staged production build.
Treat accessibility and SEO as architecture
Use semantic controls, keyboard behavior, unique page metadata, structured data, discovery files, and human-readable navigation. These are content and component contracts, not final-pass patches.