Support & operations · Practical guide

Ask what a hosting upgrade will actually improve

A supplier recommends a more expensive hosting plan based on a slow page score alone.

Healthcare website support desk with a system checklist, telephone and orange notebook.
Know who to call and what help your support arrangement includes.

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. A supplier may recommend a higher hosting tier when a slow guide is actually dominated by browser work from a widget. The diagnostic review separates those contributions before spending is approved. If server response is instead the demonstrated constraint, the practice agrees the expected improvement and comparable routes in advance. The eventual review can then judge the proposal against its stated purpose rather than equating a higher bill with a faster visitor journey.

Healthcare website maintenance with infrastructure, a status panel, tools and an operational checklist.
Monitor the useful journey, not just whether a server responds.
Healthcare backup and recovery illustrated by storage copies, an archive folder and a restoration route.
Test whether a backup can restore a usable service.

What this means for your practice

A slow page score alone does not establish that more expensive hosting is the right remedy. Ask your supplier to identify the part of the delay they believe the upgrade addresses. Waiting for the server, downloading large assets and processing work in the browser are different problems. The proposal should name affected pages and an observable outcome. Agree the comparison before spending or moving the site, so you can judge whether the change resolved the stated constraint. A hosting upgrade may be justified, but its value should follow the evidence rather than the price tier. Keep unaffected pages as useful comparisons during the review.

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.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore support & operations services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.