Webopsy

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

90kaloyan.blog
94Privacy
98Security
98Legal
100Accessibility
69Design
What the scores mean
Scanned Nov 22, 2026, 9:21 AM

No change since the scan on Nov 15, 2026.

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

Privacy policy is missing 3 expected disclosures~45 min

Not found in the policy text: states whether data is sold or shared for advertising; mentions international transfers; addresses children's data. Last updated 2 OCTOBER 2026.

CCPA/CPRA §1798.120, §1798.135 · GDPR Art. 13(1)(f) · COPPA; GDPR Art. 8

Open reference

Privacy Policy: missing sections privacy-policy-addendum.md
<!-- Sections your privacy policy at https://kaloyan.blog/privacy does not have.
     Paste each under a heading of its own, in the order shown, and update the
     date at the top of the policy. -->

## Sale of personal information

We do not sell personal information, and we do not share it for cross-context behavioural advertising.

## International transfers

Some of the providers we use (Segment) are in the United States. Where information about people in the EEA or UK is transferred there, we rely on the provider's Standard Contractual Clauses or its Data Privacy Framework certification.

## Children

The Service is not directed to children under 13 (or the minimum age in your
country), and we do not knowingly collect their data. If you believe a child has
provided us information, contact us and we will delete it.

---
_Generated from what the scanner observed on kaloyan.blog on November 22, 2026. Confirm each section matches what you actually do; not legal advice._
Add these 3 sections to your existing policy (https://kaloyan.blog/privacy), then re-scan; the audit checks for each one by name.
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, UK2 findings

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.

CCPA / CPRA (California) · United States, California1 finding

Maximum. About $2,500 per violation and about $7,500 per intentional violation or one involving a minor, inflation-adjusted each year; each affected consumer can count as a violation.

Usually. A notice from the California Privacy Protection Agency or Attorney General; the 30-day cure period was removed in 2023. Enforcement has focused on larger companies, but the thresholds catch many startups once they pass roughly $26 million in revenue or 100,000 consumers.

Applies: Businesses over the CCPA thresholds with California users. Many early-stage sites are below them; the privacy-policy duty under CalOPPA applies to all. Enforced by regulators.

CalOPPA (California Online Privacy Protection Act) · United States, California1 finding

Maximum. Up to $2,500 per violation, enforced through California's unfair-competition law after a 30-day notice.

Usually. A notice to post a compliant policy within 30 days. Applies to any commercial site reaching Californians, with no size threshold.

Applies: Any commercial site or app collecting personal information from California residents. Enforced by regulators.

PIPEDA / Quebec Law 25 · Canada1 finding

Maximum. Quebec Law 25: administrative penalties up to CA$10 million or 2% of worldwide turnover, and penal fines up to CA$25 million or 4%. PIPEDA itself currently relies on findings and court orders.

Usually. A complaint to the Privacy Commissioner or Quebec's CAI, an investigation, and a public finding; Quebec has begun issuing monetary penalties.

Applies: Any organisation collecting personal information from people in Canada; Law 25 for Quebec residents. Enforced by regulators.

AI design tells

2 patterns on this page read as AI-generated: Kicker / eyebrow label above heading, Cream / beige palette. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

The area of kaloyan.blog with the most AI design tells, with each one labeled
The spot with the most tells: Wide letter spacing on body text. Labels are drawn by the detector on the live page.
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 "THE EXPERIMENT LOG" above h2 "Experiments from the frontier."

Cream / beige palette1×

A warm cream or beige page background has become the default "tasteful" AI surface, reached for by reflex. Choose a background that comes from a deliberate palette, not the safe warm off-white.

Example: cream/beige page background rgb(243, 240, 231)

Wide letter spacing on body text · quality8×

Letter spacing above 0.05em on body text disrupts natural character groupings and slows reading. Reserve wide tracking for short uppercase labels only.

Example: letter-spacing: 0.15em on body text

Tight line height · quality3×

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

Tiny body text · quality2×

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

Example: 7.424px body 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 33 chars of body text

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

Layout property animation · quality1×

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

Full annotated page (18 labels)
Full page of kaloyan.blog 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 kaloyan.blog 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 kaloyan.blogTrust page draft

Passed audits

(9)
Privacy policy is present

A privacy policy link or page was found.

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 (23 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 15 URLs from sitemap.xml.
StackNext.js on nginx, from response headers and the page. The header fix is written for it.
Third partiesAnalytics: Segment. These are the processors a privacy policy for this site should name.
Accessibilityaxe-core (WCAG 2.2 A/AA). 0 violation types, 23 rules passed, 1 need manual review.
Design auditImpeccable browser detector. 18 findings in 9.1 s at 1280px.
Duration11.4 s

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

kaloyan.blog holds Clean Bill of Health WO-2026-0272, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for kaloyan.blog

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

Webopsy badge for kaloyan.blog