-
Notifications
You must be signed in to change notification settings - Fork 35
Optimize render-blocking JavaScript and CSS in above-the-flow Content: #47
Comments
Yes, ideally we would use ResourceLoader (see #46), but it has an issue with media queries (the bits of CSS that can change the layout of the page based on things like browser window size, etc.). Getting ResourceLoader working with media queries would optimize this. |
keywords |
The ResourceLoader supports media-queries. You just need to make the path to your resources a key to an array containing a 'mediawiki.skinning.elements' => array(
'styles' => array(
'resources/src/mediawiki.skinning/elements.css' => array( 'media' => 'screen' ),
),
) There isn't much documentation about this (although Manual:$wgResourceModules has a little) — you're better just looking in the aforementioned file for examples. Beware, though, I had some trouble with the ResourceLoader a while back "sanitizing" some |
We read online somewhere then combine all of the .css source code from each of the .css sources into one .css file served <style type="text/css">. |
From: Google Developers PageSpeed Insights
Is there a way to reduce the additional serverround-trips to further reduce Page load times?
references:
https://developers.google.com/speed/docs/insights/BlockingJS
https://developers.google.com/speed/docs/insights/OptimizeCSSDelivery
The text was updated successfully, but these errors were encountered: