pagespeed-enhancer
Scan, audit, and fix web performance issues across all four Lighthouse/PageSpeed Insights pillars — Performance, Accessibility, Best Practices, and SEO — in structured batches.
Profile →npx skills add sickn33/agentic-awesome-skills --skill pagespeed-enhancer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides a batch-wise workflow to scan, audit, and fix issues across Performance, Accessibility, Best Practices, and SEO, ensuring the user completes the scan and risk assessment before applying fixes.
How it works
- Phases define the process: PHASE 1 Ingest & Classify, PHASE 2 Batch Scan with four sections (Performance, Accessibility, Best Practices, SEO), PHASE 3 Risk Report, PHASE 4 Fix Batches.
- PHASE 1: When a PageSpeed Insights report is provided, the agent extracts the four pillar scores, flags metrics with values, identifies the critical path bottleneck, and outputs a Score Summary Table. Then it proceeds to Phase 2.
- PHASE 2: Batch A (Performance), Batch B (Accessibility), Batch C (Best Practices), Batch D (SEO). Each batch outputs per-audit findings with Finding, Root Cause, and Fix Category.
- PHASE 3: Produces a Risk Report as a consolidated Risk vs Impact Matrix with Fix, Impact Score, Risk Level, Effort, and Priority, and recommends fixing P1 items first.
- PHASE 4: Applies fixes in risk order. For each fix, the agent provides what to change (file, line, change), Before and After snippets, Expected metric improvement, and verification steps.
When to use it
- User pastes a PageSpeed Insights report or mentions Lighthouse scores
- User asks to improve Core Web Vitals (LCP, FCP, CLS, TBT, SI)
- User needs help with render-blocking resources, unused JavaScript, image optimisation, security headers, ARIA compliance, or SEO meta-tag fixes
- User asks questions related to PageSpeed, Lighthouse, Web Vitals, or site speed
- Any mention of PageSpeed, Lighthouse, Web Vitals, or site speed
What it can touch
- The workflow references batch scanning and fixes but does not specify executable touch points beyond the described phases and fix batches (e.g., moving CSS, preloading images, adding security headers, etc.).
Caveats
- Risk is declared as safe.
- The skill emphasizes a structured, batch-wise approach and requires completing scans and risk assessment before applying fixes.
- No outcomes are promised beyond the described steps and risk-based guidance.
- License and authorship are provided in the description; no additional licensing notes are stated here.
# PageSpeed Enhancer Skill A structured, batch-wise audit-and-fix workflow for all four Lighthouse pillars. Always follow the batch flow in order. Never jump straight to fixes without completing the scan and risk assessment phases. --- ## When to Use This Skill - User pastes a PageSpeed Insights report or mentions Lighthouse scores - User asks to improve Core Web Vitals (LCP, FCP, CLS, TBT, SI) - User needs help with render-blocking resources, unused JavaScript, image optimisation, security headers, ARIA compliance, or SEO meta-tag fixes - User asks "why is my LCP slow", "fix accessibility issues", "improve my SEO score", or "my site scores 80 on performance" - Any mention of PageSpeed, Lighthouse, Web Vitals, or site speed --- ## High-Level Workflow ``` PHASE 1 → Ingest Report & Parse Scores PHASE 2 → Batch Scan (4 sections, parallel analysis) PHASE 3 → Consolidated Risk Report (changes ranked by impact vs risk) PHASE 4 → Fix Batches (applied in safe order: low-risk → high-risk) PHASE 5 → Verification Checklist ``` --- ## PHASE 1 — Ingest & Classify When the user provides a PageSpeed Insights report (pasted text, screenshot, or URL): 1. Extract the four pillar scores: Performance,
- When to Use This Skill
- High-Level Workflow
- PHASE 1 — Ingest & Classify
- PHASE 2 — Batch Scan (4 Sections)
- Batch A — Performance Scan
- Batch B — Accessibility Scan
- Batch C — Best Practices Scan
- Batch D — SEO Scan
- PHASE 3 — Risk Report
- PHASE 4 — Fix Batches
- Fix Batch 1 — Quick Wins (Low Risk, deploy immediately)
- Fix Batch 2 — Medium Effort (staging test recommended)
- Fix Batch 3 — Refactor Required (full QA cycle)
- PRE-DEPLOY GATE
Using cwebp cwebp -q 80 input.jpeg -o output.webp Using sharp (Node.js) macOS fallback (sips built-in) sips -s format webp input.jpeg --out output.webp Python Pillow fallback python3 -c " from PIL import Image Open https://fonts.googleapis.com/css2?family=Inter:wght@400;700&display=swap in a browser, then download each woff2 URL listed in the @font-face blocks.
What does the pagespeed-enhancer skill do?
Scan, audit, and fix web performance issues across all four Lighthouse/PageSpeed Insights pillars — Performance, Accessibility, Best Practices, and SEO — in structured batches.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill pagespeed-enhancer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.