Plugin takes a big chunk of runtime according to P3

Good question, EWWW IO has always been heavy on the admin side, but I had done quite a bit of work to slim it down as much as possible. I’ll have to see what can be done.

Thanks! either way, solid plugin you have here. Keep it up!

Same here. Any ideas? I am also using your cloud service.

https://tinypic.com/r/e9z1og/8
https://tinypic.com/r/2wqziio/8

Thanks!

tyler, are you using the cloud version of the plugin? If not, I would switch (it will keep all your existing settings).

Yes, I am using your cloud version – I hope I am using it correctly; I have watched your videos and so on. I purchased 4,000 slots and am using around 3,200. My website is https://www.Philly-Sales.com.

Am I doing something incorrectly?

https://tinypic.com/r/2iuoxo8/8
https://tinypic.com/r/2n9hsu8/8
https://tinypic.com/r/2vboojb/8
Thanks!

I’ve never profiled the cloud-only version, but it should be very fast, so something is not right there. I’ll try it on my dev server and see what I get.

Thanks! Please keep me updated.

I don’t get anything close to that, but what could be happening (even for @dragonaut), is if you have plugins that are dynamically generating images every time the page is loaded instead of caching those images to disk.

P3 (the plugin profiler) used to do separate tests for front-end, and admin-side, and I thought the results you were showing were from the admin side. EWWW IO will have zero impact on the front-end load times unless it is being called to optimize images. This should only ever happen once for each image, unless you have another plugin that is misbehaving (not caching generated resizes).

So the way it should work is that, after posting a new photo or article, you might see one slow page load while EWWW IO optimizes new images (if you are not just using the resizes already generated by wordpress). After that, EWWW IO should not even be noticeable.