Hi,
First, this plug-in is soooooooooo useful! I love it. It has helped me out no-end. Thank you for producing it.
Second, as a follow-up to this thread:
I run my site through Pingdom to check page speed. It produces a nice little ‘waterfall’ graph of everything that the page requests and the load times for each item.
I have close to 30 plug-ins installed. Of them all, WP Add Custom CSS takes by far the longest to deliver its payload.
As an example, here’s a list of total wait times:
The theme (style.css?ver=4.3.1) 87 ms
Rapidology (style.css?ver=4.3.1) 63 ms
ShockSpots (front.css?ver=112) 69 ms
AssociateGoliath (post.css?ver=20151129091707) 68 ms
ShortCodes Ultimate (box-shortcodes.css?ver=4.9.9) 77 ms
There are more but these are typical. No other plugin shows times markedly different from the above, except:
WP Add Custom CSS (?display_custom_css=css&ver=4.3.1) 760 ms
So just like the OP, WP Add Custom CSS seems to be showing huge load times: 10 x longer than all others.
One thing I’ve noticed (and I’m not a plugin developer, so I can’t be sure I’m understand this correctly or be sure it is significant) is that yours is the only URL that I have installed to use a URL parameter immediately after the website’s domain name to obtain its CSS.
I’m guessing that this is because you are calling plugin code to query the database to dynamically obtain the CSS rather than referencing a saved, fixed file. (Or am I talking rubbish?!)
If I’m right, would it explain the 10 x longer issue?
Could the plugin be written to write a fixed file using a unique ID every time it is changed? (Caching)
Please understand that I am not a plugin developer so I appreciate that I could be talking utter tosh! Or going against WordPress programming standards. I’m just adding to this thread as I, too, have noticed this issue and would love for it to be truly resolved.
Thanks.
James
PS I don’t understand why all plugins seem to add the ?ver param to the end of their URLs. Doesn’t this prevent caching and slow them all down?