Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/browser-required
Use when auditing slow page loads, heavy assets, or rendering delays related to Perform browser-based performance audits. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Please audit our frontend route loading implementation and asset delivery setup. Identify any specific network, execution, or layout bottlenecks present in our code, and provide a clear breakdown of how these issues should be measured and verified.
| Checked | Without skill | With skill |
|---|---|---|
| Explains the limitations of static code analysis for web performance. | Missed | Passed |
| Recommends conducting performance audits in an environment that executes JavaScript. | Missed | Passed |
The instructions your model reads when the skill loads.
Static analysis alone cannot simulate the complex rendering, script execution, and layout processes of modern web browsers, which is essential for capturing real-world performance.
Ensure that performance audits are conducted in an environment that executes JavaScript and renders the page (e.g., Lighthouse, Puppeteer).
Integrate browser-based testing tools like Lighthouse or WebPageTest into the development workflow and CI/CD pipeline.
Explain the limitations of static analysis for performance and why a full browser environment is necessary.
Review the routes, assets, and loading behavior that affect Perform browser-based performance audits. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/performance/browser-required
test cases passed, vs 21 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.