Thai Cooking Phuket: Preserving a booking flow while cutting embed weight
Third-party booking retained via link, but heavyweight embed dependencies removed to reclaim performance budget for content and schema.
https://thaicookingphuket.com/ · Education — cooking classes · Published 5 February 2026
Challenge
The WP site loaded multiple third-party booking embeds, each carrying its own JavaScript bundle. Total blocking time was the site's dominant performance issue.
Audit
Performance profile confirmed embeds accounted for the majority of main-thread work. Booking conversion analytics showed users mostly clicked through to the provider's own booking page rather than completing in-embed — the embed weight was unpaid-for.
Implementation
Embeds removed; direct link to the booking provider retained on every experience page. Experience content re-authored in the repository as the source of truth. FAQ schema added where relevant.
Validation
Lighthouse mobile scores now consistently in the 90s. Booking click-throughs tracked as a GA4 conversion event. No regression in booking volume during the observation window.
Outcome
Faster site, cleaner schema, class content owned in-repo rather than only visible through a booking provider iframe.
Lessons learned
Embedded third-party UI is a hidden performance and ownership tax. When users mostly click through anyway, a direct link is the better contract.