KENYA · GUIDE 0592 · EDITION 4.2
Website speed audit in Kenya: Customers and Market Demand
The buyer and the buying decision
Small businesses with slow key pages. The offer to test is: Investigate website performance within a defined page and device scope.
Review speed for priority pages and real customer journeys, agreeing testing conditions, available analytics, hosting access, and which improvements require separate implementation work.
Separate interest from an accepted order
Measure a representative page and repeat under stated conditions.
The purpose of this test is to establish whether the buyer accepts the specified result, delivery arrangement and payment terms. An encouraging interview does not establish repeat demand. Ask what the buyer currently uses, what would make them change supplier and who has authority to approve the first order. Record a refusal as carefully as an enquiry so that unsuccessful offers do not disappear from the evidence.
Collect evidence specific to this offer
Keep page URLs, testing conditions, measurements, visible delays, suspected causes, implementation dependencies, and recommendations ranked by plausible customer benefit and delivery effort.
| Question to resolve | Evidence to retain |
|---|---|
| What exactly will the buyer accept? | Repeat representative checks under documented conditions and compare visible user delays, distinguishing a stable issue from a single unusual test result. |
| What is included in the first trial? | Review speed for priority pages and real customer journeys, agreeing testing conditions, available analytics, hosting access, and which improvements require separate implementation work. |
| How will a prospect see the offer? | Present a measurable page-specific finding rather than a universal speed promise. |
| What must happen before repeating the trial? | Before-and-after results use comparable conditions and no ranking improvement is guaranteed. |
Decide whether to continue
Review the specification with the buyer before committing to tools or stock. A trial is commercially useful only if actual costs, rejected work, time spent and cash collected can be reconciled. A faster score can hide poor customer experience if the ordering interaction still stalls or a recommended change breaks essential third-party functionality.
If a buyer changes the required output, record a new scope and re-cost the test. Do not count a request for a different product as proof of demand for the original one. Keep personal contact details in your private records and use customer statements publicly only with permission.
Turn the example into a buyer test
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.
| Buyer discussion | Evidence to retain |
|---|---|
| Specification to confirm | Compare like conditions; a fast desktop run cannot substitute for mobile evidence. |
| Output to inspect | Client approves any implementation separately; no before/after claim without actual repeat evidence. |
| Failure that can defeat acceptance | Scores vary widely |
Ask the buyer to describe one acceptable and one unacceptable result. Record the decision maker, price basis, quantity, handover point and payment date privately. A sample request, an encouraging conversation and an accepted order are different evidence. Keep the first commitment within your demonstrated capacity; no customer interview or successful trial is asserted here.
What a failed test should change
Compare run settings/cache and third-party activity.. If the offer cannot meet that check, revise the specification or process before promising a repeat. Keep rejected offers and reasons in the same register as positive replies so that your record does not exaggerate demand.