Measure page loading speed and identify what prevents a page from loading in under three seconds. Use performance measurements to guide improvements such as lazy loading, caching, CDN delivery, and reducing resource costs.
Use when auditing slow page loads, heavy assets, or rendering delays related to Keep page load time under 3 seconds. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Measure page load time and investigate what keeps it from meeting a target of under three seconds. The skill examines heavy resources, unnecessary network traffic, CPU work, and layout calculations to identify specific files, requests, or rendering steps that cause delays. Based on those findings, it considers and implements improvements such as lazy loading, CDN delivery, caching, and resource optimization. It also describes the measurements used to confirm each problem.
Use it when a page feels slow but you do not know where to start making changes. It also helps with mobile performance checks and reviews of loading behavior involving images, scripts, and other resources. The review focuses on Core Web Vitals, which measure aspects of page performance, and includes checks with a connection throttled to 3G speeds.
The skill calls for confirming the cause with DevTools, Lighthouse, or data from actual usage before recommending changes. Under three seconds is a target for evaluation; the changes do not guarantee that result.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Studies show 53% of mobile users abandon sites that take longer than 3 seconds to load—slow pages directly hurt conversions, engagement, and SEO rankings.
Measure the page load time and verify it's under 3 seconds on a standard connection.
Optimize page load time through lazy loading, CDN usage, caching strategies, and resource optimization.
Explain how page load time affects bounce rate, SEO rankings, and user satisfaction.
Review the routes, assets, and loading behavior that affect Keep page load time under 3 seconds. 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/page-load-time
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.