Skip to main content
skillsFirst-partyReview first Safety Privacy

PageSpeed Insights Optimization Skill for AI Agents

Structured optimization workflow for PageSpeed Insights and Lighthouse that improves Core Web Vitals without changing UI/UX.

HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:advancedType:generalVerified:draft
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://web.dev/articles/vitals, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/pagespeed-insights-optimizer.mdx
Package URL
/downloads/skills/pagespeed-insights-optimizer.zip
Package SHA256
bcb96e6ace1641db8801d2c105e7491c4ecb18fc181ae9a73378e0578d932fc4
Safety notes
The install command downloads a zip from heyclau.de and unzips it into the working directory, and the skill runs local build/type-check commands and can patch frontend code for verification; review the package and any proposed code changes before applying.
Privacy notes
Running PageSpeed Insights / Lighthouse submits the target URL to Google's PSI service (and field data may be drawn from the public CrUX dataset); only test URLs you are authorized to assess and avoid authenticated or preview URLs that would expose private content.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2026-04-10

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

4 to clear

Platforms

6 listed

Difficulty

78/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup. Includes a review or approval gate.

0/4 ready
Install & runtime1Review & approval1General2

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: permissions & scopes, network access.

2 areas
  • SafetyNetwork accessThe install command downloads a zip from heyclau.de and unzips it into the working directory, and the skill runs local build/type-check commands and can patch frontend code for verification; review the package and any proposed code changes before applying.
  • PrivacyPermissions & scopesRunning PageSpeed Insights / Lighthouse submits the target URL to Google's PSI service (and field data may be drawn from the public CrUX dataset); only test URLs you are authorized to assess and avoid authenticated or preview URLs that would expose private content.

Safety notes

  • The install command downloads a zip from heyclau.de and unzips it into the working directory, and the skill runs local build/type-check commands and can patch frontend code for verification; review the package and any proposed code changes before applying.

Privacy notes

  • Running PageSpeed Insights / Lighthouse submits the target URL to Google's PSI service (and field data may be drawn from the public CrUX dataset); only test URLs you are authorized to assess and avoid authenticated or preview URLs that would expose private content.

Prerequisites

  • Live URL or preview URL that can be tested by Lighthouse/PageSpeed Insights
  • Access to run local build/type-check commands
  • Ability to patch frontend code and redeploy for verification
  • Optional access to Chrome DevTools trace for deep diagnostics

Schema details

Install type
package
Reading time
7 min
Difficulty score
78
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
bcb96e6ace1641db8801d2c105e7491c4ecb18fc181ae9a73378e0578d932fc4
Skill and platform metadata
Skill type
general
Skill level
advanced
Verification
draft
Verified at
2026-04-10
Retrieval sources
https://web.dev/articles/vitals
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Run the PageSpeed Insights optimizer skill on this route and only propose
changes that preserve visual output and behavior."

# Required output
1) Baseline metrics (mobile + desktop): FCP, LCP, TBT, CLS, SI
2) Top bottlenecks ordered by expected impact
3) Smallest safe patch set
4) Validation rerun with before/after deltas

# Hard constraints
- No visual redesign
- No feature removal
- Keep accessibility and SEO intact

About this resource

Overview

This skill gives an AI agent a strict, repeatable process for improving PageSpeed Insights and Lighthouse results without changing your visual design or removing product functionality. It is built for real-world optimization work: isolate bottlenecks, apply minimum-safe fixes, re-measure, and stop once gains flatten.

Compatibility

Native

  • Claude Code / Claude: direct skill package support using SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-format content (SKILL.md) and can be used as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and other IDE agents: use the same SKILL.md content as a workflow template or prompt file if native skill import is unavailable.

Prerequisites

  • A route to test (production, staging, or preview URL)
  • Baseline Lighthouse/PageSpeed run for mobile and desktop
  • Ability to run project checks after edits (type-check, build, regression tests)
  • Access to deploy and re-test

What This Skill Optimizes

  • LCP diagnosis and render delay reduction
  • Render-blocking CSS/JS mitigation
  • Unused JavaScript/CSS reduction
  • Third-party script scheduling strategy
  • Cache policy and static asset delivery consistency
  • Regression-safe micro-optimizations for initial route payload

How to Use This Skill

Prompt Pattern

Use this prompt:

Apply the PageSpeed Insights optimizer skill to <route>.
Constraints:
1) No UI/UX redesign or feature removal.
2) Preserve accessibility and SEO behavior.
3) Prioritize highest-impact, lowest-risk fixes first.
Deliverables:
- Baseline metrics table (mobile + desktop)
- Ranked bottlenecks and root causes
- Minimal patch plan
- Post-change metrics with deltas

Execution Flow

  1. Capture baseline metrics and record exact failing audits.
  2. Identify the current LCP element and why it is delayed.
  3. Apply smallest change set that targets top bottlenecks only.
  4. Re-run benchmarks and compare deltas.
  5. If gains are below threshold, stop and report diminishing returns.

Optimization Playbook

1) LCP and above-the-fold path

  • Reduce server and render delay for the LCP element.
  • Ensure critical route data and styles load predictably.
  • Move non-critical work after first render.

2) Render-blocking resources

  • Keep critical CSS minimal.
  • Defer non-critical scripts and low-priority widgets.
  • Avoid introducing blocking dependencies in root layout.

3) Bundle pressure

  • Defer or split route-noncritical bundles.
  • Remove or gate dead/unused client-side modules.
  • Keep initial route payload focused on first-screen needs.

4) Third-party impact

  • Delay analytics and low-priority scripts.
  • Verify no third-party library blocks first paint.
  • Keep third-party bytes and main-thread work accountable.

5) Cache + delivery checks

  • Ensure static assets use long-lived immutable caching where safe.
  • Ensure API and dynamic routes are not accidentally over-cached.
  • Validate cache behavior after deploy.

Troubleshooting

Issue: Score regresses after adding "helpful" scripts
Fix: Prioritize first-view rendering; move non-critical scripts to idle/lazy load.

Issue: LCP remains high despite JS reductions
Fix: Re-check the actual LCP element, image/font loading path, and render delay.

Issue: Mobile score volatile between runs
Fix: Use median over multiple runs and compare stable deltas, not single spikes.

Issue: Good lab scores but poor field data
Fix: Track CrUX trends and verify real-user bottlenecks (device/network mix, third-party load).

Notes for This Repository

  • Use the generated index and existing scripts (pnpm type-check, pnpm build) after each optimization patch.
  • Keep changes scoped to measurable performance deltas.
  • Preserve the current visual layout and interaction model.

Source citations

Add this badge to your README

Show that PageSpeed Insights Optimization Skill for AI Agents is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/pagespeed-insights-optimizer.svg)](https://heyclau.de/entry/skills/pagespeed-insights-optimizer)

How it compares

PageSpeed Insights Optimization Skill for AI Agents side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field

Structured optimization workflow for PageSpeed Insights and Lighthouse that improves Core Web Vitals without changing UI/UX.

Open dossier

Microsoft .NET team skill marketplace for AI coding agents working on .NET, C#, ASP.NET Core, Blazor, MAUI, diagnostics, MSBuild, NuGet, upgrades, tests, AI workflows, RAG pipelines, and C# MCP servers.

Open dossier

Expert Claude Code Chrome browser QA capability pack applying documented Claude in Chrome enablement, browser automation boundaries, and web QA checkpoint workflows.

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verified2026-04-10Package not verifiedPackage not verified
Source provenanceDiffersSource-backedSource-backedSubmission linkedSource submission
SubmitterDifferskiannidev
Install riskReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy
Brand
Categoryskillsskillsskills
Sourcefirst-partysource-backedsource-backed
AuthorJSONbored.NET Team at Microsoftkiannidev
Added2026-04-102026-06-182026-06-16
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLIVS Code
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo
Safety notesThe install command downloads a zip from heyclau.de and unzips it into the working directory, and the skill runs local build/type-check commands and can patch frontend code for verification; review the package and any proposed code changes before applying..NET build, test, upgrade, package, template, publish, and migration tasks can modify project files, lock files, generated code, packages, app settings, and deployment artifacts. Diagnostics skills may suggest collecting traces, dumps, counters, crash data, MSBuild binlogs, or performance profiles; collect those artifacts only with explicit approval and storage controls. MCP server skills can expose local code, files, APIs, credentials, or production services as callable tools; review tool descriptions, parameter validation, authorization, and transport choice before connecting clients. NuGet and publish workflows can push packages or artifacts to public or private feeds; verify package IDs, versions, API keys, feed targets, and release policy before publishing. Upgrade and modernization guidance should be verified against each application's framework support window, deployment target, package compatibility, and rollback plan.Browser automation can access logged-in sessions—use staging accounts only. Claude chooses Chrome before computer use for web tasks when configured. Review permission prompts before approving navigation on sensitive pages.
Privacy notesRunning PageSpeed Insights / Lighthouse submits the target URL to Google's PSI service (and field data may be drawn from the public CrUX dataset); only test URLs you are authorized to assess and avoid authenticated or preview URLs that would expose private content..NET repositories may contain connection strings, appsettings secrets, user secrets, certificates, environment variables, telemetry keys, logs, traces, dumps, package credentials, and production data. MSBuild binlogs, crash dumps, profiler output, and test artifacts can contain source paths, dependency graphs, request data, exception payloads, configuration values, and environment details. MCP servers created with these skills may forward prompts and tool inputs to local processes, HTTP services, databases, cloud APIs, or third-party model providers depending on the implementation. Keep private NuGet credentials, signing keys, deployment secrets, customer data, dumps, and proprietary source out of public prompts, issues, pull requests, and shared artifacts.Browser QA sends page content to the model—avoid customer PII in test flows. Screenshots and DOM snapshots may include session tokens in dev tools—close extras.
Prerequisites
  • Live URL or preview URL that can be tested by Lighthouse/PageSpeed Insights
  • Access to run local build/type-check commands
  • Ability to patch frontend code and redeploy for verification
  • Optional access to Chrome DevTools trace for deep diagnostics
  • An AI coding assistant or skill host that supports Agent Skills, plugin marketplaces, or direct skill installation.
  • .NET SDK and project-local build/test tooling appropriate for the repository being edited.
  • For MCP server work, the official C# MCP SDK, MCP project templates, and a target transport choice such as stdio or HTTP.
  • For diagnostics, permission to collect traces, dumps, logs, counters, binlogs, or test output from the target environment.
  • Claude in Chrome extension installed per official Chrome documentation.
  • Staging web app URL and test credentials scoped to non-production.
  • Team policy for browser automation on authenticated sessions.
Install
curl -L https://heyclau.de/downloads/skills/pagespeed-insights-optimizer.zip -o pagespeed-insights-optimizer.zip && unzip -o pagespeed-insights-optimizer.zip -d ./pagespeed-insights-optimizer
codex plugin marketplace add dotnet/skills
Config
Citations
ClaimUnclaimedUnclaimedUnclaimed
Open 3 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.