CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

page-load-time

Use when auditing slow page loads, heavy assets, or rendering delays related to Keep page load time under 3 seconds. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/page-load-time/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient overview with exemplary progressive disclosure (one clearly signaled, verified reference file). Its weaknesses are in execution detail: the Check and Fix sections stay at the technique-name level with no runnable command or measurement procedure, and the workflow lacks a post-fix re-measurement checkpoint to close the feedback loop.

Suggestions

In the Check section, name the measurement method concretely — e.g., a Lighthouse CLI one-liner or DevTools Network/LCP steps — instead of just "Measure the page load time".

Add a re-measure/verify step after Fix (e.g., "Re-run the measurement and confirm load time is under 3 seconds; if not, profile the next bottleneck") to close the workflow's feedback loop.

Deduplicate the 53% statistic and 3-second threshold between the intro paragraph and the Quick Reference bullets to tighten token usage.

DimensionReasoningScore

Conciseness

The ~45-line body is lean overall, but the 53% abandonment statistic and the 3-second threshold are each stated twice — once in the intro paragraph ("53% of mobile users abandon sites that take longer than 3 seconds") and again in the Quick Reference bullets. Minor duplication that could be trimmed keeps it at anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Concrete guidance exists ("Focus on Core Web Vitals: LCP, FID/INP, CLS", "Test on throttled 3G", "lazy loading, CDN usage, caching strategies"), but the body contains no executable command or measurement step — "Measure the page load time and verify it's under 3 seconds" names no tool or procedure, and all code is deferred to the reference file. This is incomplete concrete guidance, matching anchor 3 rather than the copy-paste-ready anchors 4-5; it sits above anchor 2 because specific metrics and techniques are named.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is present and sensibly ordered (measure before optimizing), but validation is left implicit: the Check section specifies no measurement method, and there is no re-measure step after Fix to confirm the 3-second target is met. Anchor 3 (steps listed, checkpoints missing or implicit) fits; it is below anchor 4 because no explicit post-fix verification exists, and this is not a destructive/batch skill so the forced cap is not the binding reason.

3 / 5

Progressive Disclosure

The body is a genuine overview and the single reference is well signaled — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — pointing one level deep to a file that exists in the bundle and contains self-contained code examples with no nested references. This matches the clear-overview, well-signaled, one-level-deep anchor exactly.

5 / 5

Total

15

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solidly above-midpoint description with an explicit trigger clause, concrete tool-specific actions, and mostly natural trigger terms. Its main defects are an awkward template artifact ("related to Keep page load time under 3 seconds" reads like a pasted rule title), a 'what' statement that is never crisply declared on its own, and missing common synonyms like "page speed" or "Core Web Vitals".

Suggestions

Rewrite the trigger clause to remove the interpolated rule title — e.g., "Audits page-load performance and verifies bottlenecks using DevTools, Lighthouse, or field data. Use when pages load slowly, assets feel heavy, or rendering is delayed."

Lead with a standalone third-person 'what' statement before the 'Use when' clause so the capability is explicit rather than implied by the trigger.

Add natural trigger synonyms such as "page speed", "site performance", and "Core Web Vitals" / "LCP" to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names several concrete actions — "auditing slow page loads, heavy assets, or rendering delays" and "Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes" — with specific tools. It falls short of anchor 5 because coverage is incomplete (no measure/fix scope), but exceeds anchor 3 since it lists more than 1-2 concrete actions.

4 / 5

Completeness

Both parts are present: an explicit "Use when auditing slow page loads, heavy assets, or rendering delays" trigger clause and a what-portion ("Verify the actual bottleneck in DevTools, Lighthouse, or field data"). Not anchor 5 because the 'what' is woven into the when-clause and an imperative rather than stated as a standalone capability statement, and the awkward interpolated phrase "related to Keep page load time under 3 seconds" muddies the lead.

4 / 5

Trigger Term Quality

Natural trigger phrases like "slow page loads", "heavy assets", "rendering delays", and "page load time" give good keyword coverage users would actually say. Missing common variations such as "page speed", "site is slow", or "Core Web Vitals", so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

It carves a fairly distinct web-performance-audit niche with tool-specific triggers (DevTools, Lighthouse, field data), giving minimal conflict risk. Minor overlap remains with closely related performance skills (asset optimization, bundle size), matching anchor 4 rather than the clear-niche anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/page-load-time/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.