Before the Users Do

Before the Users Do

Ran this audit on the site you're reading right now.

Found 47 issues.

23 critical or high priority.

8-16 hours of fixes before we touched a single article.

That's production quality. Not "it works on my machine" quality. Not "close enough to ship" quality.


Your console is lying to you.

The warnings you've learned to ignore. The wallet connection that works on your machine. The mobile layout that's almost right. The missing alt text. The alert() you meant to replace. The useEffect firing twice. The hundred console.logs still in production code you forgot about.

You know it. You're shipping anyway.

Fine. But knowing your risks beats hoping for the best.


Five audits. One Claude Code session. Six reports.

UI/UX & Accessibility. WCAG violations, touch targets, keyboard nav, color contrast. Where "it looks fine on my laptop" goes to die.

HACK LOVE BETRAY
OUT NOW

HACK LOVE BETRAY

The ultimate cyberpunk heist adventure. Build your crew, plan the impossible, and survive in a world where trust is the rarest currency.

PLAY NOW

Feature Completeness. Every user flow mapped. Happy paths and sad paths. What happens when the API times out. Dead ends. Missing back buttons. Forms that submit to nowhere.

Performance & SEO. Core Web Vitals against Google's thresholds. Bundle size. Missing meta tags. The stuff costing you in search rankings before users even arrive.

Bug Hunt & Security. Race conditions. Memory leaks. XSS vectors. API keys in your frontend. The state that doesn't clear on disconnect.

Code Quality. console.log count (you have more than you think). Dead code. TypeScript any abuse. Does the build pass without --no-lint? It should.

Six reports. WCAG violations with file:line references. Not "you might have accessibility issues." Specific. Actionable. Surgical.


Here's the full prompt. Copy everything below. Open Claude Code in your project directory. Paste it. Type "proceed."

# WEBSITE PRODUCTION READINESS AUDIT REQUEST

I need a comprehensive pre-launch engineering audit for my website/web app,
similar to what professional web agencies deliver.

**Context:**
- Project: [YOUR PROJECT NAME]
- Type: [Landing Page/Web App/SaaS/Portfolio/E-commerce]
- Platform: [Next.js/React/Vue/etc]
- Status: [X months/years of development]
- Goal: Prepare for public launch or stakeholder demo

Run all 5 audits sequentially, creating detailed markdown reports for each:

## AUDIT 1: UI/UX & Web Design Excellence
Focus: Responsive design, cross-browser compatibility, accessibility, brand consistency

Analyze:
1. Responsive Design — mobile-first (320px to 4K), breakpoints, touch targets (44x44px),
   horizontal scroll prevention, safe area handling
2. Cross-Browser Compatibility — Chrome, Safari, Firefox, Edge, iOS Safari quirks,
   Android Chrome, fallbacks for unsupported features
3. Accessibility (WCAG 2.1 AA) — color contrast (4.5:1 text, 3:1 UI), keyboard navigation,
   screen reader compatibility, alt text, form labels
4. Visual Consistency — color palette, typography hierarchy, spacing system, component reuse
5. Information Architecture — max 3 clicks to any page, CTA prominence, mobile menu
6. Interaction Design — loading states, error states, empty states, success feedback,
   micro-interactions (hover, focus, active)
7. Performance Perception — optimistic UI, skeleton screens, image lazy loading, 60fps animations

Deliverable: WEB_UI_UX_AUDIT.md
Critical/High/Medium/Low severity. File:line references. Before/after recommendations.
WCAG violations with remediation steps.

## AUDIT 2: Feature Completeness & User Flows
Focus: All features work end-to-end, no dead ends, proper error handling

Analyze:
1. Core User Flows — map all primary journeys (landing → conversion), friction points,
   happy paths, sad paths, dead ends, missing back buttons
2. Forms & Validation — client-side (real-time), server-side (security), error message clarity,
   success states, autofocus and tab order
3. Web3/Wallet Integration (if applicable) — MetaMask/WalletConnect flow, network switching,
   transaction handling (pending/success/failure), disconnect and reconnect
4. Data Loading States — initial load, pagination, empty states, error states, retry mechanisms
5. Edge Cases — no wallet installed, wrong network, insufficient balance, network timeouts,
   stale data
6. Content Completeness — no placeholder text, no lorem ipsum, all images sourced

Deliverable: FEATURE_COMPLETENESS_REPORT.md
User flow maps. Missing features. Error handling gaps. Edge case scenarios.

## AUDIT 3: Web Performance & SEO
Focus: Core Web Vitals, bundle size, SEO optimization, loading speed

Analyze:
1. Core Web Vitals — LCP <2.5s, FID <100ms, CLS <0.1, TTFB <600ms, TTI <3.8s
2. Bundle Size — total <300KB gzipped, JS/CSS breakdown, unused code, third-party impact
3. Code Splitting & Lazy Loading — route-based splitting, dynamic imports, font loading
4. Asset Optimization — WebP/AVIF formats, compression quality, SVG optimization, font subsetting
5. Caching Strategy — HTTP cache headers, static asset versioning, API response caching
6. SEO Fundamentals — meta tags, OG tags, JSON-LD schema, sitemap.xml, robots.txt,
   canonical URLs, mobile-friendly
7. Network Performance — API batching/debouncing, CDN usage, DNS prefetch, resource hints

Deliverable: WEB_PERFORMANCE_SEO_REPORT.md
Current vs target metrics. Lighthouse scores. Bundle size breakdown.
Optimization priorities (quick wins vs long-term).

## AUDIT 4: Bug Hunt & Security Review
Focus: Edge cases, crashes, security vulnerabilities, data integrity

Analyze:
1. Error Handling — try-catch in async code, React error boundaries, global handlers,
   graceful degradation
2. Data Validation — XSS prevention, TypeScript strict mode, null/undefined/empty handling,
   NaN/Infinity/negative number validation
3. Security Vulnerabilities — XSS vectors, CSRF protection, API key exposure (.env in git),
   sensitive data in localStorage, third-party script security
4. Web3 Security (if applicable) — transaction approval validation, contract address verification,
   reentrancy protection, gas limit handling
5. State Management — race conditions, stale state, memory leaks (event listeners, intervals),
   infinite loops (useEffect deps), zombie children
6. Browser Compatibility Bugs — iOS Safari, Android Chrome, Firefox, Edge specifics
7. Critical Flow Testing — wallet connection, form submission, navigation, modal dismiss, mobile scroll

Deliverable: BUG_SECURITY_REPORT.md
Critical/High/Medium/Low severity. OWASP Top 10 checklist.
Reproduction steps. Fix recommendations with code examples.

## AUDIT 5: Production Code Quality
Focus: Technical debt, maintainability, deployment readiness

Analyze:
1. Code Cleanliness — console.log count (target: 0), debugger statements (target: 0),
   commented-out blocks, dead code, duplication
2. TypeScript Quality — strict mode, any type usage (minimize), @ts-ignore (target: 0),
   type coverage, proper interfaces
3. React Best Practices — key props, useCallback/useMemo, dependency arrays,
   component composition, custom hooks
4. Environment Configuration — .env.example exists, no secrets in codebase,
   dev/staging/prod configs
5. Build & Deployment — build succeeds without warnings, ESLint passes, no --no-lint flag,
   TypeScript clean, production build tested locally
6. Dependencies — npm audit (no critical vulns), npm outdated, unused packages,
   bundle size impact, license compliance
7. Git Hygiene — .gitignore correct, no .env committed, no node_modules committed

Deliverable: PRODUCTION_CODE_AUDIT.md
Code quality score (1-10). Technical debt inventory. Deployment readiness checklist.
Launch blocker issues.

## FINAL DELIVERABLE
Create WEBSITE_LAUNCH_READINESS_SUMMARY.md:
- Overall scores per audit area (1-10)
- Top 10 critical issues ranked by priority
- Estimated fix time: demo-ready vs public-launch-ready
- Clear go/no-go recommendation

Standards: Vercel/Netlify speed. Airbnb/Stripe polish. Linear/Notion UX.
Tone: Specific. "Line 45 in Header.tsx" not "some files."
Include file:line references for every issue.

Expect 5-10 critical issues. 10-15 high priority. 8-16 hours of actual work.

The first report is hard to read.

Good. Finding it now beats finding it through user complaints.

By the third audit on a different project you'll anticipate most of what it finds. You'll build cleaner from day one.

Or don't. Your call.