A Nuxt module that provides real-time feedback on your application's performance, accessibility, and security right in your browser.
Nuxt Hints integrates directly into the Nuxt DevTools, giving you actionable insights to improve your web vitals, fix hydration mismatches, and audit third-party scripts without ever leaving your development environment.
Nuxt Hints provides a rich, interactive UI inside the Nuxt DevTools panel.
A central hub to see a summary of all detected issues at a glance.

Drill down into Core Web Vitals metrics. See detailed attribution for LCP, INP, and CLS, inspect the problematic elements, and get context-aware advice.

Debug hydration mismatches with a powerful side-by-side diff viewer. See the exact differences between the server-rendered HTML and the client-side result.

Analyze all third-party scripts on your page. The dashboard shows loading times, render-blocking status, and security attributes, helping you identify and mitigate performance bottlenecks.

@nuxt/hints dependency to your project:# Using pnpm
pnpm add -D @nuxt/hints
# Using yarn
yarn add --dev @nuxt/hints
# Using npm
npm install --save-dev @nuxt/hints
@nuxt/hints to the modules section of nuxt.config.ts:export default defineNuxtConfig({
modules: [
'@nuxt/hints'
]
})
That's it! Open your Nuxt app, go to the DevTools, and click the Nuxt Hints icon to get started.
Nuxt Hints uses web-vitals to gather Core Web Vitals metrics and automatically logs any metrics that need improvement. It listens for INP, LCP, and CLS and provides detailed attribution for each.
The module hooks into Vue's hydration process to compare the server-rendered DOM with the client-side DOM. When a mismatch is detected, it captures the pre- and post-hydration HTML for inspection.
Using a combination of a Nitro plugin and client-side observers, Nuxt Hints tracks every script loaded on the page, measuring its performance and analyzing its attributes.
When Nuxt Hints detects issues, you'll see clear warnings in your browser console:
[@nuxt/hints:performance] LCP Element should not have `loading="lazy"`
Learn more: https://web.dev/optimize-lcp/#optimize-the-priority-the-resource-is-given
[@nuxt/hints] Third-party script "https://cdn.example.com/script.js" is missing crossorigin attribute.
Consider adding crossorigin="anonymous" for better security and error reporting.
# Install dependencies
npm install
# Generate type stubs
npm run dev:prepare
# Develop with the playground
npm run dev
# Build the playground
npm run dev:build
# Run ESLint
npm run lint
# Run Vitest
npm run test
npm run test:watch
# Release new version
npm run release