This report was prepared for cookieyes.com. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
No change since the scan on Nov 14, 2026.
Clean bill of health since Oct 2, 2026, serial WO-2026-0073. View the certificate
Opportunities
No critical or high-severity issues. That's the bar most sites miss.
Diagnostics
Worth fixing. Not an emergency.
AI design tells
3 patterns on this page read as AI-generated: AI color palette, Auto-scrolling marquee. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

AI color palette2×
Purple/violet gradients and cyan-on-dark are the most recognizable tells of AI-generated UIs. Choose a distinctive, intentional palette.
Example: Cyan gradient background
Auto-scrolling marquee1×
Continuously auto-scrolling content demands attention it has not earned and hides half its content at any moment. Reserve motion for content that changes; let readers move at their own pace.
Example: .marquee-track — infinite horizontal loop animation "marquee-scroll"
Line length too long · quality9×
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: ~114 chars/line (aim for <80)
Body text touching viewport edge · quality7×
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 166-char body bleeds to viewport edge (left -398px)
Gray text on colored background · quality4×
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 #e2eaf5 on bg #203858
Low contrast text · quality1×
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.2:1 (need 4.5:1) — text #ffffff on #dd425a
Full annotated page (24 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 cookieyes.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 cookieyes.comTrust page draftPassed audits
(15)
Privacy policy is present
A privacy policy link or page was found.
Privacy policy covers the expected disclosures
7123 words; 14 disclosure checks passed.
A consent manager is installed alongside the trackers
Trackers detected (Google Tag Manager) and consent is handled by a consent-management platform. Confirm non-Google trackers also wait for consent.
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
Cookie policy or settings are linked
A cookie policy, notice, or preferences link was found.
"Do Not Sell or Share" link present
A CCPA/CPRA opt-out link was found.
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.
security.txt published
Researchers know where to report a vulnerability.
Served over HTTPS
The final URL uses TLS.
No WCAG A/AA violations found (32 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.
Share this report.
The link is public and shows the same free view you see here; nothing about the reader is recorded.
The certificate.
cookieyes.com holds Clean Bill of Health WO-2026-0073, 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/cookieyes.com)