Webopsy

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

96usetyton.com
100Privacy
98Security
98Legal
100Accessibility
47Design
What the scores mean
Scanned Nov 22, 2026, 8:55 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Oct 2, 2026, serial WO-2026-0345. 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.

No security.txt for vulnerability reports~5 min

A /.well-known/security.txt file tells researchers how to report a problem before it becomes a breach. Two lines: Contact and Expires.

RFC 9116; expected by many bug-bounty and disclosure norms.

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, Overused font, Flat type hierarchy. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of usetyton.com with the most AI design tells, with each one labeled
The spot with the most tells: Low contrast text. Labels are drawn by the detector on the live page.
Icon tile stacked above heading4×

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: 40x40px icon tile above h3 "Guides"

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: geist (98% of text)

Flat type hierarchy1×

Dominant heading and body roles are separated by less than 1.25× at every step, leaving the size hierarchy flat. Add at least one stronger size step.

Example: Role sizes: body 14px, h1 16px, h3 17px (largest adjacent step 1.14:1; target 1.25:1)

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: .tyton-cursor — 3x13.6px dot with infinite "tyton-blink" animation

Line length too long · quality13×

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

Low contrast text · quality12×

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: 3.1:1 (need 4.5:1) — text #ffffff on #ff5e20

Layout property animation · quality3×

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: padding

Tight line height · quality1×

Line height below 1.3x the font size makes multi-line text hard to read. Use 1.5 to 1.7 for body text so lines have room to breathe.

Example: line-height 1.06x (need >=1.3)

Undersized functional text · quality1×

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: 8px functional text "Featured on" (below 11px floor)

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> "Set up Meta Pixel and the Conversions API with your AI agent" followed by <h3> "Free to start" (missing h2)

Full annotated page (38 labels)
Full page of usetyton.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 usetyton.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 usetyton.comTrust page draft

Passed audits

(10)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

2641 words; 14 disclosure checks passed; last updated 8 November 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.

Served over HTTPS

The final URL uses TLS.

No WCAG A/AA violations found (29 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 54 URLs from sitemap.xml.
Also read/pricing /signup /contact, for the third-party services on them.
StackNext.js on Cloudflare, from response headers and the page. The header fix is written for it.
Third partiesBackend: Supabase. These are the processors a privacy policy for this site should name.
Accessibilityaxe-core (WCAG 2.2 A/AA). 0 violation types, 29 rules passed, 1 need manual review.
Design auditImpeccable browser detector. 38 findings in 8.3 s at 1280px.
Duration10.1 s

Or a free weekly re-scan of usetyton.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.

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

Seal for usetyton.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/usetyton.com)](https://webopsy.tech/s/usetyton.com)

Webopsy badge for usetyton.com