Webopsy

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

92rankzapseo.com
100Privacy
92Security
100Legal
50Accessibility
39Design
What the scores mean
Scanned Nov 22, 2026, 10:39 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Oct 8, 2026, serial WO-2026-1200. 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 only use permitted ARIA attributes (2 elements)~20 min

Ensure ARIA attributes are not prohibited for an element's role Example: <span aria-label="Connected" class="tick"><svg aria-hidden="true" viewBox="0 0 16 16"><path d="M3.4 8.4 6.3 11.3 12.6 4.9" fill="none" stroke="#FFFFFF" stroke-l

WCAG wcag2a, wcag412. 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).

How to fix this rule

Elements must meet minimum color contrast ratio thresholds (37 elements)~3 h

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds Example: <span class="w1">Plug</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).

How to fix this rule

Diagnostics

Worth fixing. Not an emergency.

Missing 4 security headers~15 min

Not set: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options. These defend against clickjacking, MIME sniffing, and protocol downgrade.

Security Headers nginx.conf
# Missing on your site: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options. The Content-Security-Policy below already allows Google Fonts; add the domain of anything else you load to script-src or connect-src, then re-scan.
add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" always;
add_header X-Content-Type-Options "nosniff" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;
add_header Content-Security-Policy "default-src 'self'; script-src 'self'; connect-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; frame-src 'none'; frame-ancestors 'self'; base-uri 'self'; form-action 'self'" always;
Inside the server {} block; nginx -s reload. Then re-scan. The Content-Security-Policy is written for what the scan saw (Google Fonts); if a script or request is blocked after deploy, the browser console names the origin to add.
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 security items sit under GDPR Art. 32 (up to 2% of turnover) and the FTC's security enforcement, where the real cost arrives with a breach and its mandatory notifications; 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, security of processing · EU, EEA, UK1 finding

Maximum. Up to €10 million or 2% of worldwide annual turnover (Art. 83(4)); UK: up to £8.7 million or 2%.

Usually. Fines follow a breach, not a scan. If exposed data reaches users, breach notification to the regulator within 72 hours is mandatory and the fine considers whether the weakness was known.

Applies: Any site processing personal data of people in the EU or UK. Enforced by regulators.

ADA Title III and California's Unruh Act (web accessibility) · United States3 findings

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, Ontario3 findings

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.

FTC Act §5 (unfair or deceptive practices) and state breach laws · United States1 finding

Maximum. No fixed fine for a first violation; the FTC obtains consent orders with 20-year audit obligations, and violating an order costs over $53,000 per day. State breach-notification laws add per-resident notification costs and, in some states, per-record penalties.

Usually. Enforcement follows an incident. An exposed live key or open database is the incident waiting to happen; the practical cost is fraud on the account plus mandatory notification.

Applies: Any US company holding consumer data. Enforced by regulators.

AI design tells

11 patterns on this page read as AI-generated: Kicker / eyebrow label 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 rankzapseo.com with the most AI design tells, with each one labeled
The spot with the most tells: Nested cards. Labels are drawn by the detector on the live page.
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 "Plug and play" above h2 "Bring your own LLM"

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 + 50px 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: plus jakarta sans (89% of text)

Glowing shadow accents1×

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 (#6438f5) on dark page

Nested cards1×

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

Low contrast text · quality27×

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 #d97757

Undersized functional text · quality10×

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 "Ready soon" (below 11px floor)

Tiny body text · quality5×

Body text below 12px is hard to read, especially on high-DPI screens. Use at least 14px for body content, 16px is ideal.

Example: 11.5px body text

Raster buried under a wash or opacity · quality5×

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: <img> at opacity 0 "Search Performance: clicks, impressions and keyword movement"

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 ≥4.0px for 13px text)

All-caps body text · quality1×

Long passages in uppercase are hard to read. We recognize words by shape (ascenders and descenders), which all-caps removes. Reserve uppercase for short labels and headings.

Example: text-transform: uppercase on 37 chars of body text

Gray text on colored background · quality1×

Gray text looks washed out on colored backgrounds. Use a darker shade of the background color instead, or white/near-white for contrast.

Example: text #5c5b64 on bg #ded6ff

Line length too long · quality1×

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

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

Passed audits

(11)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

3788 words; 14 disclosure checks passed; last updated 29 September 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 2 script bundles it loads.

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.

Email signup shows consent or privacy language

1 email field with consent or privacy wording on the page.

Served over HTTPS

The final URL uses TLS.

33 accessibility rules passed

Rules axe-core tested and found no violations for.

MethodStatic fetch. JavaScript was not executed. What the browser renders after load is not visible to this scan.
SitemapRead 183 URLs from sitemap.xml.
Also read/pricing /contact /login, for the third-party services on them.
Stacknginx, 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). 3 violation types, 33 rules passed, 3 need manual review.
Design auditImpeccable browser detector. 63 findings in 7.8 s at 1280px.
Duration9.2 s

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

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

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

Webopsy badge for rankzapseo.com