Free Next.js website audit: speed, accessibility, SEO and security
With Next.js you control everything, so every issue is fixable in code. The audit points to the exact config, component or API to change.
Free, no sign-up needed. We detect Next.js automatically and tailor every fix to it.
Issues you can fix on Next.js
- How to fix low color contrast on your website
Accessibility Find where the color is defined: a CSS variable, your Tailwind config or a component's styles.
- How to add alt text to images (and when to leave it empty)
Accessibility next/image requires an alt prop on every image. Give meaningful images a description and decorative ones an empty string.
- How to fix “Links do not have a discernible name” (icon links)
Accessibility Give icon links an aria-label, or include visually hidden text next to the icon. Mark the icon itself as decorative.
- How to add the Strict-Transport-Security (HSTS) header
Security Add the header for every route in next.config.ts using headers().
- How to add a Content-Security-Policy (CSP) header without breaking your site
Security Add the header for every route in next.config.ts using headers().
- How to add the X-Content-Type-Options: nosniff header
Security Add the header for every route in next.config.ts using headers().
- How to stop other sites embedding your pages (clickjacking protection)
Security Add the header for every route in next.config.ts using headers().
- How to add a Referrer-Policy header
Security Add the header for every route in next.config.ts using headers().
- How to add a meta description that gets clicks
SEO Add a description to the metadata export of each page, or return it from generateMetadata for dynamic pages.
- How to fix “Links do not have descriptive text”
SEO Change the link text in the component. For repeated cards, include the item's title in the link.
- How to fix “Image elements do not have explicit width and height”
Performance next/image always sets dimensions: statically imported images get them automatically, and remote images need width and height props (or fill inside a sized container).
- How to fix “Improve image delivery”: smaller, faster images
Performance Use next/image: it resizes on demand, serves WebP by default (add AVIF in next.config), and generates srcset for you.
- How to fix render-blocking requests (CSS and JavaScript)
Performance Next.js handles your own CSS and JavaScript. Blocking requests usually come from third-party <script> tags or font stylesheets added by hand.
- How to reduce unused JavaScript
Performance Keep components as Server Components unless they need interactivity: they send no JavaScript to the browser.
- How to fix a slow Largest Contentful Paint (LCP)
Performance next/image lazy-loads by default. On the image at the top of the page, set loading="eager" and fetchPriority="high". The old priority prop is deprecated in Next.js 16.
- How to fix a slow First Contentful Paint (FCP) and Speed Index
Performance Render pages statically or cache them where you can, so the server answers quickly.
- How to reduce Total Blocking Time (and JavaScript execution time)
Performance Keep components on the server unless they need interactivity; Server Components send no JavaScript to the browser.
- How to fix a slow server response, redirects and missing compression
Performance Make pages static or cached wherever their data allows, so the server isn't rendering on every request.
- How to fix long critical request chains (network dependency tree)
Performance Load fonts with next/font. It self-hosts Google Fonts with your other files, so the browser makes no request to Google.
- How to fix “Font display”: keep text visible while fonts load
Performance next/font uses font-display: swap by default. Load your fonts with it rather than with <link> tags or @font-face in global CSS.
- How to fix “Use efficient cache lifetimes”
Performance Files Next.js builds (everything under /_next/static/) already get a one-year immutable lifetime.
- How to fix “Legacy JavaScript”: stop shipping code for old browsers
Performance Next.js already targets modern browsers by default. If code is flagged, check for a browserslist entry in package.json or a .browserslistrc file that targets old browsers, and remove or update it.
- How to fix “Optimize DOM size”: pages with too many elements
Performance For long lists, render only what's on screen with a windowing library such as react-window, or paginate.
- How to fix layout shifts (Cumulative Layout Shift, CLS)
Performance next/image needs a width and height (or fill inside a sized container), so the space is reserved.
- How to reduce unused CSS, minify CSS and JavaScript, and remove duplicate code
Performance Production builds (next build) minify CSS and JavaScript automatically. If files are flagged as unminified, check you aren't serving a development build, and look for scripts loaded from /public.
- How to fix forced reflow (layout thrashing)
Performance Look for effects that measure elements after setting state, such as reading getBoundingClientRect() in a loop or on every scroll event.
- How to fix “Avoid enormous network payloads” (page weight)
Performance Use next/image for every image so it's resized and served in modern formats.
- How to fix “Page prevented back/forward cache restoration”
Performance Next.js sends Cache-Control: no-store on dynamically rendered pages, which can keep them out of the bfcache. Render pages statically, or cache them, where their content allows.
- How to fix the viewport meta tag (zoom disabled or not optimized for mobile)
Accessibility Next.js adds width=device-width, initial-scale=1 to every page by default.
- How to fix “Form elements do not have associated labels”
Accessibility Tie each input to a <label> with htmlFor and id, or wrap the input in the label. Use aria-label only when there's no visible text.
- How to fix “Buttons do not have an accessible name” (icon buttons)
Accessibility Give icon buttons an aria-label (or visually hidden text) and mark the icon as decorative.
- How to fix heading order (skipped heading levels and empty headings)
Accessibility Pass the heading level into reusable components (for example a Card that renders an h2 on one page and an h3 on another) instead of hard-coding it.
- How to set your page's language (the lang attribute)
Accessibility Set lang on the <html> element in your root layout. For multilingual sites, set it from the locale segment.
- How to fix small tap targets (“Touch targets do not have sufficient size or spacing”)
Accessibility Give icon buttons and small links a minimum size or padding in your styles.
- How to fix “Frames do not have a title” (embedded maps, videos and widgets)
Accessibility Add a title prop to every iframe.
- How to add captions to videos (“<video> elements do not contain a captions track”)
Accessibility Add a <track> with kind="captions" to every <video> with speech, and keep the .vtt file in /public.
- How to fix “aria-hidden elements contain focusable descendants”
Accessibility Don't render closed menus and dialogs at all, or use the inert attribute on hidden content. Use the native <dialog> element, which handles this for the page behind it.
- How to fix ARIA dialogs, fields and toggles without an accessible name
Accessibility Label dialogs with their heading, and custom controls with their visible label.
- How to fix invalid ARIA (roles, attributes and duplicate IDs)
Accessibility Use React's useId() for IDs inside reusable components, so each instance gets a unique one.
- How to fix list markup (lists must only contain list items)
Accessibility When mapping data to a list, render each item as an <li> directly inside the <ul>; put wrappers inside the <li>.
- How to fix “Some elements have a tabindex value greater than 0”
Accessibility Remove positive tabIndex props and reorder the JSX instead.
- How to add a skip link and a main landmark
Accessibility Put <main> in your root layout around the page content, and a skip link before your header.
- How to fix data table headers (size charts, price and spec tables)
Accessibility Render header cells as <th scope="col"> (or "row") and add a <caption>; it can be visually hidden if needed.
- How to fix “The document uses <meta http-equiv="refresh">”
Accessibility Use redirects in next.config, or redirect() in a server component, instead of a meta tag.
- How to fix “Links rely on color to be distinguishable”
Accessibility Underline links inside your prose styles.
- How to fix “Document doesn't have a <title> element”
SEO Export metadata (or generateMetadata) with a title from every page, and use a title template in the root layout for your brand name.
- How to fix “Page is blocked from indexing” (noindex)
SEO Check metadata.robots in the page and its layouts, and any X-Robots-Tag header set in next.config or middleware. Make sure noindex for preview environments doesn't apply in production.
- How to fix “Page has unsuccessful HTTP status code” (404 and 500 errors)
SEO A 404 usually means no route matches, or notFound() was called because data wasn't found. A 500 means rendering threw an error; check your logs.
- How to fix “Links are not crawlable”
SEO Use next/link for navigation (it renders a real <a href>), not a div or button with router.push().
- How to fix “robots.txt is not valid”
SEO Generate robots.txt from app/robots.ts so it's always valid, and remove any public/robots.txt that conflicts.
- How to fix “Document doesn't have a valid hreflang”
SEO Set alternates.languages in each page's metadata with valid codes and absolute URLs.
- How to fix “Document doesn't have a valid rel=canonical”
SEO Set metadataBase in the root layout and alternates.canonical in each page, so every page outputs one absolute, self-referencing canonical.
- How to fix “Browser errors were logged to the console”
UX & conversion Hydration errors (server and client rendered different HTML) are common: avoid reading window, dates or random values while rendering.
- How to fix “Uses deprecated APIs”
UX & conversion Update dependencies (npm outdated shows which are behind), and replace deprecated APIs in your own code, such as unload listeners with pagehide.
- How to fix “Uses third-party cookies”
UX & conversion Review third-party scripts loaded with next/script or in components. If you embed your own service on another domain, use partitioned cookies (CHIPS) or the Storage Access API.
- How to fix location and notification requests on page load
UX & conversion Call the permission APIs inside an event handler, never in a useEffect that runs on mount.
- How to fix “Prevents users from pasting into input fields”
UX & conversion Remove onPaste handlers that call preventDefault().
- How to fix distorted or blurry images (aspect ratio and resolution)
UX & conversion With fill, give the parent a size and use object-fit in style or a class. With width and height, pass the file's real dimensions.
- How to fix “Site isn't served over HTTPS”
Security Hosts such as Vercel and Netlify provision certificates automatically for custom domains. On your own server, use a reverse proxy (nginx, Caddy) with a Let's Encrypt certificate.
- How to fix an expiring or expired SSL certificate
Security On Vercel and Netlify, certificates renew automatically when the domain points to them. On your own server, check your certbot (or Caddy) renewal timer is running.
Handled by Next.js
Next.js controls these, so they can't be changed from your site's settings. If an audit flags one, the guide explains your options.
- How to fix a missing doctype or character encoding
Next.js always outputs <!DOCTYPE html> and <meta charset="utf-8">. If they're flagged, check for a custom server or proxy that alters the HTML.
See every guide on the fix guides page, or browse other platforms: Shopify, WordPress, Webflow, Wix, Squarespace.