KENYA · GUIDE 0592 · EDITION 4.7
Website speed audit in Kenya: Equipment and Supplier Buying Checks
Editorial update: 28 October 2026 · Business planning reference · Review scope
Purchase for the required result
Compare Audit tooling, Page inventory, Evidence storage by specification, compatibility and buying checks, before comparing prices.
This is a planning reference for website speed audit. The order below is an invented teaching case. It is not a completed customer job, an operating approval or a prediction of demand or earnings.
The example offer and its boundary
Fictional speed review SPD-92 examines home, services and contact pages with three comparable mobile lab runs per page. Output is nine saved reports, a settings log and three prioritised opportunities. No performance score or improvement is invented; live optimisation and promised search rankings are excluded.
The resource brief to send for quotations
| Resource | Required variant or quantity | Inspection or document check |
|---|---|---|
| Audit tooling | Lighthouse/PageSpeed-compatible workflow with exported reports. | Record version and settings. |
| Page inventory | Three exact URLs and relevant visitor state. | Avoid authenticated personal data in shareable reports. |
| Evidence storage | Client-controlled nine-report folder. | Open saved reports and match names to page/run. |
Use the delivery checkpoints to check suitability
| Planning stage | Acceptance evidence to agree |
|---|---|
| Fix conditions | Compare like conditions; a fast desktop run cannot substitute for mobile evidence. |
| Capture baseline | Report representative results and spread, not only the best score. |
| Separate field data | Missing field data is unknown, not proof that users have no problems. |
| Inspect causes | A tool suggestion becomes a scoped hypothesis, not an automatic instruction to remove business-critical scripts. |
| Deliver retest plan | Client approves any implementation separately; no before/after claim without actual repeat evidence. |
Compare like with like
Request the same specification, unit/pack size, usable quantity, destination, lead time and support terms from each supplier. Keep an unmatched lower-priced variant separate. A supplier’s photograph, headline price or description does not establish that the delivered item fits this order.
Goods received record
| Field | What to enter for this offer |
|---|---|
| Quote and delivery reference | Exact supplier quote and date, plus the receiving document |
| Item match | Record version and settings. |
| Quantity and condition | Count or measure the actual received lot; keep mismatches separate |
| Release decision | Client approves any implementation separately; no before/after claim without actual repeat evidence. |
| Unresolved evidence | No site measured; nine reports are the proposed job output. |
Do not use an item with an unresolved suitability question for work that depends on that question. Obtain the relevant competent assessment rather than treating this checklist as technical approval.
References and their limits
Introduction to Lighthouse — Chrome for Developers
Automated audit execution/report export, not complete security/accessibility certification. Reference check recorded 2026-10-26.
Why lab and field data can differ — web.dev
Lab/field interpretation; no measured client performance supplied. Reference check recorded 2026-10-26.
Rights Of A Data Subject
Kenyan privacy principles and data minimisation; not a complete compliance assessment. Reference check recorded 2026-10-26.
Recorded references support only the scope stated beside them. They do not prove current supplier stock, a local quotation, actual buyer demand, operator competence or the feasibility of this particular business. Later editorial changes do not refresh earlier source-check dates.
Prepared by Business Starter Guides using AI-assisted drafting and desk editorial checks. Independent operator trials and specialist certification are not claimed. See the editorial method for the review scope.
Editorial method and evidence limits