A93%
Quality Score
2
Pages
21
Issues
8.0
Avg Confidence
7.8
Avg Priority
8 Critical10 High2 Medium1 Low
>_ Testers.AI
AI Analysis
v0 by Vercel was tested and 21 issues were detected across the site. The most critical finding was: Multiple 404 errors loading static resources (CSS/JS chunks). Issues span Performance, A11y, Other, UX categories. Persona feedback rated Visual highest (8/10) and Accessibility lowest (7/10).
Qualitative Quality
v0 by Vercel
Category Avg
Best in Category
Pages Tested · 2 screenshots
Homepage
v0.dev
Detected Issues · 21 total
1
Multiple 404 errors loading static resources (CSS/JS chunks)
CRIT P9
Prompt to Fix
Investigate all console errors: 'Failed to load resource: the server responded with a status of 404 ()'. Identify the exact resource URLs that are returning 404s (likely assets under /_next/static/chunks and /chat-static). Verify that those assets exist in the deployed build and that the server is serving them from the correct path. If assets are missing, re-run the build and deploy stage, or adjust assetHost/publicPath to the correct base URL. After applying fixes, reproduce to confirm 200 responses for those resources and no 404s on page load.
Why it's a bug
Missing resources (404) indicate assets failed to load, which can break critical UI styling, JavaScript functionality, or data-fetch code on initial render. This can lead to broken layout, missing interactivity, or incomplete functionality for users.
Why it might not be a bug
If assets are cached or served from a resilient CDN, user impact may be limited. However, repeated 404s suggest deployment or path configuration problems that could affect new sessions.
Suggested Fix
Audit deployment of static assets under /_next/static/chunks and /chat-static; verify asset paths, publicPath/config, and server routing. Ensure 404-reported assets exist in the deployed build or correct the asset URLs. If assets are optional, implement graceful fallbacks or conditional loading to avoid breaking UI.
Why Fix
Fixing missing assets restores initial UI correctness and interactive functionality, reduces user-visible errors, and prevents data/UI integrity issues during tasks.
Route To
Frontend Engineer
Page
Tester
Sharon · Security Tester
Technical Evidence
Console:
[ERROR] Failed to load resource: the server responded with a status of 404 ()
[ERROR] Failed to load resource: the server responded with a status of 404 ()
[ERROR] Failed to load resource: the server responded with a status of 404 ()Network:
Unknown resource URLs due to log formatting; indicates 404 on static assets (CSS/JS chunks under _next/static and chat-static).2
Excessive number of network requests (589+ requests observed)
CRIT P9
Prompt to Fix
Audit the build for code-splitting opportunities. Replace large bundles with dynamic imports, ship only what is needed for initial render, and lazy-load other modules. Reduce third-party script load and inline critical CSS.
Why it's a bug
Very high total number of requests increases latency, connection overhead, and can degrade Core Web Vitals, especially on mobile networks.
Why it might not be a bug
Some modern apps bundle many modules; however, this scale is typically excessive and should be optimized.
Suggested Fix
Implement code splitting and dynamic imports; lazy-load non-critical assets; consolidate CSS/JS where possible; remove unused dependencies; optimize image loading strategy.
Why Fix
Reduces payload and improves TTFB, LCP, and CLS; lowers energy usage and improves SEO signals.
Route To
Frontend Architect / Build System Engineer
Page
Tester
Tariq · Performance Specialist
Technical Evidence
Network:
Total network requests reported: 5933
UI stub button with empty label and id (placeholder artifact)
CRIT P9
Prompt to Fix
Review the Page Content JSON where there is a button object with text: "" and id: "". Remove or properly label this placeholder button. If it is intended to render conditionally, implement a clear feature-flag and ensure the button has a meaningful aria-label for accessibility.
Why it's a bug
The Page Content shows a button entry with text: "" and an empty id field, indicating an unfinished AI-generated UI stub that will render as an invisible or non-functional control. This can confuse users or break accessibility (screen readers) and indicates incomplete code generation.
Why it might not be a bug
If the empty button is intentionally hidden and only used as a placeholder until runtime, it could be acceptable; however, there is no conditional rendering visible to justify this placeholder in static screenshot.
Suggested Fix
Remove the empty button placeholder or fill with a valid label and non-empty id. If conditional, wrap rendering in a feature-flag and ensure accessibility (aria-label) and keyboard focus remain coherent.
Why Fix
Prevents broken UI, improves accessibility, and removes unclear placeholder artifacts from generated code.
Route To
Frontend/UI Engineer
Page
Tester
Jason · GenAI Code Analyzer