Skill Detail
PageSpeed CLI Skill
PageSpeed-CLI · github
AI-ready PageSpeed Insights and Lighthouse CLI for Core Web Vitals audits, performance fixes, SEO optimization, and before/after verification.
Skill Overview
AI-ready PageSpeed Insights and Lighthouse CLI for Core Web Vitals audits, performance fixes, SEO optimization, and before/after verification.
PageSpeed CLI Search Terms
This page targets users searching for PageSpeed CLI Skill, download, installation, README, Skill URL, and usage guide.
Resource Type
BHINNKJ Tool
Categories
Development, Data & Analysis, Testing, Marketing & Growth
Tags
PageSpeed, Lighthouse, Core Web Vitals, SEO
The download is a local Markdown skill file saved by EasyGlobe and deployable with the site to GitHub and Cloudflare.
Detailed Skill Introduction
What PageSpeed CLI is for
PageSpeed CLI is an AI agent skill resource for Development, Data & Analysis, Testing, Marketing & Growth workflows. Based on the archived project material, its core value is: AI-ready PageSpeed Insights and Lighthouse CLI for Core Web Vitals audits, performance fixes, SEO optimization, and before/after verification.. People landing on this page are likely searching for PageSpeed CLI, PageSpeed CLI download, PageSpeed CLI installation, PageSpeed CLI README, PageSpeed CLI Skill URL, or platform-specific terms such as Claude Skills, Codex Skills, Gemini Skills, Kimi Skills, and GLM Skills. This detail page brings those signals together so a user can understand what the skill does before opening the original project.
README summary
中文 README
PageSpeed-CLI is an AI-ready command-line plugin for Google PageSpeed Insights. It helps developers and AI coding agents quickly collect PageSpeed/Lighthouse evidence for a single website or a batch of websites, then turns the raw report into actionable optimization briefs.
Instead of asking an AI agent to inspect a slow website blindly, PageSpeed-CLI gives it structured performance context: Core Web Vitals lab metrics, Lighthouse scores, high-impact opportunities, affected resources, third-party scripts, implementation hints, and verification commands. The goal is to make website speed optimization repeatable from the CLI, easy to automate in CI, and easy to feed into AI coding workflows.
README capability notes
- Runs Google PageSpeed Insights for normal URLs through GET https://www.googleapis.com/pagespeedonline/v5/runPagespeed.
- Extracts cached Lighthouse JSON from pagespeed.web.dev/analysis/... share links without consuming PageSpeed API quota.
- Supports single target analysis through /PageSpeed.
- Supports batch analysis from command arguments or a text file.
- Saves raw-report.json, summary.json, and ai-brief.md for each target.
- Produces an AI-ready Markdown brief with concrete evidence and implementation guidance.
README usage notes
1. Run /PageSpeed or batch.
2. Give the saved ai-brief.md to an AI coding agent.
3. Ask the agent to map each finding to source files, infrastructure, or third-party tags.
4. Implement changes.
5. Rerun the same command and compare performance, LCP, TBT, CLS, and opportunity savings.
README setup and configuration notes
An API key is optional for single fresh URL audits. Without a key, PageSpeed-CLI still calls Google PageSpeed directly and prints a warning because anonymous quota may fail.
For batch or parallel runs, configure an API key:
export PAGESPEED_API_KEY="..."
pagespeed-cli batch --input urls.txt --jobs 4You can also pass a key per command:
pagespeed-cli --api-key "$PAGESPEED_API_KEY" /PageSpeed https://example.comShare-link extraction does not rerun PageSpeed and does not consume PageSpeed API quota.
Workflow fit and practical value
The current taxonomy places PageSpeed CLI under Development, Data & Analysis, Testing, Marketing & Growth, with tags such as PageSpeed, Lighthouse, Core Web Vitals, SEO. That means the skill should be evaluated through the lens of repeatable work: what task it helps an AI agent perform, what context the agent needs, what output a user should expect, and whether the workflow can be reused as a team SOP. The archived README is used as the first source of truth whenever it includes feature lists, examples, setup notes, or usage guidance....
Installation
git clone https://github.com/BHINNKJ/PageSpeed-CLI.git
cd PageSpeed-CLI
python3 -m pip install -e ".[dev]"Usage
1. Run /PageSpeed or batch.
2. Give the saved ai-brief.md to an AI coding agent.
3. Ask the agent to map each finding to source files, infrastructure, or third-party tags.
4. Implement changes.
5. Rerun the same command and compare performance, LCP, TBT, CLS, and opportunity savings.
Capabilities
- Runs Google PageSpeed Insights for normal URLs through GET https://www.googleapis.com/pagespeedonline/v5/runPagespeed.
- Extracts cached Lighthouse JSON from pagespeed.web.dev/analysis/... share links without consuming PageSpeed API quota.
- Supports single target analysis through /PageSpeed.
- Supports batch analysis from command arguments or a text file.
- Saves raw-report.json, summary.json, and ai-brief.md for each target.
- Produces an AI-ready Markdown brief with concrete evidence and implementation guidance.
Supported Platforms
Use this skill as a reference template for these AI agents, model workflows, or team SOPs.
Configuration & Updates
An API key is optional for single fresh URL audits. Without a key, PageSpeed-CLI still calls Google PageSpeed directly and prints a warning because anonymous quota may fail.
For batch or parallel runs, configure an API key:
export PAGESPEED_API_KEY="..."
pagespeed-cli batch --input urls.txt --jobs 4You can also pass a key per command:
pagespeed-cli --api-key "$PAGESPEED_API_KEY" /PageSpeed https://example.comShare-link extraction does not rerun PageSpeed and does not consume PageSpeed API quota.
README Command Examples
git clone https://github.com/BHINNKJ/PageSpeed-CLI.git
cd PageSpeed-CLI
python3 -m pip install -e ".[dev]" pagespeed-cli /PageSpeed https://example.com pagespeed-cli /PageSpeed "https://pagespeed.web.dev/analysis/..." Tags
FAQ
What is PageSpeed CLI Skill?
AI-ready PageSpeed Insights and Lighthouse CLI for Core Web Vitals audits, performance fixes, SEO optimization, and before/after verification.
Who should use PageSpeed CLI?
Use this skill if your team, operator, developer, or AI agent works on Development, Data & Analysis, Testing, Marketing & Growth workflows.
When should you use PageSpeed CLI Skill?
Use it when a task involves PageSpeed, Lighthouse, Core Web Vitals, SEO, or when the workflow should become a Claude Skill, Codex Skill, Gemini Skill, Kimi Skill, GLM Skill, or team SOP.
How do you download PageSpeed CLI Skill?
Use the “Download Skill File” button near the top of the page or in the Skill Information panel. The local Markdown file saved by EasyGlobe is bhinnkj-pagespeed-cli.md.
How do you install PageSpeed CLI Skill?
Check the Installation section on this page. If the archived README does not include an explicit installation section, open the Skill URL and follow the official README, platform documentation, or marketplace instructions.
How do you use PageSpeed CLI Skill?
Check the Usage, Capabilities, and README summary sections. The page extracts usage notes, command examples, and workflow context from the archived README where available.
Does PageSpeed CLI Skill work with Claude, Codex, Gemini, Kimi, and GLM?
This page packages the resource as reusable AI agent skill material for Claude Skills, Codex Skills, Gemini Skills, Kimi Skills, GLM Skills, ChatGPT Skills or team SOPs. Actual runtime compatibility depends on the official instructions at the Skill URL.
Where is the Skill URL for PageSpeed CLI Skill?
The Skill URL is shown in the Skill Information panel. You can also use the “Open Original Skill” button near the top of the page to open the original project or official page.
What is the difference between the local download and the Skill URL?
The local download is an EasyGlobe-saved Markdown copy for archiving, reading, and reuse. The Skill URL points to the original project, official documentation, or marketplace page for the latest instructions.