Website Audit Guides for Developers

Guides for website audits

• Website launch checklist for developers

  Use this website launch checklist to verify redirects, crawl controls, metadata, accessibility, forms, performance, and monitoring before release.

• Mobile website testing before launch

  How to test a website on mobile before launch, including layout, navigation, text, tap targets, and common desktop-only mistakes.

• Robots.txt vs sitemap.xml: what each file does

  A developer guide to robots.txt and sitemap.xml, when to use each file, and how to keep their crawl instructions consistent.

• How Slop Audit audits a public website

  See how Slop Audit checks a website, what it measures, and how the report helps developers fix issues.

• Website audit report example: a practical template

  Use this website audit report example to turn reachability, SEO, UX, accessibility, and content evidence into prioritized fixes before launch.

• Accessibility checks before launch for developers

  An accessibility checklist for developers covering headings, labels, focus, contrast, target size, and automated-check limits.

• Core Web Vitals for developers: LCP, INP, and CLS guide

  Learn what LCP, INP, and CLS measure, how to test Core Web Vitals, and how to fix common performance problems before you ship a page and compare each release.

• Canonical URLs and redirects: a practical developer guide

  Learn how canonical URLs, redirects, and internal links work together so search engines index the page version you want to publish and avoid duplicate routes.

• Open Graph meta tags: a practical guide for developers

  Set up Open Graph title, description, image, and URL tags so shared links show the right preview, with a production test checklist.

• JSON-LD structured data: a practical developer guide

  Learn how to add JSON-LD structured data, choose a page type, validate it, and avoid markup that does not match visible page content.

• Website form testing checklist: developer QA guide

  Test website forms before launch: labels, validation, keyboard use, errors, redirects, analytics, and success states users can verify on desktop and mobile.

• Website regression testing checklist for developers

  Use this website regression testing checklist to compare routes, metadata, mobile layouts, accessibility, crawl controls, and performance after every release.

• Website security headers: a pre-launch checklist

  Use this website security headers checklist to test CSP, HSTS, MIME sniffing, referrer, and browser permission controls on the deployed URL before launch.

• How to check broken links before launch

  Learn how to check broken links before launch, test redirects and 404 responses, add a focused CI check, and verify the deployed page with clear evidence.

• Website favicon checklist: icons, manifest, and launch tests

  Use this website favicon checklist to verify favicon HTML, Apple touch icons, web app manifest identity, caching, and deployed responses before launch.

• Website image optimization checklist: launch QA

  Use this website image optimization checklist to resize responsive images, choose efficient formats, prevent layout shifts, write alt text, and test production.

• Title tag and meta description: developer checklist

  Use this title tag and meta description checklist to write unique search metadata, render it in HTML, and test production pages before launch.

• llms.txt example: setup and testing guide

  Use this llms.txt example to create a concise site guide for agents, publish it at the right path, test the response, and keep its links accurate over time.

• JavaScript console errors: pre-launch guide

  Use this JavaScript console errors guide to find page exceptions and failed requests, debug them in DevTools, and add a focused Playwright check before launch.

• HTML heading structure: developer testing guide

  Use this HTML heading structure guide to order H1-H6 tags, find skipped levels, test rendered pages, and keep accessible headings in your release checks.

• Keyboard accessibility testing: developer checklist

  Use this keyboard accessibility testing checklist to verify focus order, visible focus, controls, dialogs, and keyboard traps before you launch a website.

• Color contrast accessibility: developer guide

  Use this color contrast accessibility guide to apply WCAG ratios, test rendered states, fix CSS color tokens, and catch regressions before launch.

• Touch target size: WCAG and mobile testing guide

  Use this touch target size guide to apply WCAG rules, fix small buttons and links, test mobile controls, and catch spacing problems before launch.

• Website content audit checklist for developers

  Use this website content audit checklist to remove placeholder copy, clarify claims and actions, add proof, and test production pages before launch.

• Accessible name: HTML and ARIA testing guide

  Use this accessible name guide to label buttons, links, and form controls, avoid ARIA conflicts, test production HTML, and catch failures before launch.

• Website navigation testing checklist for developers

  Use this website navigation testing checklist to verify labels, landmarks, destinations, mobile menus, keyboard access, and critical routes before launch.

• Website audit with GitHub Actions: CI setup guide

  Run a website audit with GitHub Actions to check a deployed URL, protect the audit token, review evidence, and enforce a useful pull request gate.

• Cookie banner accessibility: developer checklist

  Use this cookie banner accessibility checklist to test dialog semantics, keyboard flow, focus, controls, target size, contrast, and production behavior.

• XML sitemap validation: a pre-launch test for developers

  Use this XML sitemap validation checklist to test the deployed response, parse URL entries, catch stale or noncanonical pages, and verify discovery before launch.

• HTML lang attribute: accessibility testing guide

  Use this HTML lang attribute guide to choose a BCP 47 language tag, handle multilingual content, test production HTML, and catch missing declarations.

• HTML landmarks: accessibility testing guide

  Use this HTML landmarks guide to structure header, navigation, main, aside, and footer regions, label repeated landmarks, and test the rendered page.

• Viewport meta tag: responsive design testing guide

  Use this viewport meta tag guide to configure width and scale, protect browser zoom, test responsive layouts, and catch mobile overflow before launch.

• Soft 404: how to find and fix it before launch

  Learn how to find and fix a soft 404, return the right HTTP status, test custom 404 pages, and prevent crawl and monitoring errors before launch.

• CSS hover states: test buttons and links before launch

  Use CSS hover states to give controls clear pointer feedback, preserve keyboard focus, and test deployed buttons and links with Playwright before launch.

• Cumulative Layout Shift: how to find and fix CLS

  Learn how to find and fix Cumulative Layout Shift, reserve space for images and dynamic content, test CLS in production, and prevent regressions.

• Largest Contentful Paint: how to improve LCP

  Learn how to improve Largest Contentful Paint by finding the LCP element, fixing request and render delays, testing production, and preventing regressions.

• JavaScript long tasks: how to find and fix them

  Learn how to find and fix JavaScript long tasks, reduce main thread blocking, measure a lab proxy, and prevent responsiveness regressions before launch.

• Website performance budget: a practical developer guide

  Build a website performance budget for page weight, requests, Core Web Vitals, and CI so your team can catch regressions before every release.

• WebMCP testing: a pre-launch checklist for developers

  Use this WebMCP testing checklist to inspect document.modelContext, tool discovery, schemas, security annotations, lifecycle, and production registration.

• Robots.txt testing: a practical developer guide

  Use robots.txt testing to verify the deployed file, test crawler rules against real URLs, catch accidental blocks, and keep checks in CI.

• Alt text testing: a practical developer guide

  Use alt text testing to find missing attributes, review image purpose, test rendered pages, and keep useful image alternatives in CI before launch.

• Website CTA checklist: test labels and destinations

  Use this website CTA checklist to test call-to-action labels, destinations, accessibility, mobile behavior, and safe first-task paths before launch.

• Horizontal overflow CSS: find and fix mobile scrolling

  Debug horizontal overflow CSS on deployed pages, fix flex and grid sizing, contain wide content, and test mobile layouts for regressions before launch.

• Noindex tag: find and fix accidental indexing blocks

  Find a noindex tag in HTML or HTTP headers, fix accidental production blocks, and test indexing directives in CI before launching your website.

• Mixed content errors: find and fix HTTPS launch failures

  Find mixed content errors on HTTPS pages, repair insecure asset and API URLs, verify browser behavior, and add focused checks before a website launch.

• Cache-Control header: prevent stale website deployments

  Use the Cache-Control header to set HTML and asset policies, debug stale deployments, verify CDN responses, and add focused release checks.

• Skip link: HTML, CSS, and keyboard testing guide

  Build a skip link that bypasses repeated navigation, reveals itself on focus, reaches main content, and keeps working after route changes and deployment.

• CSP testing: verify a policy before enforcement

  Use CSP testing to inspect deployed headers, collect report-only violations, fix blocked resources, and check browser tasks before enforcing a policy.

• prefers-reduced-motion: CSS, JavaScript, and testing

  Implement prefers-reduced-motion in CSS and JavaScript, preserve usable states, and test animation preferences before launching your website.

• HSTS header: setup, testing, and safe rollout

  Set up the HSTS header, choose host coverage and max-age, test deployed HTTPS responses, and plan rollback before launching your website.

• JavaScript MIME type error: fix scripts served as HTML

  Fix a JavaScript MIME type error by checking asset responses, SPA rewrites, build paths, and stale releases, then add deployed script checks to CI.

• font-display: choose swap, fallback, or optional

  Choose font-display settings for readable text, compare swap, fallback, and optional, and test slow or failed font loads before launching your website.