Some Suggestions

  • AJ @ WpFASTER.org

    (@ajm_1976)


    11 years, 3 months ago

    Hi!

    We have our own solution for inlining critical CSS, but I did test drive the plugin as it would be nice to be able to manage inlining critical CSS by way of one.

    What I noticed is that it ultimately suffers the same drawback as Autoptimize’s “Inline and Defer” option, which is that there’s no (easy) way to override the globally applied block of CSS on a page-by-page, post-by-post basis. So, maybe that functionality could be added via an input field on each page/post.

    Also, this plugin does not aggregate style sheets nor does it aggregate and defer non-critical blocks of CSS such as customizer-css-output. Which are things Autoptimize does do.

    Lastly, there are myriad instances in which people will want to make use of W3TC for everything but minification, Autoptimize for JS and HTML, and perhaps now (or in the future) your plugin for inline CSS. But, at least on the setup on which I tested this triad, your plugin doesn’t cooperate. The combination of W3TC and Autoptimize, on the other hand, works great so long as one isn’t attempting to minify/concatenate the same things with both.

    Anyway, just some suggestions and thank you very much for attempting to solve the “Above the Fold” conundrum via a plugin!

    Best,
    AJ

    https://ww.wp.xz.cn/plugins/above-the-fold-optimization/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author optimalisatie

    (@optimalisatie)

    11 years, 3 months ago

    Hi AJ!

    Thanks a lot for the suggestions! I will consider the page-based-configuration. I will actively use the plugin in optimization service and improve it further. Perhaps I will find a way to automate the Critical Path generation process or integrate a WYSIWYG generator within WordPress.

    Can you perhaps provide an example of a website where page based configuration is required to achieve a higher PageSpeed score?

    Regarding aggregation, the plugin is meant to be simple and light weight and to work next to other optimization plugins that for example handle aggregation. The only thing the plugin (optionally) does is optimize the delivery of CSS files by loading the files asynchronously via a modified version of LoadCSS that includes the CSS via Window.requestAnimationFrame().

    When using the minification function of W3 Total Cache the plugin will optimize the delivery of the minified CSS files. It should work with any other aggregation plugin.

    The plugin does not yet touch inline CSS blocks. I will consider the suggestion, however, perhaps it is better to handle it via an other plugin.

    Regarding the usage of W3 Total Cache + Autoptimize + this plugin, can you please provide details about the problems you experienced?

    [ Signature moderated ]

    • This reply was modified 9 years, 4 months ago by Jan Dembowski.
    Thread Starter AJ @ WpFASTER.org

    (@ajm_1976)

    11 years, 3 months ago

    Hi Optimalisatie.nl,

    Can you perhaps provide an example of a website where page based configuration is required to achieve a higher PageSpeed score?

    Well, a higher PageSpeed score and optimal critical path rendering ride the line of being mutually exclusive. Setting aside the ubiquitous false-positives and bugs of the PageSpeed tool, what I’m specifically interested in is actual, real optimization of the critical rendering path when the critical CSS differs on different pages/posts.

    For aesthetically redundant instances, a globally applied block of above-the-fold CSS can be applied and still render each page optimally (Smashing Magazine is a good example of this). However, in aesthetically ‘diverse’ instances, there is a need for more granular control (our website, as one example: note that different blocks of inline CSS are applied to every main page; then, a block applied globally to blog posts). 90%+ of the sites we work on require such granularity for optimal rendering/UX.

    Regarding aggregation, the plugin is meant to be simple and light weight and to work next to other optimization plugins that for example handle aggregation. The only thing the plugin (optionally) does is optimize the delivery of CSS files by loading the files asynchronously via a modified version of LoadCSS that includes the CSS via Window.requestAnimationFrame().

    When using the minification function of W3 Total Cache the plugin will optimize the delivery of the minified CSS files. It should work with any other aggregation plugin.

    Ah, okay. So you’re saying that this plugin does/should be making use of the combined W3TC (or Autoptimize) CSS file, yes? If I recall correctly, the problem I was having is that it wasn’t, at least not when using Autoptimize for aggregation/concatenation: the combined (Autoptimized) CSS file was still appearing at the top of the HTML with your plugin including the globally applied, inlined CSS as well as each individual CSS file via Window.requestAnimationFrame() at the bottom. I didn’t experiment with W3TC as we generally don’t use it for minification since it too does not aggregate inline scripts or inline CSS output by plugins.

    You may wish to construct your own instance and scenarios with these three plugins, though, to get your own eyes on the conflicts (potential or otherwise) as my experiment was very basic.

    Best!
    AJ

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Some Suggestions’ is closed to new replies.