Missing loading state
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A component performs data fetching with no visible loading-state variable, usually a bare/blank UI while data loads.
Why it matters
While a fetch is in flight the component renders with empty data, so users see a blank section, a zero, or a layout jump with nothing telling them a request is happening. On slow connections that reads as broken, and people leave or click again. A visible loading state costs a few lines.
How to fix it
Track the request state and render something during it: with plain fetch or axios, an isLoading useState flag set before the request and cleared in a finally block; with TanStack Query or SWR, use the isPending or isLoading flag the hook already returns. Show a spinner or skeleton while loading, and disable any button that triggers the request so users cannot double-fire it.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo