Hey @Ethan
Thanks again for flipping the WebP switch back on for us. Really appreciate the swift action on your part!
I wanted to circle back on the PageSpeed Insights report we mentioned: https://pagespeed.web.dev/analysis/https-www-discovernauts-com-en-travel-guides-tours-ricks-cafe-negril/68clkhwxt9?form_factor=mobile It does a great job of highlighting the double-loading issue with our hero image and its impact on site performance. This isn't just a minor hiccup; it's something that's genuinely affecting our user experience and metrics. There will never be an advantage in site speed by loading a hero image twice, especially not on mobile.
The thing is, this WebP feature and how it's applied across our sites isn't something that can be toggled on a per-site basis under one account. It's an all-in scenario, meaning if it's off for one site, it's off for all. This is crucial because it means the issue we're facing isn't isolated; it's affecting all our projects under this account. Means also when webP is turned on it is turned on for all sites within account. That works independently of LEAP itself.
Now that webP is turned on again for both sites (which is good and needed), the issue of duplicate loading is back on both sites:
For https://www.discovernauts.com/en/travel-guides/tours/ricks-cafe-negril/
For https://staging.theworldtravelindex.com/en/asia/thailand/ (our dev environment)
Also we tried to disable these options to see whether this would help to not load hero images above the fold twice, but no luck:
Given the technical nature of this, and understanding that it might not be in your wheelhouse to fix this directly, could we possibly get the technical team looped in on this? After a few days of back-and-forth, it's clear we need their expertise to dive into this and help us find a solution. The PageSpeed report and all the screenshots should give them a good starting point, and from there, they can hopefully address the double-loading problem across all sites.
I'm not trying to push this back onto your plate – I just believe getting the technical team involved is our best bet for getting this sorted efficiently. If you could forward this issue to them with a note about our discussions and the PageSpeed Insights findings and the screenshots, that would be fantastic.
Thanks a ton for your understanding and for helping us navigate this. Looking forward to getting this resolved with the tech team's help.
Tom