本文へ移動
cccskills
無料GitHub で公開

seo-lighthouse-audit

Run a Lighthouse audit against any URL via the local Lighthouse CLI or the PageSpeed Insights API fallback, parse category scores and failed audits, and map every failed audit ID to its official Chrome docs page plus a one-line fix. Use when user says "lighthouse", "lighthouse audit", "run lighthouse", "lighthouse score", or "pagespeed".

インストール方法を見る

含まれるファイル(1)

  • SKILL.md9.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Lighthouse Audit & Fix Mapping

<!-- Updated: 2026-06-10 -->

Lighthouse is Google's open-source page quality tool. It runs a series of audits against a URL and scores four categories: Performance, Accessibility, Best Practices, and SEO. Reference: https://developer.chrome.com/docs/lighthouse/overview

Scope notes (keep the report honest):

  • PWA category was removed in Lighthouse v12 (2024). Do NOT score or report a PWA category. If the user asks for it, explain it no longer exists.
  • Lighthouse is lab data — a single synthetic run on emulated hardware/network. Always recommend validating against CrUX field data (75th percentile of real users) before treating a score as ground truth. Delegate field-data analysis to the seo-core-web-vitals skill.
  • Agentic Browsing is a new experimental category (llms.txt, WebMCP tools, accessibility-for-agents). It is informational only — it reports a pass ratio, not a 0-100 score. See https://developer.chrome.com/docs/lighthouse/agentic-browsing/scoring

Inputs

InputRequiredDefault
URL to auditYes—
Strategy (mobile/desktop)Nomobile
CategoriesNoperformance, seo, best-practices, accessibility

Execution

  1. Detect a local Lighthouse CLI:

    npx lighthouse --version 2>/dev/null || which lighthouse
    

    Requires Chrome installed locally. If either succeeds, prefer the CLI path (step 2); otherwise fall back to the PageSpeed Insights API (step 3).

  2. CLI path — run headless and write JSON to a temp file:

    npx lighthouse <url> --output=json \
      --output-path=/tmp/lh-report.json \
      --chrome-flags="--headless" --quiet
    

    For desktop strategy add --preset=desktop.

  3. API fallback — PageSpeed Insights v5 (no API key needed for light use; add &key= if one is configured):

    curl -s "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=<url>&category=performance&category=seo&category=best-practices&category=accessibility&strategy=mobile" -o /tmp/psi.json
    

    The Lighthouse result lives under .lighthouseResult. Docs: https://developers.google.com/speed/docs/insights/v5/get-started Bonus: the same response embeds CrUX field data under loadingExperience — surface it as a lab-vs-field sanity check.

  4. Parse the JSON:

    • Category scores: .categories[].score (multiply by 100).
    • Failed audits: every entry in .audits with score < 0.9 and a non-informative scoreDisplayMode (binary or numeric). Capture id, title, displayValue, and details.overallSavingsMs / overallSavingsBytes where present.
    • Key lab metrics: largest-contentful-paint, total-blocking-time, cumulative-layout-shift, first-contentful-paint, speed-index. Performance scoring weights: https://developer.chrome.com/docs/lighthouse/performance/performance-scoring
  5. Map each failed audit to its docs page and a fix. Docs URL pattern:

    https://developer.chrome.com/docs/lighthouse/<category>/<audit-id>
    

    where <category> is performance, seo, best-practices, or accessibility. Use the reference table below for the highest-impact audits; for others, construct the URL from the pattern and write a one-line fix from the audit's own description field.

  6. Prioritize: sort performance audits by estimated savings (ms/bytes), then list SEO and best-practices failures (these are usually binary pass/fail and cheap to fix).

High-Impact Audit Reference

Performance

Audit IDOne-line fixDocs
render-blocking-resourcesInline critical CSS, defer non-critical CSS/JSdocs
unused-javascriptCode-split and lazy-load unused bundlesdocs
uses-responsive-imagesServe appropriately sized images via srcset/sizesdocs
total-byte-weightReduce total payload below ~1.6 MB (compress, trim, lazy-load)docs
bf-cacheRemove unload handlers and no-store headers blocking back/forward cachedocs
largest-contentful-paintPreload the LCP resource, add fetchpriority="high"docs
total-blocking-timeBreak up long main-thread tasks, defer third-party JSdocs
dom-sizeKeep DOM under ~1,500 nodes; virtualize long listsdocs
third-party-summaryLazy-load or facade heavy third-party embedsdocs
font-displayUse font-display: swap to avoid invisible textdocs

Other frequent flags: unused-css-rules, unminified-javascript, unminified-css, uses-text-compression, uses-long-cache-ttl, uses-optimized-images, offscreen-images, server-response-time, redirects, uses-rel-preconnect, mainthread-work-breakdown, bootup-time, non-composited-animations — same URL pattern.

SEO

Audit IDOne-line fixDocs
is-crawlableRemove blocking noindex / robots.txt rules on indexable pagesdocs
meta-descriptionAdd a unique, descriptive meta descriptiondocs
canonicalAdd a single valid, absolute canonical URLdocs
hreflangFix hreflang codes and ensure reciprocal linksdocs
http-status-codeReturn 200 for indexable pages, not 4xx/5xxdocs
link-textReplace "click here" with descriptive anchor textdocs

Also check: font-size (legible ≥12px text), tap-targets (48x48px touch targets), invalid-robots-txt, structured-data (manual).

Best Practices

Audit IDOne-line fixDocs
viewportAdd <meta name="viewport" content="width=device-width, initial-scale=1">docs
csp-xssAdd a strict Content-Security-Policy against XSSdocs
has-hstsSend a Strict-Transport-Security headerdocs

Also frequent: is-on-https, errors-in-console, no-vulnerable-libraries, image-aspect-ratio, uses-http2, deprecations, charset, doctype, external-anchors-use-rel-noopener, clickjacking-mitigation — same URL pattern.

Agentic Browsing (informational — do not score)

Experimental audits for AI-agent readiness: llms-txt (machine-readable site summary at /llms.txt — N/A if 404, flagged only on server error; see docs), WebMCP tool registration and schema validity, accessibility-for-agents, layout stability for agents. Report pass ratio only and cross-reference the seo-llms-txt and seo-robots-ai skills.

Output

# Lighthouse Audit: <url> (mobile|desktop, lab data)

## Category Scores
| Category | Score |
|----------|-------|
| Performance | XX/100 |
| Accessibility | XX/100 |
| Best Practices | XX/100 |
| SEO | XX/100 |

## Key Lab Metrics
| Metric | Value | Rating |
|--------|-------|--------|
| LCP | X.Xs | ✅/⚠️/❌ |
| TBT | XXXms | ✅/⚠️/❌ |
| CLS | 0.XX | ✅/⚠️/❌ |
| FCP / Speed Index | ... | ... |

## Failed Audits → Fixes (sorted by estimated savings)
| # | Audit | Category | Est. Savings | Fix | Docs |
|---|-------|----------|--------------|-----|------|
| 1 | render-blocking-resources | Performance | 1,200 ms | Inline critical CSS, defer the rest | link |
| ... | | | | | |

## Field vs Lab (if PSI response included loadingExperience)
Note agreement/divergence between lab metrics and CrUX field data.

## Caveats
- Lab data from a single emulated run — validate with CrUX field data
  (see seo-core-web-vitals skill) before declaring CWV pass/fail.
- PWA category removed in Lighthouse v12; Agentic Browsing is experimental
  and informational only.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

seo

無料

Comprehensive SEO analysis for any website or business type. Orchestrates 52 sub-skills (52 active): full site audits, technical SEO (CWV/INP), schema, E-E-A-T content quality, images, sitemaps, GEO for AI Overviews, llms.txt generation, AI crawler audit, plus live GSC and Ahrefs MCP data. GSC: overview, drops, opportunities, brand-vs-nonbrand, cannibalization, compare, content-decay, index-issues, new-keywords. Ahrefs: overview, backlinks, keywords, competitors, content-gap, broken-links, new-links, anchor-analysis, dr-history, top-pages. Cross-MCP: serp, content-brief, brand-radar, site-audit-pro, report. Local: log-analysis, ai-content-check, internal-links, local, migration-check, obsidian-kb. AI Readability: llms-txt, robots-ai. Performance: lighthouse-audit, core-web-vitals, page-experience. Quality & AI Search: rich-results, ai-optimization, eeat-audit, helpful-content. Triggers on: "SEO", "audit", "schema", "Core Web Vitals", "sitemap", "E-E-A-T", "AI Overviews", "GEO", "technical SEO", "content quality", "structured data", "GSC", "Ahrefs", "backlinks", "keywords", "search console", "domain rating", "local SEO", "migration", "lighthouse", "pagespeed", "LCP", "INP", "CLS", "page experience", "interstitials", "mobile friendly", "rich results", "rich snippets", "schema eligibility", "AI optimization", "AI search readiness", "EEAT", "trust signals", "helpful content", "people-first", "content quality gate".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Analyze a domain's anchor text distribution from Ahrefs: see the breakdown of anchor text used across all backlinks and assess link profile health. Use when user says "anchor text", "anchor analysis", "anchor distribution", "link anchors", or "anchor text profile".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Analyze a domain's backlink profile using Ahrefs: see who links to the domain, source Domain Rating, anchor text, link type, and when each link was first seen. Use when user says "Ahrefs backlinks", "backlink profile", "who links to", "link analysis", or "referring pages".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Find broken backlinks pointing to a domain using Ahrefs: links targeting 404 pages that can be reclaimed. Prioritizes highest-DR lost links for maximum recovery impact. Use when user says "broken backlinks", "broken links", "link reclamation", "dead backlinks", or "404 backlinks".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Discover a domain's top organic competitors from Ahrefs: competing domains, keyword overlap count, shared keywords, and unique competitor keywords. Use when user says "Ahrefs competitors", "organic competitors", "competing domains", "keyword overlap", or "who competes with".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

Find keywords that competitors rank for but the target domain does not, using Ahrefs data. Reveals content opportunities and topic gaps. Use when user says "content gap", "keywords competitors rank for", "missing keywords", "competitor keywords", or "content gap analysis".

日本語の概要は準備中です。原文の説明を表示しています。

lionkiii/claude-seo-skills212026年6月11日 更新

lionkiii のスキルをすべて見る

このスキルの問題を報告する