Move CSS to inline – no html optimization?!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Scott Hartley

    (@destac)

    9 years, 7 months ago

    This might be a design issue but a quick note is you shouldn’t be inlining all the CSS in this case you are hurting the actual load time. You would be better of taking it all into a single file.

    Thread Starter Mirko

    (@miwalter)

    9 years, 7 months ago

    Thanks! I’m currently testing out, if the pageloadtime (and scores on the multiple performance measuring services… it’s like an addiction sometimes *g*) will decrease if I inline the main stylesheet into the page itself. But I think you are right, so far this does not seem to be a good idea.

    Plugin Author Frank Goossens

    (@futtta)

    9 years, 7 months ago

    the reason why this might be happening is also the reason why inlining all CSS is probably not a good idea; your aggregated CSS is approx. 1MB (as a result of which it’s not impossible the HTML optimizer chokes when all of that is inlined).

    best result would be to choose “inline & defer CSS”, although it’s not the easiest of approaches. have a look at the FAQ for more info on how to do that.

    hope this clarifies,
    frank

    Thread Starter Mirko

    (@miwalter)

    9 years, 7 months ago

    Thanks for clarifying!

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

The topic ‘Move CSS to inline – no html optimization?!’ is closed to new replies.