Securely inlining is a lot of effort though, compared to adding a HTTP header to trigger HTTP 2.0 push.Whether it's comparable in performance as inlining doesn't really factor into whether the Insight checks should rate it as bad as not HTTP pushing it, as it's clearly much better than doing nothing.
--
You received this message because you are subscribed to the Google Groups "pagespeed-insights-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pagespeed-insights-discuss+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pagespeed-insights-discuss/0cac03df-f72f-41a2-a204-6b4df492d2d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Actually it is not at all clear that http push is better than doing nothing. If you push a non-critical resource you may slow delivery of critical resources when bandwidth is limited.The main question for me is whether/how you have partitioned critical vs non-critical css.
Second question is how to deliver critical CSS: inlining and h2 push are both options with since pros and cons. IMO h2 push wins if the h2 server or proxy attempt to model the browser cache and only push css to clients that don't already have it. Inlining wins otherwise and in particular when browsers or proxies don't support h2.
Third question is how to delay-load non-critical CSS. I am skeptical of solutions that don't involve both RAF and setTimeout. Loading css from end of body is not sufficient.
--
You received this message because you are subscribed to a topic in the Google Groups "pagespeed-insights-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pagespeed-insights-discuss/_diiYU73r8A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pagespeed-insights-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pagespeed-insights-discuss/9f607796-5043-4a0e-8bad-7508b3a6880b%40googlegroups.com.
You don't actually need to do the checks and avoid push to get the same network level benefit as CSS inlining, which would also send the same styles every request.I can see there might be some tiny performance benefits of inlining over it though, but this won't be anywhere near as significant as waiting for a 2nd request/response.Certainly clever logic to avoid the push when unneeded is worth points too though, but hard to achieve.
Hi,--
I don't see major problems loading the critical path CSS in an <style> node if you've access to the separate file.
Unless you're using an H2O http/2 server you would have to implement something to read user's cookies in order to know if you have to send him the resource or not.
While I see that H2 push will have benefits over inline, I do think that it is harder to implement properly.
El lunes, 7 de agosto de 2017, 6:36:06 (UTC+2), Andy Thompson escribió:Just to be clear, I wasn't meaning h2 pushing the full CSS content, only the critical path CSS as a separate file.Also I'm not saying this should replace the CSS inlining rule, only that it be another option. Both options don't have to be as good as each other.
You received this message because you are subscribed to a topic in the Google Groups "pagespeed-insights-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pagespeed-insights-discuss/_diiYU73r8A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pagespeed-insights-discuss+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pagespeed-insights-discuss/9f607796-5043-4a0e-8bad-7508b3a6880b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "pagespeed-insights-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pagespeed-insights-discuss+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pagespeed-insights-discuss/D3BC2B5F-B62D-4221-9C9F-C2DCF735DF01%40andytson.com.
To unsubscribe from this group and all its topics, send an email to pagespeed-insights-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pagespeed-insights-discuss/CAGKR%2BEAfoUm205%2BfGtQ8T%2B%2BF0pmkFu%3D9kPPbGrnjymG-PfR1mg%40mail.gmail.com.