Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
agricidaniel avatar

Seo Performance

  • 35 installs
  • 548 repo stars
  • Updated July 20, 2026
  • agricidaniel/codex-seo

seo-performance is a Claude Code skill that measures Core Web Vitals and Lighthouse signals for the performance sub-track of an SEO audit and emits deterministic report artifacts.

About

seo-performance is a Claude Code skill that measures Core Web Vitals (LCP, INP, CLS) and Lighthouse performance signals as the performance sub-track of a full SEO audit. A developer uses it to get deterministic performance report artifacts, preferring real-user field data and labeling lab-data fallbacks. It applies priority rules so poor scores surface as high-priority issues.

  • Measures Core Web Vitals (LCP/INP/CLS) and Lighthouse signals for SEO audits
  • Prefers real-user CrUX/PageSpeed data and clearly labels Lighthouse lab fallbacks
  • Emits deterministic PERFORMANCE-AUDIT-REPORT.md and SUMMARY.json artifacts

Seo Performance by the numbers

  • 35 all-time installs (skills.sh)
  • Ranked #1,384 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

seo-performance capabilities & compatibility

Free; an optional PAGESPEED_API_KEY improves data quality but is not required

Capabilities
core web vitals · lighthouse audit · performance audit · cwv measurement
Use cases
seo
Pricing
Free
From the docs

What seo-performance says it does

Performance specialist for full audits. Measures CWV (LCP/INP/CLS), Lighthouse score signals, and emits deterministic report artifacts.
SKILL.md
INP only when the data source actually provides it; do not fabricate or infer INP from TBT
SKILL.md
npx skills add https://github.com/agricidaniel/codex-seo --skill seo-performance

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs35
repo stars548
Last updatedJuly 20, 2026
Repositoryagricidaniel/codex-seo

What it does

Measure Core Web Vitals and Lighthouse signals for a URL and emit a deterministic SEO performance report.

Who is it for?

Measuring Core Web Vitals and Lighthouse signals as the performance leg of an SEO audit

Skip if: On-page content or schema analysis; those are handled by seo-page and seo-content

When should I use this skill?

running the performance sub-track of a full SEO audit or measuring LCP/INP/CLS

What you get

Deterministic performance artifacts with CWV metrics, priority-rated issues, and clearly labeled lab vs field data.

  • PERFORMANCE-AUDIT-REPORT.md
  • SUMMARY.json
  • performance.json cache entry

By the numbers

  • High priority thresholds: LCP > 2500ms, INP > 200ms, CLS > 0.1
  • Performance score < 70 flagged High

Files

SKILL.mdMarkdownGitHub ↗

Performance Specialist

Use this for the performance sub-track in full audits.

Shared Data Cache

Step 0 -- Check shared data cache:

Before gathering, check .seo-cache/ for cached data from other skills. Reference: ../seo/references/shared-data-cache.md for schemas and dependency map.

This specialist does not require upstream cache inputs before running fresh performance checks.

  • If found: no prerequisite cache is needed; continue with current measurements
  • If missing: proceed normally and gather fresh performance data
  • If the user says "refresh" or "re-run": ignore cache entirely

Inputs

  • URL
  • Timeout
  • Optional PageSpeed API key (PAGESPEED_API_KEY)

Execution Path

Prefer running scripts/analyze_performance.py for deterministic performance analysis in API/headless environments. The script uses PageSpeed data when available and otherwise falls back to labeled heuristics so the pipeline still completes without a human in the loop.

Outputs

  • PERFORMANCE-AUDIT-REPORT.md
  • SUMMARY.json

Core checks

  • Prefer real-user CWV data from PageSpeed Insights / CrUX when available
  • If real-user data is unavailable, fall back to Lighthouse lab data and label it clearly as lab data
  • Lighthouse performance score (mobile + desktop if available)
  • LCP and CLS measurements
  • INP only when the data source actually provides it; do not fabricate or infer INP from TBT
  • TBT may be reported as a lab proxy when INP is unavailable
  • Fallback guidance when API data is unavailable, quota-blocked, or unauthenticated

Priority Rules

  • High: Performance score < 70 or LCP > 2500ms or INP > 200ms or CLS > 0.1
  • Medium: Performance score 70-79
  • Low: Data-source limitations

Write to shared data cache

After completing all work, write results to .seo-cache/.

mkdir -p .seo-cache/pages/{url-slug}

Write .seo-cache/pages/{url-slug}/performance.json using the schema in ../seo/references/shared-data-cache.md. At minimum, match the documented cache keys: core_web_vitals and issues. Add extra helpful fields only if they do not replace or rename the documented keys.

Add .seo-cache/ to .gitignore if not already present:

grep -qxF '.seo-cache/' .gitignore 2>/dev/null || echo '.seo-cache/' >> .gitignore

Premium Deliverable

If the user requests a 'client report' or 'premium deliverable', automatically read ../seo-audit/assets/report-template.html and ../seo/references/premium-report-standard.md. Use that report standard as the default brief. Generate the HTML as an internal intermediate artifact, then produce the PDF as the public deliverable. Mention only the PDF in your final response unless the user explicitly asks for the HTML file.

Related skills

FAQ

Does seo-performance require an API key?

No. It can use a PageSpeed API key when available but otherwise falls back to labeled Lighthouse lab heuristics so the pipeline completes without a human in the loop.

How does it handle INP?

It reports INP only when the data source provides it and does not fabricate or infer INP from TBT; TBT may be shown as a lab proxy instead.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.