RoGuE_StreaK

Hi Jack, yes the "good" version has the animated HTML page loaded into an iframe in a div, it's a Shopify site so was quite limited to what he could do, and this way made it easier for me to make updates and just send him a new link, especially with a spritesheet etc needing to be imported. Most changeable settings like colours listed are dictated by external github files, so he can change stock without needing me to republish. The majority of graphics are deliberately vector, with some PNG overlays for textures, and those would be scaled on my phone; but I'll see if I can get an exact div size from the "good" site when it displays on my phone, and create a test holding page for the "standalone" version so that element is exactly the same for testing. For quite some time I was caching the dynamically coloured elements as bitmap and using easel to colour them, but in moving to v3 I finally figured out how to directly address the vector fills to tween or set their style values instead. This did improve performance on low-end devices, as did compressing the overlay PNG spritesheet with tinypng (actually that was more load time reduction) I didn't particularly think it was directly a GSAP issue as such, but thought perhaps someone here has come across the issue and/or know more about the various concerns that can impact how well animations perform.

Wondering if a knowledgeable person can figure out why, on my oldish android phone, my GSAP animations run extremely poorly when viewed standalone, but when embedded within the destination website they run perfectly smoothly?? Not particularly an issue as everyone else sees it via the site itself, but I can't understand why it's happening when it's the exact same page. Wanting to ensure you don't need the very latest phone to use the page smoothly, that any old device will work. It's developed within Animate CC (2018) (I'm an old Flash developer), with pretty-much everything being dynamically driven by GSAP v3.6; I haven't checked the latest offering to see if I need to change things to upgrade to v3.11 like I did when moving from v2. Over the years it's been heavily optimised and recoded, runs buttery smooth EXCEPT when I view it directly in a browser on my Moto G7 android. Have tested different browsers with the same result, very bad when standalone, smooth as silk when embedded. Runs fine standalone on my work iphone, and of course when viewed on a laptop etc. Here's the direct version https://baudalign.com/hp2023/board_selector_v233.html And here's the embedded version, sitting in a div which resizes to suit the browser viewing window height/width https://www.hpbodyboards.com/pages/visualise-your-custom As I said, it's not a big deal as it works for practically everyone, but I'm just at a loss as to why the exact same page runs very differently depending on whether it's standalone or embedded! So any help / thoughts / advice would be greatly appreciated.