Slow loading and delayed interactions require different fixes, and laboratory scores can hide real user problems. This skill guides measurement and targeted browser performance improvements.
Review the Skillstore skill "web-performance" from https://skillstore.io/skills/shreyam1008-web-performance.md and its manifest at https://skillstore.io/api/skills/shreyam1008-web-performance/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
All 22 static findings are false positives in browser performance guidance. Backticks mark Markdown formatting, while reconnaissance matches describe rendering stages and DOM layout measurements. No evidence found of shell execution, host reconnaissance, data exfiltration, or prompt injection in the reviewed SKILL.md.
shreyam1008. (2026). web-performance security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-web-performance/audits/1
BibTeX 引用
@techreport{shreyam1008-shreyam1008-web-performance-2026,
author = {shreyam1008},
title = {web-performance security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/shreyam1008-web-performance/audits/1},
note = {Author version unspecified}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "web-performance security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "shreyam1008"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/shreyam1008-web-performance/audits/1"
identifiers:
- type: other
value: "skillstore:shreyam1008-web-performance:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 评分
评分依据证据置信度: 中
55
架构
85
可维护性
87
内容
65
社区
91
规范符合性
你能构建什么
Improve Storefront Loading
Prioritize the measured LCP resource and reduce blocking scripts, oversized images, and font delays on product pages.
Investigate Slow Interactions
Use interaction traces to separate input delay, handler work, and presentation delay before selecting targeted fixes.
Stabilize Browser Animation
Review animation scheduling, layout reads and writes, and frame timing across display refresh rates.
试试这些提示
Understand My Metrics
Review these LCP, INP, and CLS measurements: [measurements]. Explain the targets and identify what additional field or laboratory evidence is needed.
Prioritize Loading Fixes
Review this loading trace and resource waterfall: [evidence]. Identify the LCP resource, blocking work, and three prioritized changes with validation steps.
Diagnose Interaction Delays
Analyze this interaction trace: [trace]. Separate input delay, handler work, and presentation delay. Recommend measured fixes and supported scheduling fallbacks.
Review Runtime Performance
Review this animation loop and traces: [evidence]. Compare 60Hz and 120Hz budgets, layout batching, worker opportunities, and GPU constraints. Define regression checks.
最佳实践
Measure the dominant loading or runtime cost before making changes, then repeat the same measurement after each fix.
Evaluate field metrics at the 75th percentile and separate mobile, desktop, and laboratory results.
Feature-detect scheduling APIs and test representative devices, refresh rates, and GPU conditions.
避免
Treating one fast Lighthouse run as proof of healthy field Core Web Vitals.
Preloading many resources without confirming their importance to the measured critical path.
Changing renderers or applying workers and WebAssembly without evidence that they address the dominant bottleneck.
常见问题
What does this skill cover?
It covers browser loading, Core Web Vitals, interaction responsiveness, layout work, and animation timing.
Does it run an automatic performance audit?
No. It provides guidance and a checklist; browser tools or supplied measurements are needed for diagnosis.
Which measurements should I provide?
Provide field LCP, INP, and CLS when available, plus loading waterfalls or interaction traces relevant to the reported problem.
Is Lighthouse enough to validate improvements?
No. Laboratory runs help diagnose problems, but field metrics must be evaluated separately at the 75th percentile.
Does it handle React and GPU bottlenecks?
It helps identify browser-level costs. Isolated React rendering and detailed GPU optimization need specialist workflows.
Are scheduling APIs supported everywhere?
Support varies. Feature-detect scheduler APIs and retain appropriate fallbacks; reserve idle callbacks for deferrable work.