Practical guide · 6 steps

Website audit checklist: checks you can do yourself

By Antoine Le Louët · Estimated reading : 9 min

First source version : · Content revision : · References

English version:

Choose an important page, open it like a visitor, and record what you see. This technical audit checklist helps you find concrete issues before running an automated tool.

Work on one URL, then repeat on a page of each important type (home, service, article, product). One page cannot describe an entire website.

Run an audit for automated checks

Tick boxes track your review; they do not validate any technical check. Progress resets when you reload the page.

0 / 6 steps marked

  1. Why it matters
    An unavailable page or a blocking screen cannot serve visitors.
    How to check
    Open the URL in a private window on desktop and mobile. Record the final URL, visible content, and response status in the browser Network panel.
    Expected result
    The intended page appears without a redirect loop or server error. Any intentional redirect leads to the correct URL.
    If it fails
    Fix the address, redirects, server, or a protection rule blocking legitimate visitors, then test again.
    What Argos checks — and its limit
    Argos records the HTTP response and some detectable blocks for the submitted URL. It cannot inspect signed-in areas or guarantee access from every network.

  2. Why it matters
    A useful search page may be excluded by mistake or point to another URL as its preferred version.
    How to check
    For a page intended for Google, check robots.txt, meta robots or X-Robots-Tag, the canonical link, and the sitemap. If you own the property, confirm the selected URL with Search Console URL Inspection.
    Expected result
    The intended page can be crawled and has no accidental noindex rule. Its canonical points to the preferred version; important URLs appear in the sitemap.
    If it fails
    Remove unintended blocks and align redirects, canonical, and sitemap. Keep intentional exclusions for private or low-value pages.
    What Argos checks — and its limit
    Argos detects robots.txt, sitemap, meta robots, and the presence of a canonical. It cannot know your editorial intent or prove that Google indexed the page or chose that canonical.

  3. Why it matters
    The title, visible headings, and links help readers and search engines understand its subject.
    How to check
    Read the title tag, meta description, H1, heading order, and internal links in the delivered HTML. Check text alternatives for informative images.
    Expected result
    The title and H1 describe the real content; headings are understandable; links lead to relevant pages; informative images have useful alternatives.
    If it fails
    Rewrite generic labels, repair structure and broken links, and add suitable alternatives to informative images.
    What Argos checks — and its limit
    Argos checks tags, headings, and the presence of alt attributes. It cannot judge writing quality, search intent, or the usefulness of an alternative.

  4. Why it matters
    A reliable connection and appropriate headers reduce some technical risks, without proving that a site is secure.
    How to check
    Inspect the certificate and final HTTPS URL in the browser. In the Network panel, examine response headers such as HSTS and Content-Security-Policy, and look for resources loaded over HTTP.
    Expected result
    The certificate is valid for the domain, sensitive pages use HTTPS, resources cause no mixed content, and declared protections fit the site.
    If it fails
    Renew or correct the certificate, redirect HTTP URLs, load resources over HTTPS, and test header changes so useful functions still work.
    What Argos checks — and its limit
    Argos checks TLS and several headers; external services may add findings. No warning is not a penetration test or a security guarantee.

  5. Why it matters
    Slow loading or delayed interaction makes visitors' tasks harder.
    How to check
    Load the page on mobile and a slower connection, then repeat with Lighthouse. Look for heavy images, blocking scripts, and layout shifts. Compare with field data when available.
    Expected result
    Main content appears without excessive delay, interactions respond, and the layout stays stable in the conditions tested.
    If it fails
    Optimize images and fonts, defer nonessential scripts, reserve space for late elements, and measure again after each change.
    What Argos checks — and its limit
    Argos collects browser metrics and Lighthouse scores for one run. This lab snapshot varies and does not replace real-user data, especially for interactivity.

  6. Why it matters
    A page can appear fine with a mouse while blocking people using a keyboard or assistive technology.
    How to check
    Use only a keyboard to test order, visible focus, menus, and forms. Check field and button names, text alternatives, and contrast, then try a screen reader on a key journey.
    Expected result
    Every essential action is understandable and possible without a mouse, with perceptible guidance and identifiable errors.
    If it fails
    Fix blocked journeys, unnamed controls, and invisible focus first; repeat a human check after the changes.
    What Argos checks — and its limit
    Argos reports automated signals and a Lighthouse score. It cannot certify WCAG compliance or a real user's experience on its own.

Example: what should you fix first?

On a product page, you find an accidental noindex rule, a heavy image, and a purchase button that cannot be reached by keyboard.

  1. Fix the blocked button: some visitors cannot complete an essential task.
  2. Remove noindex if the product should appear in search, then verify indexing in Search Console.
  3. Optimize the image, measure again on mobile, and monitor field data.

The actual order depends on user impact, your goals, and the cost of each fix. An overall score cannot replace that judgment.

Explore further

References to check your findings

Speed up the checks a tool can run

After your manual review, run a free audit of a public page. The private report gathers measurable signals; keep your notes for checks that require a person.

No account · One public page analysed

Put this diagnosis in context

The checklist complements automated analysis of one public URL. Signed-in areas and real journeys still need manual checks.

An automated score does not certify security or accessibility. Argos and Lighthouse use different scoring policies.

Understand the scoring method and limits

See evidence and corrections in the example