Utalize http/2
-
Consider not grouping css files to utilise http/2.
Grab all css and inline css and async. Instead of grouping adding inline to it’s own css file and async all.
-
The HTTP2 thing is a matter of debate honestly that I have done research on as well as I have wanted to try to make use of prefetching/preloading related stuff as well. However a talk by an engineer at fastly, https://www.youtube.com/watch?v=cznVISavm-k, has shown while it helps, it doesn’t actually solve the root issues.
I do understand there may be cases where having a handful of CSS files might be better than one. However, at this time the plugin is designed to be a drop-in replacement and silent, so even if I added a “mode” for that would have to use an existing rocket option without adding my own settings page which I want to avoid.
So I am not closed to this, but it is not in any near plans to work on this.
I appreciate your feedback so far though 🙂
Surely is, but that’s why you should give me the option to decide or test. Now I’m forced into one big file.
I see increase loading times when loading the files combined.
You could add a helper function or hook to alter this? Since I also end up with loading unused css files on pages where this css is not used.
Thanks, I appreciate the plugins, just some FOUC I try to solve without a js preloader and plugin, just CSS. Together with some feedback and thoughts of improvements.
Would look forward to improvements to this or just busy at the moment? Async and Defer are not the same, and the issue is not all scripts can be asynced. In my case async works which is strange since defer is usually safer:
For example, in cases where a second script depends upon the first script (e.g. your second script uses the jQuery loaded in the first script), then you can’t make them async without additional code to control execution order, but you can make them defer because defer scripts will still be executed in order, just not until after the document has been parsed.
I am not against having improvements but changing how things behave to be multiple files would require a lot of thought, as that’s foundational code. My efforts so far are also mainly due to my own client’s needs or a need of my own. So in regards to priorities, this is not on my roadmap so-to-speak right now.
If you find a place however that you would like 1+ hooks to be added to modify behavior, that is doable. I will say the last 5 versions I think got the minify and processing of CSS separated such you CAN go and hook into do other things, https://github.com/pcfreak30/rocket-async-css/blob/master/lib/Rocket/Async/CSS.php#L808.
And I do understand
async
vsdefer
. I also have hit issues with async and race conditions I have had to solve in the JS plugin.For FOUC, you can use wp critical css.
Thanks.
I am not against having improvements but changing how things behave to be multiple files would require a lot of thought, as that’s foundational code. My efforts so far are also mainly due to my own client’s needs or a need of my own. So in regards to priorities, this is not on my roadmap so-to-speak right now.
Understand it’s a free plugin after all 🙂 But would be nice to see improvements but fully understandable.
If you find a place however that you would like 1+ hooks to be added to modify behavior, that is doable. I will say the last 5 versions I think got the minify and processing of CSS separated such you CAN go and hook into do other things, https://github.com/pcfreak30/rocket-async-css/blob/master/lib/Rocket/Async/CSS.php#L808.
If we easily could just listen to wp rocket settings here? Inline css and js become it’s individual file meaning 1 more css file and 1 more js file.
Would that be doable?
And I do understand async vs defer. I also have hit issues with async and race conditions I have had to solve in the JS plugin.
Found some issues with the async and your plugin as well but might be issues in js code from other side of course. Mainly on modal jquery and anchor links off-set jquery fix.
For FOUC, you can use wp critical css.
Using wp rockets should be enough, but do still FOUC the svg inlined icons that displays.
If we easily could just listen to wp rocket settings here? Inline css and js become its individual file meaning 1 more CSS file and 1 more js file.
Even if I did it would mean just using that to change behaviors for code that does not exist currently as most of the code in CSS.php if for minification and data processing. The hook idea was to allow you/others to do the changes you might want yourself until such time this may be implemented.
but do still FOUC the svg inlined icons that displays.
I have seen this. Generally the trick there is to define css in the head that would set a width/height on all SVG tags (it is a huge size before full CSS loads).
Using wp rockets should be enough, but do still FOUC the svg inlined icons that displays.
I am biased since it’s my critical css plugin, but I also believe the paid service allows more control than wp-rockets free service.
- The topic ‘Utalize http/2’ is closed to new replies.