Load third-party scripts only where they’re needed
Payment SDKs, chat widgets, review tools and marketing tags are often loaded on every page. Restrict them to where they’re used to cut requests and speed pages up.
Payment SDKs, chat widgets, review tools and marketing tags are often loaded on every page. Restrict them to where they’re used to cut requests and speed pages up.
A payment-provider SDK was loading on every page although it was mainly needed on product, cart and checkout. Restricting it removed many requests and reduced transferred data site-wide.
Common offenders
- Payment provider SDKs on every page
- Chat widgets loading on first paint
- Review widgets on pages without reviews
- Multiple analytics and marketing tags
- Personalisation and A/B testing scripts
How to fix
Load payment SDKs only on product/cart/checkout, lazy-load chat on interaction or after idle, and remove tags nobody uses.
Common mistakes to avoid
How we help with performance
Frequently asked questions
Will conditional loading break payments?
Not if the SDK loads everywhere it is needed — test express checkout buttons carefully.
What is a performance budget?
A limit on script weight or requests per page that new tags must fit within.
Can you audit our scripts?
Yes.