A host upgrade is proposed without evidence of the bottleneck

What to change

Ask which part of the delay the upgrade is expected to improve. Separate server response, asset transfer and browser work using the available diagnostic evidence. A hosting change may be justified, but the proposal should identify the affected routes and the measurable condition it intends to address. Agree a comparison plan before committing so the practice can evaluate whether the change solved the stated problem rather than merely moved the site.

A worked example

Illustrative example

Illustrative test: A controlled sample tests the same routes before and after the proposed adjustment.

How to check the result

The recommendation is tied to a demonstrated bottleneck and testable outcome.

A mistake to avoid

A higher hosting tier cannot automatically fix expensive browser-side work.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordRequest evidence identifying the suspected server-side constraint.Compare affected and unaffected pages under consistent conditions.Define the expected post-change measurement before approving the move.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.