This report was prepared for cometweb.io. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
Score up 4 since Nov 15, 2026 (94 → 98). Fixed: Privacy policy is missing 1 expected disclosure. New: No postal address for the business.
Clean bill of health since Oct 2, 2026, serial WO-2026-0329. View the certificate
Opportunities
These are the issues most likely to matter to a regulator, an app store, or an attacker. Fix them first.
Elements must meet minimum color contrast ratio thresholds (7 elements)~40 min
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Example: <span class="hiw-chip svelte-lrh373" style="--d: 0.55s">Perf</span>
WCAG wcag2aa, wcag143. Web accessibility is enforced under the ADA (US, thousands of private suits a year), Section 508, the European Accessibility Act, the UK Equality Act, and AODA (Ontario).
Diagnostics
Worth fixing. Not an emergency.
No postal address for the business~5 min
Sites that take money or serve EU/German users are expected to show who runs them and where. It also unblocks Stripe and app-store reviews.
GDPR Art. 13(1)(a) (controller identity); German TMG §5 Impressum; EU e-Commerce Directive Art. 5; consumer-protection rules in most countries.
What these findings expose you to
For scale: the privacy items fall under GDPR's top tier (up to 4% of turnover; small-business fines for missing notices and cookie consent have run from the low thousands of euros upward) and, for California users, CalOPPA at up to $2,500 per violation and CCPA at roughly $2,500 to $7,500 per violation once you pass its thresholds; the accessibility violations are the kind that draw private ADA suits, thousands a year, usually settled for $5,000 to $25,000 plus the plaintiff's fees. In practice the first step is almost always a complaint and a notice with a deadline; the cost comes from ignoring it. These are published maximums and reported ranges, not a prediction.
GDPR / UK GDPR, transparency and consent · EU, EEA, UK1 finding
Maximum. Up to €20 million or 4% of worldwide annual turnover, whichever is higher (Art. 83(5)); UK: up to £17.5 million or 4%.
Usually. A complaint to a data-protection authority, then a notice with a deadline to fix. Published fines against small businesses for missing notices and cookie consent have run from the low thousands of euros upward; the largest cookie-consent fines have been in the tens of millions.
Applies: Any site with users in the EU or UK, regardless of where the company is. Enforced by regulators.
ADA Title III and California's Unruh Act (web accessibility) · United States1 finding
Maximum. The ADA carries no fixed fine for private suits, but the defendant typically pays the plaintiff's attorney fees; California's Unruh Act adds statutory damages of $4,000 per violation. DOJ actions can carry civil penalties up to $75,000 for a first violation.
Usually. Thousands of private lawsuits a year, most against small and mid-sized sites, usually settled for roughly $5,000 to $25,000 plus fees. Fixing the automated violations is the cheapest defence.
Applies: Any business website in the US; California residents can sue under Unruh. Enforced by regulators and private plaintiffs.
European Accessibility Act / UK Equality Act / AODA · EU, UK, Ontario1 finding
Maximum. Set by each EU member state since June 2025; AODA penalties up to CA$100,000 per day for corporations; UK Equality Act claims are private.
Usually. Complaints and compliance orders first; fines are reserved for refusal to fix.
Applies: Consumer-facing digital services in the EU; Ontario organisations; UK service providers. Enforced by regulators and private plaintiffs.
AI design tells
138 patterns on this page read as AI-generated: AI color palette, Glowing shadow accents, Decorative radial spotlight glow. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

AI color palette85×
Purple/violet gradients and cyan-on-dark are the most recognizable tells of AI-generated UIs. Choose a distinctive, intentional palette.
Example: Purple/violet neon text on dark background
Glowing shadow accents25×
Colored glow shadows — a zero-offset chromatic halo (box- or text-shadow) on any background, or any colored blurred shadow on a dark background — are the default "cool" look of AI-generated UIs. Use neutral elevation shadows and subtle, purposeful lighting instead.
Example: Zero-offset box-shadow glow (#05f29b)
Decorative radial spotlight glow14×
A soft, low-opacity accent-colored radial gradient fading to transparent, dropped behind a hero or section as a "spotlight." It is a reflex AI decoration — the translucent cousin of the saturated radial halo. Let the surface stand on its own, or light the composition with a deliberate material accent rather than a floating colored haze.
Example: radial-gradient spotlight glow "home-hero" (#05f29b a0.18 → transparent) on 1280x678 surface
Kicker / eyebrow label above heading7×
A tiny tracked uppercase or small-caps label sitting as its own block directly above a heading is banned outright, repeated or not. Generated kickers never earn their place: the heading carries its own weight. Delete the label and let the heading speak; if the words matter, work them into the heading or the body.
Example: kicker "How Insight works" above h2 "From a site URL to a verified fix."
Gradient text2×
Gradient text is decorative rather than meaningful — a common AI tell, especially on headings and metrics. Use solid colors for text.
Example: background-clip: text + gradient
Nested cards2×
Cards inside cards create visual noise and excessive depth. Flatten the hierarchy — use spacing, typography, and dividers instead of nesting containers.
Example: Card inside card
Hairline border with wide shadow1×
A hairline border paired with a wide, diffuse shadow is a recurring generated-UI signature. Commit to one — a defined edge or a soft elevation — rather than both at once.
Example: 1px border + 28px shadow blur
Pulsing status dot1×
Small pulsing status dots simulate liveness decoratively. Reserve pulse animation for indicators tied to genuinely live, changing data; a static indicator with clear labeling is honest and calmer.
Example: .hiw-status-dot.svelte-lrh373 — 7x7px dot with infinite "svelte-lrh373-hiw-dot-pulse" animation
Decorative grid-line background1×
A decorative grid or line-field background drawn with hairline linear-gradient layers tiled by a fixed pixel cell is a recurring generated-UI signature. Reserve grid overlays for actual canvas, map, blueprint, or measurement surfaces; elsewhere use product structure or a plain surface.
Example: two-axis grid-line gradient background
Line length too long · quality12×
Text lines wider than ~80 characters are hard to read. The eye loses its place tracking back to the start of the next line. Add a max-width (65ch to 75ch) to text containers.
Example: ~113 chars/line (aim for <80)
Low contrast text · quality10×
Text does not meet WCAG AA contrast requirements (4.5:1 for body, 3:1 for large text). Increase the contrast between text and background.
Example: 4.3:1 (need 4.5:1) — text #034c32 on #04c27c
Layout property animation · quality7×
Animating width, height, padding, or margin causes layout thrash and janky performance. Use transform and opacity instead, or grid-template-rows for height animations.
Example: transition: width
Cramped padding · quality5×
Text is too close to the edge of its container. Two shapes: (1) an element with its own text where the padding is too low for the font size, and (2) a wrapper with text-bearing children and near-zero padding against a visible boundary (border, outline, or non-transparent background) — children land flush against the boundary line. Add at least 8px (ideally 12–16px) of padding inside bordered, outlined, or colored containers.
Example: <div> "dapp": children flush against bg on bottom (no inset)
Undersized functional text · quality3×
Interactive and content-bearing UI text (links, buttons, nav items, labels, table cells, meta rows, timecodes) below 11px is a legibility failure, not a style choice. WCAG sets no absolute pixel floor, but functional text under 11px is a defensible quality bar: it fails on high-DPI and small viewports and it degrades tap and read targets. The 11px floor holds even inside a footer; only non-interactive legal smallprint gets the softer 10px floor. Being ON the DESIGN.md size ramp does not exempt a value here: adding 8px to the ramp launders the token but not the legibility problem, and that is exactly the escape hatch this rule closes. Exempts sup/sub, visually-hidden (sr-only) text, and code/terminal contexts. Decorative letterspaced micro-labels are still functional and stay in scope.
Example: 10.5px functional text "Overall score" (below 11px floor)
Positioned child clipped by overflow container · quality1×
A clipping container (overflow hidden or clip) wrapping an absolutely-positioned child cuts off tooltips, menus, and popovers that need to escape. Let the overflow be visible, or move the positioned layer out of the clip.
Example: section.home-hero.svelte-1uha8ag clips a positioned child
Tiny body text · quality1×
Body text below 12px is hard to read, especially on high-DPI screens. Use at least 14px for body content, 16px is ideal.
Example: 11px body text
Skipped heading level · quality1×
Heading levels should not skip (e.g. h1 then h3 with no h2). Screen readers use heading hierarchy for navigation. Skipping levels breaks the document outline.
Example: <h1> "Client site audits, a clear fix order and before-and-after r" followed by <h3> "What to do now" (missing h2)
Full annotated page (178 labels)

This report is complete and free, and true as of the scan time above. The next deploy, a tag added in Tag Manager or a redesigned footer can change it. Watch re-checks cometweb.io every day and after every deploy, emails you the moment something regresses, keeps the dated record, and gives you a trust page your customers can check.
Watch cometweb.ioTrust page draftPassed audits
(12)
Privacy policy is present
A privacy policy link or page was found.
Privacy policy covers the expected disclosures
2547 words; 14 disclosure checks passed; last updated 2026-11-20.
No third-party trackers detected
None of the common analytics or marketing pixels were found in the page.
Terms of service are present
A terms page or link was found.
Public contact or business identity present
A contact email, contact page, or mailto link was found.
No secret keys in the page or its scripts
No server-side keys (Stripe secret, OpenAI, Anthropic, AWS, GitHub, Slack, SendGrid, Supabase service_role, private keys) in the page or the 2 script bundles it loads.
4 security headers set
Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options
No mixed content
All referenced resources use HTTPS.
Email signup shows consent or privacy language
1 email field with consent or privacy wording on the page.
security.txt published
Researchers know where to report a vulnerability.
Served over HTTPS
The final URL uses TLS.
34 accessibility rules passed
Rules axe-core tested and found no violations for.
Share this report.
The link is public and shows the same free view you see here; nothing about the reader is recorded.
The certificate.
cometweb.io holds Clean Bill of Health WO-2026-0329, last checked November 22, 2026. Open it for the seal and what it verified.
Put your score on your README.
An embeddable badge that re-checks weekly. Builders use it the way they use a CI badge: proof the boring stuff is handled.
[](https://webopsy.tech/s/cometweb.io)