Webopsy

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

92grep.ai
100Privacy
92Security
100Legal
100Accessibility
27Design
What the scores mean
Scanned Nov 22, 2026, 6:17 AM

Score down 6 since Nov 14, 2026 (98 → 92). New: Missing 1 security header.

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

Missing 1 security header~15 min

Not set: Strict-Transport-Security. These defend against clickjacking, MIME sniffing, and protocol downgrade.

Security Headers next.config.js
// next.config.js — Missing on your site: Strict-Transport-Security. The Content-Security-Policy below already allows Calendly; add the domain of anything else you load to script-src or connect-src, then re-scan.
/** @type {import('next').NextConfig} */
const securityHeaders = [
  { key: 'Strict-Transport-Security', value: "max-age=63072000; includeSubDomains; preload" },
  { key: 'X-Content-Type-Options', value: "nosniff" },
  { key: 'X-Frame-Options', value: "SAMEORIGIN" },
  { key: 'Referrer-Policy', value: "strict-origin-when-cross-origin" },
  { key: 'Permissions-Policy', value: "camera=(), microphone=(), geolocation=()" },
  { key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' https://assets.calendly.com 'unsafe-inline'; connect-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; font-src 'self' data:; frame-src https://calendly.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self'" },
];

module.exports = {
  async headers() {
    return [{ source: '/:path*', headers: securityHeaders }];
  },
};
Next.js config (works on Vercel, Netlify, or a Node server). Then re-scan. The Content-Security-Policy is written for what the scan saw (Calendly); 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. 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.

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

17 patterns on this page read as AI-generated: Hairline border with wide shadow, Kicker / eyebrow label above heading, Glowing shadow accents. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.

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

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

Kicker / eyebrow label above heading3×

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 "Agent SwarmsNew feature" above h2 "Put a swarm of agents to work on your backlog."

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: Zero-offset box-shadow glow (#5d5fef)

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: .gfb-source-track — infinite horizontal loop animation "gfb-source-drift"

Repeating-gradient stripes1×

Repeating-gradient stripes used as surface decoration are a recurring generated-UI signature. Reach for a deliberate texture or leave the surface plain.

Example: repeating-gradient decorative stripes

Decorative grid-line background1×

A decorative grid or line-field background drawn with hairline linear-gradient layers tiled by a fixed pixel cell is a recurring generated-UI signature. Reserve grid overlays for actual canvas, map, blueprint, or measurement surfaces; elsewhere use product structure or a plain surface.

Example: two-axis grid-line gradient background

Undersized functional text · quality28×

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

Tiny body text · quality11×

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

Example: 11px body text

Gray text on colored background · quality6×

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 #ebebeb on bg #5147ef

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

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

Wide letter spacing on body text · quality2×

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.06em on body text

Positioned child clipped by overflow container · quality1×

A clipping container (overflow hidden or clip) wrapping an absolutely-positioned child cuts off tooltips, menus, and popovers that need to escape. Let the overflow be visible, or move the positioned layer out of the clip.

Example: div.grep-public-site.grep-homepage clips a positioned child

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: 2.9:1 (need 4.5:1) — text #ffffff on #ff6600

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

Full annotated page (71 labels)
Full page of grep.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 grep.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 grep.aiTrust page draft

Passed audits

(11)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

3313 words; 14 disclosure checks passed; last updated September 21, 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 6 script bundles it loads.

3 security headers set

Content-Security-Policy, 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 (34 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 200 URLs from sitemap.xml.
Also read/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 partiesForms: Calendly. These are the processors a privacy policy for this site should name.
Accessibilityaxe-core (WCAG 2.2 A/AA). 0 violation types, 34 rules passed, 1 need manual review.
Design auditImpeccable browser detector. 71 findings in 61.0 s at 1280px.
Duration61.5 s

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

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

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

Webopsy badge for grep.ai