www.pestheroguard.com

Nuxt what actually works on this platform

Nuxt decides per route whether a page is prerendered, cached for a while, or rendered fresh every time — and that decision, not server tuning, is where most of the time goes.

• Nothing indicated the HTML came from a cache on this request — every visit appears to pay for a fresh render.
• Time to first byte measured 684ms on this run — one sample; re-run it before treating it as the number.

1. Set route rules for the pages that do not change per visitor. Nuxt lets you mark a route prerendered, cached with revalidation, or rendered per request, in one config block. Marketing pages, docs and posts are almost always in the first two categories and are usually left in the third by default.
2. Check what the payload carries. Nuxt serialises the data a page fetched into the HTML so the client does not refetch it. A route that pulls a large collection ships all of it twice — once as markup, once as payload. Fetch only the fields the page renders.
3. Prefetch links, but only what is likely. NuxtLink prefetches by default, which is right for a small nav and wasteful on a long list. Turn it off where a page links to hundreds of routes.
4. Use the image component and lazy-load below the fold. Nuxt Image emits modern formats at the right size; explicit dimensions stop layout shift. On most Nuxt sites this is the largest single win after the route rules.

The full instruction set, and a machine-readable copy of this report, live at www.pestheroguard.com.md — paste that URL into your AI builder's chat and it can work straight from these measurements.