Webopsy

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

96redcenterstudio.com
100Privacy
98Security
98Legal
100Accessibility
49Design
What the scores mean
Scanned Nov 22, 2026, 6:19 AM

Score up 6 since Nov 14, 2026 (90 → 96). Fixed: Missing 4 security headers.

Clean bill of health since Nov 14, 2026, serial WO-2026-4823. 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

9 patterns on this page read as AI-generated: Kicker / eyebrow label above heading, Hero eyebrow / pill chip, 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 redcenterstudio.com with the most AI design tells, with each one labeled
The spot with the most tells: Line length too long. Labels are drawn by the detector on the live page.
Kicker / eyebrow label above heading6×

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 "New: self-serve App Mover" above h2 "Move your Bubble® app to Cloudflare yourself."

Hero eyebrow / pill chip1×

A tiny uppercase letter-spaced label sitting immediately above an oversized hero headline — or the same shape rendered as a pill chip — is now the default AI SaaS hero. Drop the eyebrow, integrate the kicker into the headline, or run it as a navigation breadcrumb instead.

Example: eyebrow chip (tracked-caps) "Independent studio, worldwide" above h1 "Software you own, not rent."

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 (64% of text)

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(245, 239, 230)

Text occluded by an overlapping element · quality6×

Text is painted under an opaque element or a second text run, so part of it cannot be read. A decorative box, a stacked layer, or an inline element with leaked padding lands on the words instead of beside them. Give overlapping layers room, or move the text out from under the layer above it.

Example: a "No-Code App Porting" is 50% covered by an opaque element (div.band)

All-caps body text · quality2×

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 40 chars of body text

Line length too long · quality2×

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

Heading crowded against the previous block · quality2×

A heading binds to the content it introduces, so the rendered space above it should exceed the space below it. When headings across a page sit as close or closer to the block above than to their own content, every section reads as if it captions the previous one. Open up the space above each heading.

Example: h2 "Free checks, no sign-up." has 8px above vs 40px below — it reads as bound to the block above (2 headings on page)

Content overflowing its container · quality1×

Content renders wider than its container, spilling out or forcing a horizontal scrollbar. Let text wrap, constrain widths, or give the region a deliberate scroll affordance.

Example: strong overflows its container by 36px

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

Passed audits

(10)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

3603 words; 14 disclosure checks passed; last updated 22 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 1 script bundle 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 124 URLs from sitemap.xml.
Also read/contact, for the third-party services on them.
StackCloudflare, from response headers and the page. The header fix is written for it.
Accessibilityaxe-core (WCAG 2.2 A/AA). 0 violation types, 23 rules passed, 0 need manual review.
Design auditImpeccable browser detector. 22 findings in 6.6 s at 1280px.
Duration7.0 s

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

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

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

Webopsy badge for redcenterstudio.com