soynomm / splendid-speed Goto Github PK

Much like the Inline CSS module, this would do the exact same, but for scripts.

Since the minimum target audience of this plugin starts with PHP7, there's a bunch of cool stuff to add to this plugin to leverage that.

Currently when Imagick is not supported, you can still toggle on and off WebP compression. It just won't do anything. It would be nicer to display a message instead of the toggle switch in such a case to make it clear why it's not doing anything.

Currently when doing development work (like adding new plugins that add CSS or editing the theme's CSS) with some of the features such as caching or inline css turned on, those new changes won't take effect until you turn those features on and off again in Splendid Speed. The problem here is the user probably doesn't even know he needs to do that, so an attempt to help with that I figure a toggle button for development and production mode would be useful.

When toggled to development mode, any feature that uses caching would be silently turned off.

I've recently changed my website address, which needs to be updated in this plugin.

This would help make sure that when the plugin or module is deactivated, we only remove the WebP images that we created. Sometimes the user might have their own WebP images and, currently, those would be deleted as well.

This happens because of how instant.page script is minified to use one-letter constants which will naturally clash with other scripts on the page.

Any CSS file that is @import-ed will not work with Inline CSS, because @import needs to precede any other CSS rule. This is breaking some sites I have tested.

A fix that I can think of would be to strip the entire CSS from @imports, and move them to the top.

Currently deferring is done with priority 10, so it's highly likely some plugins or themes will have scripts also loaded after that, which Splendid Speed then will not catch. Setting this to some impossibly high number would fix that.

As an addition to #1 it would be nice to check the theme's CSS files against the ones cached in Splendid Speed for Inline CSS, and if a change is detected then delete the cache. This would allow users to work on their themes with the plugin even in production mode and it would pick up on those changes.

While it's nice to have better metrics, I don't think it's worth giving users yet-another-notification for.