Webopsy

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

98www.verifiedconnections.ai
100Privacy
98Security
100Legal
100Accessibility
35Design
What the scores mean
Scanned Nov 22, 2026, 11:58 AM

No change since the scan on Nov 15, 2026.

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

AI design tells

10 patterns on this page read as AI-generated: Nested cards, 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.

The area of www.verifiedconnections.ai with the most AI design tells, with each one labeled
The spot with the most tells: Hairline border with wide shadow, Nested cards. Labels are drawn by the detector on the live page.
Nested cards3×

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

Glowing shadow accents2×

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: Colored box-shadow glow (#9af79c) on dark background

Decorative radial spotlight glow2×

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 "pointer-events-none" (#42c642 a0.30 → transparent) on 479x172 surface

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

Kicker / eyebrow label above heading1×

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 "Tools" above h2 "Make the first conversation a little easier."

Raster buried under a wash or opacity · quality4×

A background image under a near-opaque gradient wash, or a raster on an element at near-zero opacity, never reaches the screen: the page shows the wash, and the produced texture or photo ships as a compliance token. Let the material show (a tint under 0.9 alpha, a blend mode, an opacity you can see) or remove the file.

Example: raster background at opacity 0.1

Tight line height · quality4×

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.25x (need >=1.3)

Line length too long · quality3×

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

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: 10px functional text "WHAT LOOKS" (below 11px floor)

Cramped padding · quality1×

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 ≥4.8px for 16px text)

Body text touching viewport edge · quality1×

Body paragraphs render flush against the left or right viewport edge with no container providing horizontal padding. Wrap content in a container with at least 16px (ideally 24-32px) of horizontal padding, or apply max-width with mx-auto.

Example: <p> with 138-char body bleeds to viewport edge (left 0px / right 0px)

Full annotated page (26 labels)
Full page of www.verifiedconnections.ai 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 verifiedconnections.ai 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 verifiedconnections.aiTrust page draft

Passed audits

(11)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

1918 words; 14 disclosure checks passed.

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.

Legal entity and address are shown

A company name and a postal address appear on the page.

Served over HTTPS

The final URL uses TLS.

No WCAG A/AA violations found (26 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 83 URLs from sitemap.xml.
Also read/contact /dashboard/tools /pricing, 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 partiesFonts: Google Fonts. These are the processors a privacy policy for this site should name.
Accessibilityaxe-core (WCAG 2.2 A/AA). 0 violation types, 26 rules passed, 1 need manual review.
Design auditImpeccable browser detector. 26 findings in 8.5 s at 1280px.
Duration10.5 s

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

verifiedconnections.ai holds Clean Bill of Health WO-2026-0991, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for verifiedconnections.ai

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/verifiedconnections.ai)](https://webopsy.tech/s/verifiedconnections.ai)

Webopsy badge for verifiedconnections.ai