Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Web resources

    Performance, accessibility and quality

    Quality tools reveal speed, accessibility and stability issues, but no score replaces a real person completing a task. Compare lab and field data when the latter is available.

    Measure one page on a phone, then complete a task by keyboard and with larger text. Link findings to a specific component or piece of content before fixing them.

    AI-generated illustration

    Editorial method

    A directory made to be useful, not merely long.

    Selection prioritises recognition within the field, professional use and reference status. Highly specialised documentation entries are consolidated under their main resource.

    01

    Official foundations

    Standards bodies, official documentation and public authorities are used as primary reference points.

    02

    Professional tools

    Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.

    03

    Independent reading

    Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.

    Before choosing

    Compare on three practical questions

    Performance, accessibility and quality
    CriterionQuestion to resolve
    Test typeDoes the result come from a laboratory test, field data or human assessment?
    JourneyDo contact, search and navigation remain usable with a keyboard and on mobile?
    PriorityWhich problem blocks a user and which fix can be verified?

    Keep a short decision record: requirement, source, observed result and unresolved point. Test the same task with each candidate instead of comparing marketing lists of features.

    Search and filter

    Official starting points for this topic

    Compare their role and documentation before selecting a tool. Inclusion is not a ranking.

    11 resources displayed

    The date applies to the linked document, not to a review of every service feature.

    Performance, accessibility and quality

    web.dev

    Learning paths covering Web development fundamentals, performance and accessibility. Useful for studying a topic through explained examples. Select a module for the task to improve, then compare the exercise with your own site’s content, constraints and users.

    web.dev · Source consulted

    Use it for : Connect performance or accessibility guidance to a measurement on your pages.

    InternationalMedia / news
    web.devVisit official website
    Performance, accessibility and quality

    PageSpeed Insights

    URL analysis combining Lighthouse diagnostics with field data where available. Useful for distinguishing a simulated trial from historical observations at page or origin level. Record the displayed scope and test conditions before comparing results.

    PageSpeed Insights · Source consulted

    Use it for : Separate field and lab data, then check the relevant URL and device before prioritising fixes.

    Documented characteristics
    Application covered
    CrUX · Lighthouse
    Metrics
    LCP · INP · CLS

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    If PageSpeed shows origin data rather than URL data, the result covers a set of pages on the site. It does not prove that the examined page performs the same way. Record the displayed scope before choosing a correction.
    Useful check
    The CrUX panel describes experiences observed over the previous 28 days; Lighthouse runs a simulated test at a particular moment. Keep the URL, device type, scope and report date separate. A recent fix may change the test before older experiences leave the field window.
    Interpretation and next step
    Missing field data means the available sample cannot support that report. It is neither a zero score nor a pass. Use lab diagnostics to investigate a cause, then follow field data when it becomes available.

    Official documentation ·

    InternationalTool / software
    pagespeed.web.devVisit official website
    Performance, accessibility and quality

    Lighthouse

    Automated page checks for performance, accessibility, best practices and SEO. Useful for identifying reproducible issues and tracking fixes under defined conditions. Scores replace neither journey testing nor a full accessibility evaluation and can vary between runs.

    Lighthouse · Source consulted

    Use it for : Use diagnostics to find reproducible causes and compare tests under similar conditions.

    Documented characteristics
    Modes
    Chrome DevTools · CLI · Node
    Checks
    Performance · Accessibility · SEO
    Command
    lighthouse <URL>

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: a Lighthouse Performance score rises from 72 to 84. The team wants to announce a website that is “12% faster”.
    Useful check
    The difference is 12 score points, not a 12% reduction in loading time. Examine underlying measurements, settings and several comparable runs before stating an outcome.
    Interpretation and next step
    Metrics contribute to the Performance score through weighting; the number of recommendations or diagnostics is not deducted directly. Also check the actual journey after the change.

    Official documentation ·

    Official documentation · Chrome — Lighthouse performance scoring

    InternationalTool / software
    developer.chrome.comVisit official website
    Performance, accessibility and quality

    WebPageTest

    Detailed page-load testing from multiple devices and locations.

    WebPageTest — GitHub · Source consulted

    Use it for : Inspect loading and network waterfall for a defined scenario and location.

    Documented characteristics
    Modes
    First View / Repeat View
    Configuration
    Location, browser, connection and runs
    Checks
    Compare matching views and settings

    Verification path

    1. Fix the conditions
    2. Separate first and repeat views
    3. Compare the traces

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    The table gives three fictional runs with LCP in seconds. Location, browser, connection and content are assumed constant. First and repeat visits represent distinct cache conditions.
    Useful check
    The separate medians here are 3.3 and 1.9 seconds. Compare the same measure with matching settings; selecting the best first view against a median repeat view would distort the comparison. These values do not measure a real website.
    Interpretation and next step
    Relate the difference to the request waterfall and reused resources. Repeat the same conditions after a targeted change. A faster repeat visit does not show that every visitor gets that result.
    Fictional runs · LCP in seconds
    RunFirst visitRepeat visit
    13.21.8
    23.42.0
    33.31.9

    Official documentation ·

    InternationalTool / software
    webpagetest.orgVisit official website
    Performance, accessibility and quality

    W3C HTML Validator

    Checks document markup syntax and explains detected errors. A valid result is neither a quality seal nor a complete accessibility assessment.

    W3C — Markup Validator Help · Source consulted

    Use it for : Start with the first errors, which may produce cascading messages. Check that the tested document matches the served page, then revisit keyboard use, forms and reading: these journeys require checks beyond syntax.

    Documented characteristics
    Checker
    Nu Html Checker
    Format
    HTML · JSON
    Certification
    This check does not issue certification
    Headers
    Content-Type: text/html; charset=utf-8
    Syntax
    out=json

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    To check a demonstration page with Nu Html Checker, a POST request body can contain the HTML directly, with Content-Type: text/html; charset=utf-8. The out=json parameter requests a structured report. Distinguish the submitted document from the returned report and retain the examined page version.
    Useful check
    In a fictional report, inspect the messages array and the type field. An error entry identifies a detected problem; non-document-error means checking could not complete. The latter must not be presented as an error-free page: the result remains indeterminate.
    Interpretation and next step
    Messages and their positions help locate the source to fix. Run the check again after editing, then verify keyboard use, content and useful functions. No validator errors is neither accessibility certification nor a guarantee of functionality or search-engine rankings.

    Official documentation ·

    Official documentation · Nu Html Checker — POST body

    Official documentation · Nu Html Checker — JSON output

    InternationalTool / software
    validator.w3.orgVisit official website
    Performance, accessibility and quality

    Can I Use

    Browser- and version-specific support tables for Web technologies. Useful before choosing an API or CSS feature and for reading compatibility qualifications. Usage shares depend on the selected population; then test the feature and fallback in required environments.

    Can I Use · Source consulted

    Use it for : Check feature support for the browsers used by the intended audience.

    Documented characteristics
    Scope
    Feature, browser and version
    Status
    Primary support; read the notes
    Source
    tests.caniuse.com

    Verification path

    1. Choose the feature and versions
    2. Read notes and plan a fallback
    3. Test the actual component

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional case: a card grid uses subgrid. Record the exact feature and target browsers and versions before reading the table. A global percentage alone does not describe the project’s audience.
    Useful check
    Read the notes attached to the cells. Support means the main purpose is largely usable; it does not guarantee every edge case. Prepare a fallback layout that keeps the cards readable.
    Interpretation and next step
    Then try long content, zoom and component navigation in the selected environments. The support table prepares this verification; it does not run it on your interface.

    Official documentation ·

    InternationalCommunity / learning
    caniuse.comVisit official website
    Performance, accessibility and quality

    axe

    Deque tools for automating accessibility checks in different development and testing contexts. Useful for finding known issues in the states examined. Identify the product, scope and remaining manual checks instead of inferring general conformance from no alerts.

    axe · Source consulted

    Use it for : Pair automated findings with human review of the journey.

    Documented characteristics
    Application covered
    axe-core
    Status
    violations / incomplete / passes / inapplicable
    Scope
    Rendered content in the tested state
    Checks
    Manual review of undetermined results

    Verification path

    1. Display the state to test
    2. Classify the results
    3. Check the task manually

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    A fictional axe-core report contains violations: [] and an incomplete result. The latter needs further checking; it does not become a pass because the violations array is empty.
    Useful check
    Keep the engine version, scope and interface state. Open the relevant menu or dialog before rerunning analysis: a panel that remains hidden is not checked as its displayed state.
    Interpretation and next step
    Inspect the target and rule of the undetermined result, then record your manual check. inapplicable means no content matching that rule was found. Complement automation with keyboard journeys and relevant human checks.

    Official documentation ·

    InternationalTool / software
    deque.comVisit official website
    Performance, accessibility and quality

    WAVE

    Visual page evaluation highlighting accessibility findings and information needing manual review. Useful for locating elements, structure and alternative-text meaning. No automated tool checks every criterion; supplement it with reading, keyboard use and actual tasks.

    WAVE · Source consulted

    Use it for : Review alerts in context, then add keyboard, screen-reader and journey-comprehension checks.

    Documented characteristics
    Application covered
    WAVE
    Validation
    This check does not issue certification

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    An image has alternative text, so WAVE does not report it as missing. That result does not say whether the text conveys the right information. Compare the image, its purpose on the page and the text read without the image.
    Useful check
    Read the documentation for each icon: an alert requires judgement, while an identified accessibility feature may still be misused. Add a keyboard journey and tests of form error states.
    Interpretation and next step
    For local, dynamic or protected pages, WAVE extensions can examine the page in the browser. Reproduce relevant states before checking. No detected errors does not constitute a conformance certification.

    Official documentation ·

    InternationalTool / software
    wave.webaim.orgVisit official website
    Choose a starting point

    What each category helps you decide.

    These examples illustrate uses, not rankings or endorsements. Verify each provider’s current documentation and terms before a decision.

    Performance, accessibility and quality

    Quality tools reveal speed, accessibility and stability issues, but no score replaces a real person completing a task. Compare lab and field data when the latter is available.

    Questions to check
    • Measure different page families and devices.
    • Connect each finding to a cause and an affected journey.
    • Distinguish field measurements, laboratory runs and manual review rather than combining them into one score.

    A practical use : Measure one page on a phone, then complete a task by keyboard and with larger text. Link findings to a specific component or piece of content before fixing them.

    What this cannot prove : A lab score varies with its environment and cannot describe all visitors. Automated checks do not cover every accessibility barrier.

    Examples : web.dev · PageSpeed Insights

    Related guide : Test website accessibility through real tasks

    Explore troubleshooting situations

    Troubleshooting methods

    Quality tools help locate a defect; validation concerns a task that can actually be completed. Preserve the device, width, context and actions for each trial. These situations connect a score or file to an observable difficulty.

    A good score conceals a keyboard barrier

    What you observe
    An automated report is reassuring, but a menu, filter or window closure prevents task completion using a keyboard.
    Before drawing a conclusion
    Automated and manual checks do not cover identical barriers. A successful report does not replace observing the task.
    Verification step
    Complete the action from the beginning with a keyboard. Record focus order, visibility, announced state and a way out of the component. Connect each barrier to the relevant check and retest after correction.

    A small photograph still downloads a large file

    What you observe
    The image occupies little space on a mobile page, but the browser retrieves a version much larger than its display warrants.
    Before drawing a conclusion
    Reducing CSS width changes presentation, but not necessarily the transferred file. Offered variants and the browser’s actual selection need inspection.
    Verification step
    Compare displayed width, resource dimensions, the actual loaded file and transferred size. Test several viewport widths and screen densities. Also check cropping and alternative text after optimisation.

    Lab results and user feedback disagree

    What you observe
    Your tests are fast, while some visitors report slow opening or elements moving during reading.
    Before drawing a conclusion
    A local trial reflects its own conditions. Visitors may use different devices, networks, caches or stages of a task.
    Verification step
    Reproduce a first load, slower connection and representative page with long content. Compare available field data while preserving its period and coverage; do not claim a universal experience from one trial.
    Another case to examineThe mobile menu works, but enlarged text blocks the task
    Situation
    The phone check passes, then text enlargement hides confirmation or overlaps buttons. A narrow screen is not the only state to examine.
    Before drawing a conclusion
    A mobile screenshot does not establish support for enlargement. Lost information and exceptions for tables must be assessed in context.
    Practical check
    Enlarge the content and repeat the task with a keyboard. Record the first inaccessible element and its container; correct the layout, then check messages and actions again.

    Reference : W3C · Reflow

    Further documentation

    Keep useful data when changing tools

    Before making a resource part of website operations, plan for updates and an exit too. These checks concern your trial results without assuming features or prices of a particular plan.

    Keep test conditions

    Retain URL, viewport, browser, date and measurement mode. A lab result without conditions cannot be compared reliably with another run.

    Export useful defects

    For each retained defect, keep steps, expected result and impact. A score disappearing from a tool does not prove a fix.

    Change methods

    Repeat representative manual checks. A tool update can change its rules even when the page is unchanged.

    Transparency

    Editorial scope and third-party websites

    This non-exhaustive directory had its data consistency and links checked on 2 October 2026. Some websites restrict automated checks. It contains external links to independent websites. Their availability, content, prices, cookies and terms may change. Française du Numérique does not control them and receives no commission for their inclusion.

    Directory questions

    Selection, independence and updates.

    Entries describe resources from their publishers’ pages and provide a source, category, purpose and checking date. The selection covers different Web tasks rather than ranking every available provider. Open the cited source to check current scope, availability and conditions before relying on a service.

    No. Inclusion identifies a resource to examine; it does not certify every feature, price, policy or result. Compare the resource with your actual task, country, language and technical requirements. Confirm current conditions with its publisher before committing time, data or money.

    Yes. Search the displayed catalogue, combine the available filters and clear them to return to the full list. Every entered word must match the indexed text. The visible result count describes this selection, not the entire Web. Individual category pages and direct links remain available without JavaScript.

    Record the URL, viewport width and height, zoom level, language and preceding steps. A screenshot alone may not describe the cause. Include the expected result and affected element, then verify the fix in the same context.

    Start with the changed component and page families sharing its rules. Cover mobile, desktop, long text and relevant languages. Broaden checks when the change affects a global rule, causes a regression or leaves uncertainty about other templates.

    Compare using observable evidence

    Before choosing a resource, run a limited trial using the same data and task. Keep the outcome and its limitations rather than a ranking based on familiarity.

    Run the same task on mobile, with a keyboard and using the chosen inspection tools. Keep page, device, conditions and observed obstacle. An automated score does not replace a journey check; connect each issue to a tested correction.

    Use precise terms

    Two distinctions before comparing resources

    An image’s meaning and the version actually displayed concern different aspects of quality.

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    WCAG 2.2 · 1.4.3
    4.5:1 / 3:1Normal / large text (18 pt or 14 pt bold); criterion exceptions apply.
    WCAG 2.2 · 2.5.8
    24 × 24 CSS pxA smaller target can satisfy the criterion through spacing; other exceptions apply.
    WCAG 2.2 · 1.4.10
    320 CSS pxVertical content without two-dimensional scrolling; exceptions cover inherently two-dimensional content.
    WCAG 2.2 · 3.3.7
    A · same processWithin one process, previously supplied information must be auto-populated or available to select, subject to the criterion’s exceptions. Browser autocomplete alone is insufficient; the site must offer the information already received or avoid requesting it again.

    Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.