e952909eperformance
INP ≤ 200ms
Core Web Vitals + bundle budgets. LCP, INP, CLS, bundle size, hot-cache reload time. Measured with the testing agent's headless Chrome.
Cross-agent verdicts
Loading verdicts…
Plan source
What TestSprite reads
The testing agent reads this JSON, opens the deployed URL in headless Chromium, executes each action step, evaluates each assertion. Verdict: passed / failed / blocked / inconclusive.
{
"projectId": "1ad26753-ee03-4689-8f0f-6fa5d67c5c72",
"type": "frontend",
"name": "Performance — Interaction to Next Paint (INP) ≤ 200ms on bracket interaction",
"description": "Clicking a fixture card to navigate to /match/[id] should respond within 200ms (good per Core Web Vitals). Catches deployables with blocking JS that delay click handlers.",
"priority": "p2",
"metadata": {
"category": "performance",
"stage": "all"
},
"planSteps": [
{
"type": "action",
"description": "Navigate to the homepage and wait for the bracket to fully render"
},
{
"type": "action",
"description": "Click on the first R16 fixture card"
},
{
"type": "assertion",
"description": "Verify the click-to-next-paint elapsed time is ≤ 200ms"
}
]
}View on GitHub →