Explore a sample
website audit
report.

1. Missing meta descriptions on 3 pages [high · lower effort · DIY]

The pages /products, /about, and /contact have no meta description. Search engines may choose page content or other sources for the displayed snippet.

Fix: Write a specific, accurate description for each page and its likely query context. Keep it concise without forcing a fixed length or repeating keywords.

2. Duplicate title tags [high · DIY]

5 product pages share the title "Products | Demo Store", making distinct products difficult to identify in tabs and search results.

Fix: Use a consistent pattern such as "[Product Name] — [Category] | Demo Store" while keeping each title accurate and distinct.

3. Short category-page copy needs review [medium · DIY]

Category pages /shoes, /accessories, and /sale have fewer than 100 recorded words. Length alone does not show whether they satisfy shopping intent.

Fix: Review each category as a shopper. Add only useful guidance about range, fit, materials, filters, delivery, or selection when it helps the decision.

4. No structured data (Product schema) [medium · developer]

Product pages lack Product structured data, so they are not eligible through this markup for supported product enhancements.

Fix: Add accurate Product and Offer properties that match visible page content. Include review or aggregate-rating data only when genuine and compliant with the applicable guidelines.

5. Generic product-image filenames [low · lower effort · developer]

12 product images use generic filenames such as "IMG_4521.jpg", which makes asset identification and maintenance harder.

Fix: Use stable descriptive filenames such as "mens-leather-wallet-brown.jpg" where the deployment process supports renaming without broken references.

6. Canonical tags missing on faceted navigation pages [high · developer]

Filter URLs such as /shoes?color=black and /shoes?size=10 have no canonical declaration. Some combinations may duplicate the base category, while others may serve distinct demand.

Fix: Define a faceted-navigation policy. Canonicalize genuinely duplicate sort/filter states, preserve valuable indexable facets where justified, and align internal links, sitemaps, and crawl controls.

7. H1 tag missing or duplicated on 4 pages [medium · DIY]

The /about, /contact, /blog, and /sale pages either have no H1 or use the same H1 text as another page. Each page needs a unique, descriptive H1.

Fix: Give each page a clear primary heading that describes its topic or task. Avoid duplicate wording when the pages serve different purposes.

8. No hreflang annotations on localized pages [low · developer]

The fictional site inventory includes alternate localized URLs but no hreflang annotations connecting equivalent language or regional versions.

Fix: If the URLs are true localized equivalents, add reciprocal hreflang annotations with valid language or language-region codes and self-references.

1. 18 images missing alt text [critical · lower effort · DIY]

Informative product images in the sample homepage carousel and category grids have empty or missing alt attributes, so their content is not available to screen-reader users.

Fix: Add descriptive alt text to each informative product image (e.g., alt="Blue running shoes, side view, size 10") and keep decorative images correctly empty.

2. Insufficient color contrast on CTA buttons [high · lower effort · developer]

The "Add to Cart" buttons use #7CB342 green text on #F5F5F5 background, yielding a contrast ratio of 2.8:1 (minimum 4.5:1 required for WCAG AA).

Fix: Darken the green to at least #558B2F or use white text on a solid green background to meet WCAG AA standards.

3. Form inputs without associated labels [high · developer]

The newsletter signup and checkout forms use placeholder text instead of proper <label> elements. This breaks screen reader navigation.

Fix: Add programmatic labels associated through for/id. Use aria-label only when a visible label is not appropriate.

4. Missing skip navigation link [medium · lower effort · developer]

There is no skip-to-content link at the top of the page. Keyboard users must tab through the entire navigation on every page load.

Fix: Add a visually-hidden "Skip to main content" link as the first focusable element in the DOM.

5. Non-descriptive link text [medium · DIY]

9 links use generic text like "Click here" or "Read more" without context. Screen readers list links out of context, so these are meaningless.

Fix: Use descriptive link text like "Read our return policy" or "View the summer collection".

6. Focus indicators removed by CSS [low · developer]

The global stylesheet includes "outline: none" on interactive elements, removing the default focus ring for keyboard users.

Fix: Replace outline:none with a custom focus-visible style that meets WCAG 2.4.7 requirements.

7. Keyboard focus trap in cart slide-out modal [high · developer]

When the modal cart drawer opens, focus can move to controls behind the overlay and is not restored to the trigger when the drawer closes.

Fix: Implement the expected modal-dialog keyboard pattern: move focus into the drawer, keep it within the active modal, support Escape where appropriate, and restore focus on close.

8. Video content missing captions [high · developer]

The product demo video on the homepage has no closed captions or transcript. Deaf and hard-of-hearing users cannot access this content (WCAG 1.2.2).

Fix: Add synchronized captions, such as a WebVTT track, to prerecorded video with meaningful audio. Offer a transcript as an additional format where useful.

9. Heading hierarchy skips levels (H2 → H4) [medium · developer]

Product cards jump from H2 section titles to H4 headings. The visual and semantic outline needs review because heading levels should represent section nesting.

Fix: Use headings for document structure rather than text styling, and choose the level that accurately represents each section’s relationship to its parent.

10. Missing ARIA landmark roles [medium · developer]

The page lacks semantic HTML5 landmarks (<main>, <nav>, <footer>) or equivalent ARIA role attributes. Assistive technology users cannot jump between page sections.

Fix: Add role='main' to the content wrapper, role='navigation' to nav elements, and role='contentinfo' to the footer — or use native HTML5 elements directly.

11. HTML lang attribute not declared [low · lower effort · developer]

The <html> element has no lang attribute. Screen readers cannot select the correct language profile, leading to mispronounced content for non-English users.

Fix: Add lang="en" (or the appropriate BCP 47 language tag) to the <html> element: <html lang="en">.

1. Missing Content-Security-Policy header [high · developer]

No Content-Security-Policy header is present, so the site lacks this browser-enforced control for restricting approved resource sources and related behaviors.

Fix: Design a policy for the site’s actual resources, deploy it in report-only mode, resolve violations, and then enforce a tested Content-Security-Policy.

2. X-Frame-Options header not set [medium · lower effort · developer]

Without X-Frame-Options or frame-ancestors CSP directive, the site can be embedded in iframes on other domains, enabling clickjacking attacks.

Fix: Add "X-Frame-Options: DENY" or "Content-Security-Policy: frame-ancestors 'none'" to prevent framing.

3. Permissions-Policy header missing [low · lower effort · developer]

No Permissions-Policy header is set, so the site has not explicitly limited access to selected browser features by origin.

Fix: Add a Permissions-Policy header restricting unused features: "camera=(), microphone=(), geolocation=()".

1. 14 pages with short copy need intent review [high · DIY]

Category and product-listing pages average 87 recorded words. Word count alone does not determine usefulness, quality, or search performance.

Fix: Review whether each page answers the shopper’s questions. Add original selection guidance, sizing, materials, delivery, or care information only where useful.

2. Limited editorial coverage [high · DIY]

The fictional crawl found 2 blog posts and no evidence of several customer-question formats. It did not analyze competitors, search demand, or an editorial strategy.

Fix: Use customer questions, Search Console data, product expertise, and independent keyword research to decide whether new guides are worthwhile. Publish to a sustainable quality-led cadence.

3. Product descriptions copied from manufacturer [medium · DIY]

23 product pages use duplicate manufacturer descriptions. This creates duplicate content across the web and provides no unique value to search engines.

Fix: Rewrite product descriptions with unique copy: highlight real benefits, include customer use cases, and add size/fit guidance.

4. Missing FAQ sections on key pages [medium · lower effort · developer]

No Q&A sections were found on the reviewed product, category, or shipping pages. Those pages may still answer their intended questions without an FAQ.

Fix: Add concise FAQs only for recurring questions not answered elsewhere. Use FAQ structured data only when the page and site are eligible and the markup matches visible content.

5. Average reading level too complex [low · DIY]

Sample body copy averages Flesch-Kincaid grade 14. A formula cannot determine whether the terminology is appropriate for the intended shopper.

Fix: Review representative copy with target readers. Prefer direct sentences, explain necessary specialist terms, and use headings and short paragraphs to support scanning.

1. Checkout reassurance needs manual review [critical · lower effort · developer]

The fictional checkout does not visibly explain accepted payments, returns, support, delivery timing, or transaction security in the reviewed viewport.

Fix: Show accurate payment, delivery, returns, support, and security information where shoppers need it. Do not add decorative badges, guarantees, or review counts that cannot be verified.

2. Product availability context needs review [high · DIY]

The sample product pages do not explain stock status or time-sensitive delivery cutoffs. A lack of scarcity language is not itself a defect.

Fix: Show inventory, delivery cutoffs, or capacity only when the data is current and useful. Do not manufacture low-stock, countdown, viewer, or purchase signals.

3. No email-subscription route detected [high · developer]

The fictional site has no detected email-subscription form. This matters only if email retention is part of the customer strategy and a relevant consent basis and notice are in place.

Fix: If visitors would value updates, test a clear, non-intrusive subscription offer and explain what they will receive. Do not default to an interruptive popup or unverified discount.

4. Add-to-cart button below the fold on mobile [medium · lower effort · developer]

On mobile devices (375px width), users must scroll 2-3 screens before reaching the Add to Cart button on product pages.

Fix: Review the product-information order and test whether a persistent purchase action helps without obscuring options, pricing, validation messages, or content.

5. Product listings show limited decision context [medium · developer]

Category pages show product images, names, and prices but no verified review summary or other comparison context.

Fix: If genuine review data is available and useful, display an accurate summary with its count. Never invent ratings, purchases, popularity, scarcity, or customer activity.

6. Breadcrumb navigation missing [low · lower effort · developer]

No breadcrumb navigation is present on the sample product and category pages, making the current hierarchy less explicit.

Fix: If the catalog hierarchy is meaningful, add visible breadcrumbs and matching BreadcrumbList structured data with accurate URLs and names.