Very good, but extremely resource hungry

Hi Nick,

Is the slowness problem just in the editor or also when viewing/previewing the post? When viewing the post, the block should fall back to a static image if the browser being used doesn’t have hardware acceleration (or JavaScript) enabled. The same fallback is not applied in the editor so you are still able to see some animation (even if degraded) when editing.

Unfortunately the nature of this block, using WebGL, is going to make it more resource intensive than most blocks. If your device does have hardware acceleration enabled and it’s still slow, something that may improve it slightly is using a smaller complexity and limiting to using only one waves block per page.

I’d also like to try to optimize the code more. If you’re able to share the version of the operating system, the version of the browser, and what sort of device hardware (CPU/GPU or year/model of computer) you are using, I may be able to adjust some things to make it work better. Thank you!

Hi Alex,

Intel i7 U5500, 4GB Ram, Win 7 Pro, descent but not great onboard Graphics card, 2011 Acer brand laptop. The slowness I was referring to was on the video I had in a Cover block, and it was not too bad, but that said, I can see the performance becoming a huge issue with mobile devices, and slower cheaper computers. I tested it using my localserver, and never went live on the internet, so I did not check the prformance with my phone or even my Chromebook.

BTW, I use a yahoo email, so I don’t get emails from this site, so if you want more interactions/feedback, feel free to email me… or even maybe better, message me on Slack.