A third-party script dominates the performance cost

What to change

Evaluate the dependency and its purpose together. Ask for a controlled comparison with the script enabled and disabled, using an authorised test environment where necessary. Have the business owner explain what the widget contributes and whether a simpler alternative exists. The decision should consider the observed cost, required function and operational consequences, rather than treating every external script as either indispensable or automatically unacceptable.

A worked example

Illustrative example

Illustrative test: A preview comparison shows the performance difference without changing the live visitor experience. Record the exact preview configuration so the performance difference can be reproduced without disabling the live function.

How to check the result

The decision records measured impact and the accepted functional trade-off.

A mistake to avoid

Removing a script without checking dependencies can break an important service.

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 recordIdentify the script and the function it supports.Compare matched tests with the dependency isolated.Review alternatives with the owner of that function.

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.