Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi @jmslbam,
    I can see those styles are still present even without Hummingbird. Please check for the inline styles with ID wprmenu.css-inline-css. Hummingbird will adjust the ID’s, to track proper groups of files. That’s why it might look like it’s coming from Hummingbird.

    In terms of combining. The Asset Optimization engine will use a smart algorithm to combine assets. It won’t combine all the files, only those that have matching attributes. For example, if a CSS will only load on IE or on screens larger than 1280px, and the other one loads everywhere, these two files will not be combined. We do this for two reasons – first of all, this reduces errors and style breaks, and second of all, on HTTP/2 combining is not the recommended approach, because loading multiple smaller files should be faster than loading a single large file.

    Best regards,
    Anton

    Thread Starter jmslbam

    (@jmslbam)

    Hi Anton,

    Thank you for you quick reply. If had a release of a other big project so my focus was there the last days, sorry.

    The Asset Optimization logic
    Thank you for your explaination. It’s indeed not necessary to combine everything to 1 files, especially with HTTP/2.

    About the styles
    Correct, the styles are still there, but now only once, and not repeated for every enqueued CSS file. That is the reason I disable the assets optimization of HB.

    Kinds regards,

    Jaime!

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

The topic ‘Repeated inline css’ is closed to new replies.