Auditsu Review: strong product, fixable gaps (86/100) — SiteList

Fact	Value
Domain	auditsu.com
Category	Accessibility compliance software for websites and mobile apps
Pricing	Freemium; £0–£197/month
Pages crawled	40
Crawl date	2026-08-30

Auditsu is a strong product site with an 86/100 overall score. Its clearest advantages are a specific positioning claim, audience-aware messaging, high usability, disciplined design execution, and a clean technical SEO foundation. The site also shows strong foundational accessibility, with no major P0 or P1 failures reported.

The main gaps are concentrated in the buying and delivery experience. Mobile loading takes 7.4 seconds despite a 1.8-second LCP, while the homepage's LCP image is the main performance bottleneck. The pricing page presents three plans side by side but offers limited help choosing among them. Writing quality is solid but loses force through presentation density. Traffic stability remains only partly assessable because the domain is less than one year old and several data sources are unavailable.

Auditsu makes a strong first impression because its promise is specific: “Accessibility compliance you run in-house.” The site names “the person who owns compliance” and supports that position with visible proof: backing from the Royal Academy of Engineering, funding from the UK Government, and a Google Cloud foundation. “No consultants, no £15,000 PDF” also establishes a clear contrast with consultancy-led work. The category is easy to understand as accessibility compliance software, and the pricing tiers reinforce the product framing. Competitive awareness is the remaining opening: a direct comparison section explaining how Auditsu differs from consultants would make the position easier to evaluate.

Auditsu’s messaging is unusually direct about who it serves. The /solutions page says it is “Built for the person who owns compliance, not the person who writes the code,” while the homepage frames accessibility compliance as something teams can run in-house. That audience choice gives the product copy a coherent job: explain guided checks, tickets, and recorded fixes in operational terms. Proof points such as UK Government funding, Royal Academy of Engineering backing, and Google Cloud support the message rather than interrupting it. Keep this audience language consistent across commercial pages, and add a concise comparison with consultant and widget approaches to sharpen the choice for buyers.

Auditsu is easy to use: the homepage states its value, navigation exposes Pricing, Compliance, and Resources, and visitors can find a trial or contact route without significant friction. The main usability cost is concentrated on the pricing page, where three plans use similar visual treatment and the Free option does not stand out at a glance. The contact form uses placeholder-only Name and Email fields, while Message has no label. Standardize primary CTA styling across the pricing page, give the Free plan a distinct visual hierarchy, and add explicit labels to the affected contact fields. These are small changes with a direct effect on confidence and completion.

Auditsu has a solid accessibility foundation: pages use header, nav, main, and footer landmarks; heading levels are sequential; and skip links are present. The supplied evidence reports no major P0 or P1 failures, with contrast, reflow, and motion handling appearing compliant. The remaining issues are technical and local: the marketing opt-in checkbox has aria-hidden=true without an accessible name, the resources search input uses only a visually hidden label, the mobile menu toggle lacks an aria-label, and footer links need clearer accessible names. Fix those controls with explicit labels or associated label elements, preserving the current structural patterns.

Auditsu’s design system is consistent across the sampled experience. The crawl found 79 distinct color values with only minor drift, coherent button and card radii, one H1 per page, visible focus states, and tap targets meeting 44px plus 8px separation. Mobile views showed zero horizontal scroll, inputs of at least 16px, and motion guarded by prefers-reduced-motion. The refinements are visual rather than structural: the hero blue measures 4.5:1 on white, mobile card padding varies between 8px and 16px, and pricing secondary headings sit at 24px beside a 36px H1. Normalize mobile padding and heading tokens; the foundation is already strong.

Auditsu’s performance is acceptable on desktop but needs mobile work: the homepage loads in 7.4 seconds on mobile, while CLS is 0.001. The main bottleneck is the hero image, served at 4032px into a 750px slot without srcset, responsive dimensions, or a preload. Thirteen blocking requests also include app.termly.io at 537KB and googletagmanager.com at 308KB. Optimize the hero image for the viewport, preload it with fetchpriority=high, and defer non-critical third-party scripts. Font unicode-range subsetting is a longer-term payload improvement.

Auditsu’s writing is strongest when it explains the product workflow plainly. The promise “Accessibility compliance you run in-house.” is audience-led, and the copy gives it substance through guided checks, tickets, and a statement. Scanability breaks down on the homepage: N1 reports 1,683 extracted words in one paragraph. Three legal pages also have a concrete heading defect, with missing H1s on /privacy, /terms, and /cookies. Split the long homepage block beneath its existing headings and add one descriptive H1 to each legal page. That preserves the direct voice while making the content easier to follow on mobile and with assistive technology.

The pricing page presents three options—Free, Beta, and Pilot Programme—across six feature axes, but it does not tell a buyer which plan fits a situation. Every listed capability uses a checkmark, so the grid supplies little tradeoff signal; the “Not sure which way to go?” prompt offers contact but not a recommendation. Add a recommendation layer explaining which plan fits different user types and situations; proposed scenarios could include small teams, growing teams needing mobile auditing, and enterprise clients needing custom audits. Replace all-checkmark rows with explicit limits or differences, then give each mobile plan card more type size and spacing.

Indexability is clean, but traffic stability is only partly assessable. RDAP records the domain registration as 2024-12-02, and the Wayback CDX API returned no rows, so there is no historical baseline in the supplied evidence. The accessibility compliance software category also carries medium exposure to AI overview and featured-snippet displacement because its content targets WCAG, EAA, and ADA standards. Optional resilience actions include monitoring indexing velocity and backlink acquisition, connecting GSC, and adding clear entity definitions, author credentials, and structured data where supported. These steps cannot remove new-domain volatility, but they create earlier signals and strengthen resilience as the site builds history.

Auditsu’s technical SEO foundation is strong across the assessed layers. HTTP, www, and trailing-slash variants consolidate through single-hop redirects; robots.txt allows public paths and declares the sitemap; and raw-versus-rendered comparison reports js_only_share: 0 with matching word counts across 40 sampled URLs. Security headers include HSTS, nosniff, X-Frame-Options: DENY, and a permissions policy, while marketing pages use s-maxage=31536000. The crawl bundle did not include Core Web Vitals or structured-data extraction, so those layers remain enrichment_pending.

Auditsu earns its strong score through clear positioning, strong usability, disciplined design, and clean technical foundations. Auditsu is aimed at the person who owns compliance and product teams.

Three improvements would make the buying experience more decisive: reduce the mobile loading burden around the LCP image, guide visitors through the three pricing plans instead of presenting an undifferentiated feature grid, and reduce presentation density in key copy. The result is already credible; these changes would make the evidence easier to act on.

This review uses the supplied crawl evidence and public dimension score summaries. The crawl covered 40 pages on 2026-08-30. Scores and claims in this frame are limited to the supplied public summaries.

Traffic stability is also only partly assessable because historical ranking data and other enrichment inputs were unavailable; GSC was not connected. Read more about this supplied crawl-based scope in How SiteList scores.