TS35Performance and deployment
Performance and deploymentDoes the lab test help identify the cause?
Laboratory tests support diagnosis rather than simulate field data.
Prepare evidence
- In the app
- Evidence import
- You provide
- Report and test conditions
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
A slowdown. Conditions to explain it.
Laboratory tests support diagnosis rather than simulate field data.
According to Google
Lab measurements use controlled conditions; field data comes from real visits. Different results from these sources are therefore not necessarily contradictory.
Check
The same scenario. A repeatable problem.
In TSEP Control
You import evidence for this control. The engine assesses it within the declared scope; missing items remain visible.
Your contribution
Define the scope and expectations before collection. Gather the items below and supply the requested reviews.
With your own tools
With your own toolsRun Lighthouse or Chrome Performance tools with a documented scenario. Retain version, device, network, traces and results from repeated runs; keep these measurements separate from field data.
Evidence to retain
Reproducible Lighthouse/WebPageTest report tied to a remediation hypothesis.
What this result covers
A Lighthouse score of 100 guarantees neither field CWV nor rankings.
Act
An observed cause. A targeted fix.
Connect the diagnosis to a hypothesis and compare runs under the same conditions.
Recheck
Same conditions. A new measurement.
After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.
To go further.
Statuses, sources and method.
Understand the statusesC · NC · NT · NA
The same legend in guides, analysis and demo. Each status depends on the control’s evidence and rules.
- C · Verified
- The criterion is met within the assessed scope. Keep dated evidence for the next comparison.
- NC · To correct
- Connect the diagnosis to a hypothesis and compare runs under the same conditions.
- NT · Not established
- Evidence or confirmations are insufficient to conclude. Supply what is missing; this status does not establish an SEO error.
- NA · Not applicable
- The control does not apply to the scope under its rules, with a retained justification. Missing evidence alone does not make it non-applicable.
Sources and references1 reference
Detailed method and rules2 rules
Control method and criteria
Method
Retain URL, device, network profile, tool version and detailed metrics.
Acceptance criteria
URL, tool/version, device, network and measurements are retained; conclusions remain limited to the lab and tied to a hypothesis.
Non-applicability
No lab diagnostic planned in this scope.
Detailed rules
TS35-A01 · Repeatable laboratory context and measurements
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Declared performance scope for this control and qualified reading profile.
Evidence
Original JSON with source/date/hash; plan and supplied review when required, diagnostics and limits under docs/performance-evidence.md.
Method
Retain a planned series of 2–10 distinct Lighthouse reports, dates, URLs, tool/version, client, device, throttling, native measures and spread.
Acceptance criteria
Series matches planned context/count. URL contrary to plan fails; different context, missing measure or runtime error remains inconclusive.
When the result remains inconclusive
Insufficient source/plan/dates/measures; unsupported format/profile, scope mismatch, exceeded bounds or missing review under the contract. Absence never becomes C or NA.
Non-applicability
No automatic atomic exemption; whole-control non-applicability requires its own evidence.
Assumptions
Supplied data/reviews are not authenticated. Plan precedes assessment and lab runs; a historical cohort is not preregistration.
Limitations
C describes documentation, not good performance. No display/ranking, demonstrated cause, automatic human review or global conformity. Replay performs no new measurement.
TS35-A02 · Diagnostic hypothesis and next verification
Protocol assessment mode : manual. App availability is shown on the control card.
Scope
Declared performance scope for this control and qualified reading profile.
Evidence
Original JSON with source/date/hash; plan and supplied review when required, diagnostics and limits under docs/performance-evidence.md.
Method
Bind a supplied review to ordered reports, measured metrics, a hypothesis and next measurement. Separate laboratory, INP and field results.
Acceptance criteria
Bound review names hypothesis, metrics and action without field substitution. Explicit lab/CWV or TBT/INP substitution fails; absent review is inconclusive.
When the result remains inconclusive
Insufficient source/plan/dates/measures; unsupported format/profile, scope mismatch, exceeded bounds or missing review under the contract. Absence never becomes C or NA.
Non-applicability
No automatic atomic exemption; whole-control non-applicability requires its own evidence.
Assumptions
Supplied data/reviews are not authenticated. Plan precedes assessment and lab runs; a historical cohort is not preregistration.
Limitations
C describes documentation, not good performance. No display/ranking, demonstrated cause, automatic human review or global conformity. Replay performs no new measurement.
Rule version 0.2.0-rc.1 · Public protocol reference · Versioned source
Put it into practice
A report and its test conditions.