Index of every page on this site: llms.txt
All skills
cloudflare avatar

/web-perf

@5108325 official
by cloudflarecloudflare/skills3.4k stars
357
Run it yourself

Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.

Use this Skill: https://skilld.dev/gh/cloudflare/skills/web-perf

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesskill-feedback.md

≈696 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Skill feedback

GitHub issues are public: anyone can read an issue once it is posted. Never include sensitive information, and never post an issue until the user has seen the exact title and body and approved it.

Use this when the user reports that the web-perf skill gave incorrect or outdated guidance, is missing information, or could be improved. This is about the skill (agent instructions), not about Cloudflare products.

What not to include

The issue is drafted from the conversation, so remove the following before drafting and describe the problem in general terms instead:

  • Credentials, API tokens, secrets, and passwords
  • Account IDs, zone IDs, and other resource identifiers
  • Customer or personal data, such as names, email addresses, and IP addresses
  • Internal hostnames and URLs
  • Private code, configuration, and logs

Steps

  1. Ask permission – Ask the user if they would like to submit feedback to the skill maintainers. If they decline, move on.

  2. Draft the issue – Fill in the table below from the conversation and use it as the issue body. Always identify which specific file and section caused the problem. Leave out everything listed in What not to include.

  3. Review with the user – Show the user the exact title and body, then ask a yes/no question, such as "Post this as a public issue on cloudflare/skills?" Submit only after the user answers yes. If they ask for changes, apply them and ask again. If they answer no, do not post. Agreeing to send feedback in step 1 is not approval of the text.

  4. Submit – Create a GitHub issue on the cloudflare/skills repository with the approved draft as the body, for example with gh issue create --repo cloudflare/skills. The title must follow this format: skill-feedback: web-perf: <summary of the problem>.

  5. Share the result – Share the issue URL with the user after submission. If submission fails, give the user the approved title and body, and this link to create the issue manually: https://github.com/cloudflare/skills/issues/new

Issue body

Field Value
Type bug (incorrect guidance), outdated, missing, or improvement
Skill web-perf
Source File and section, e.g. SKILL.md > "Section name" or references/<file>.md > "Section name"
Agent The agent and model in use, if known
Task What the user was trying to do, e.g. "deploy a preview"
Expected What should have happened, e.g. "Create a Preview deployment"
Actual What the skill said or what happened, e.g. "Unknown option: --preview"
Impact The effect on the user, e.g. "Time spent finding the correct syntax"
Suggested fix How the skill should change; leave blank if unsure

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning23d5 checks · Risk SAFE
  • Gen Agent Trust Hub23d

    This skill facilitates web performance auditing by integrating with browser automation tools. It includes considerations regarding external package dependencies and the processing of untrusted web content, which are standard for this type of utility.

  • Socket23d

    No alerts

  • Snyk23d

    Risk: MEDIUM · 1 issue

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 5108325. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 4 weeks ago
  • Performance
  • MCP
  • web-vitals
  • lighthouse
  • chrome-devtools
  • auditing
  • core-web-vitals
  • network-analysis
  • accessibility

README badge

README badge for cloudflare/skills/web-perf

Analyzes web performance metrics (Core Web Vitals, FCP, TBT, Speed Index) using Chrome DevTools MCP to identify render-blocking resources, network dependency chains, layout shifts, and caching issues. Use when auditing page load performance, Lighthouse scores, or debugging site speed problems.

Generated from the current SKILL.md.

Does this skill require Chrome DevTools MCP to be configured?
Yes. The skill uses Chrome DevTools MCP for tracing and analysis. It will check for available tools at the start and provide setup instructions if the MCP server is not configured.
What metrics does this skill measure?
It measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index). It also identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps.
Can this skill audit third-party sites without codebase access?
Yes. The skill can run Phases 1-4 (trace, vitals, network, accessibility) on any URL. Phase 5 (codebase analysis) is skipped if no repository access is available.
Does this skill provide code snippets or configuration examples?
Yes. The skill includes a workflow checklist, reference tables for tool calls and metric thresholds, and guidance on framework detection and bundler-specific optimizations. Recommendations include specific code snippets or config changes.
What happens if Chrome DevTools insight names don't match?
The skill instructs you to inspect the trace response to discover available insights for your Chrome version, since insight names may vary across DevTools versions.

Generated from the current SKILL.md. These answers refresh after source changes.