Webopsy

This report was prepared for keyupradio.com. It shows the top findings; the full report includes every issue and its fix.

98keyupradio.com
100Privacy
100Security
98Legal
100Accessibility
47Design
What the scores mean
Scanned Nov 22, 2026, 7:39 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Oct 3, 2026, serial WO-2026-0437. View the certificate

Opportunities

No critical or high-severity issues. That's the bar most sites miss.

Nothing here.

Diagnostics

Worth fixing. Not an emergency.

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. 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.

AI design tells

7 patterns on this page read as AI-generated: Icon tile stacked above heading, Hairline border with wide shadow, Overused font. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of keyupradio.com with the most AI design tells, with each one labeled
The spot with the most tells: Icon tile stacked above heading. Labels are drawn by the detector on the live page.
Icon tile stacked above heading3×

A small rounded-square icon container above a heading is the universal AI feature-card template — every generator outputs this exact shape. Try a side-by-side icon and heading, or let the icon sit in flow without its own container.

Example: 52x52px icon tile above h3 "Nothing is recorded unless you say yes."

Hairline border with wide shadow2×

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 + 32px shadow blur

Overused font1×

Inter, Roboto, Fraunces, Geist, Plus Jakarta Sans, and Space Grotesk are used on so many sites they no longer feel distinctive. Each new wave of AI-generated UIs converges on the same handful of faces. Choose a face that gives your interface personality.

Example: Primary font: inter (82% of text)

Shape-assembled illustration1×

A large inline SVG that builds a pictorial scene from a pile of primitive shapes reads as placeholder clip art, not illustration. Icons, logos, and data graphics are fine at their scale; a hero-sized visual deserves real artwork, a photograph, or a deliberately drawn graphic.

Example: inline <svg> scene: 12 primitive shapes, ~320x200px, 14 fill colors

Line length too long · quality18×

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: ~88 chars/line (aim for <80)

Text occluded by an overlapping element · quality5×

Text is painted under an opaque element or a second text run, so part of it cannot be read. A decorative box, a stacked layer, or an inline element with leaked padding lands on the words instead of beside them. Give overlapping layers room, or move the text out from under the layer above it.

Example: button.btn.btn--ink.btn--sm "Send question to Microso" is 48% covered by an opaque element (button.motion-toggle.hero__motion)

Cramped padding · quality2×

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: 0px vertical padding (need ≥5.1px for 17px text)

Full annotated page (32 labels)
Full page of keyupradio.com with every design tell labeled

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 keyupradio.com 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 keyupradio.comTrust page draft

Passed audits

(11)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

13033 words; 14 disclosure checks passed; last updated October 20, 2026.

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 6 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.

security.txt published

Researchers know where to report a vulnerability.

Served over HTTPS

The final URL uses TLS.

No WCAG A/AA violations found (30 rules passed)

axe-core found no violations of the WCAG 2.2 A/AA rules it can test automatically. Automated checks cover roughly a third of WCAG; manual review is still needed for the rest.

MethodStatic fetch. JavaScript was not executed. What the browser renders after load is not visible to this scan.
SitemapRead 165 URLs from sitemap.xml.
Also read/pricing, for the third-party services on them.
StackAstro on Cloudflare, from response headers and the page. The header fix is written for it.
Third partiesAnalytics: Cloudflare Web Analytics. These are the processors a privacy policy for this site should name.
Accessibilityaxe-core (WCAG 2.2 A/AA). 0 violation types, 30 rules passed, 2 need manual review.
Design auditImpeccable browser detector. 32 findings in 12.2 s at 1280px.
Duration13.2 s

Or a free weekly re-scan of keyupradio.com. An email only when a new issue appears.

Only change alerts, unsubscribe in any email. Privacy.

Share this report.

The link is public and shows the same free view you see here; nothing about the reader is recorded.

Post on XShare on LinkedIn

The certificate.

keyupradio.com holds Clean Bill of Health WO-2026-0437, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for keyupradio.com

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.

Markdown
[![Webopsy](https://webopsy.tech/badge/keyupradio.com)](https://webopsy.tech/s/keyupradio.com)

Webopsy badge for keyupradio.com