Static front end, WordPress backend, full optimization.
Next.js, Astro, or Nuxt powered front ends paired with WordPress as the content source still need image optimization and audit history. Some pieces of the agent are not relevant; the ones that are still ship full strength.
What ships pre tuned for this stack.
Front end agent (npm)
Drop a small npm package into your Next.js or Astro project. It reports build events, hands off image URLs, and pulls feature flags.
imgproxy on your CDN
Serve the optimized image URLs from your existing CDN, edge cached. Same compression rules as the WordPress integration.
Image sourcing from WP REST
Resolve WordPress media IDs to imgproxy URLs at build time or at request time. Both work.
Lighthouse audits the front end
We audit your live front end URL, not the WordPress backend, since that is what visitors see.
Build and deploy webhooks
Trigger our cache warmup after a Vercel or Netlify deploy. Your visitors hit a warm front end on every release.
Backend monitoring optional
If you want to also audit the WordPress admin or REST endpoints, the standard agent covers it.
The short list.
- Works with WPGraphQL, REST, or hybrid models.
- Compatible with Faust.js, Headstart WP, and bespoke Next.js setups.
- Per route audit history.
- Build artifact analysis available on Scale tier.
Ship faster, the same way.
Set up takes ten minutes. The first audit runs five minutes after that.