Page load time & server usage of Olimometer

I’m aware that the plugin causes the P3 test to flag up the Olimometer as a resource hog, but I’m not entirely convinced it is accurate. I have been through the code in the past and optimised it slightly, but given the way it works there wasn’t a lot I could do. It needs to dynamically create an image on every page load containing it, so that involves reading in the WordPress API, loading other images and fonts, processing them, then outputting as a new image.

I’ll take another look over the next couple of weeks and see what I can come up with. The only idea I have at the moment is an option to cache the image so as it only actually updates itself once in every ‘x’ number of refreshes. It does mean the image won’t always be up to date though.

It sounds like you’re saying that the image creation is what is causing the plugin to take so long to load. If you simply got rid of the dependency on the GD library and created the image using CSS3 then not only would it drastically reduce load time, but it would also be much more flexible. CSS is the way to go.

(See this plugin as an example: Progress Bar)