Comment on Google PageSpeed Insights Results by SEO Dave.

PageSpeed Insights If you look through the comments above yours I’ve described some of the Page Speed Insights issues you have in detail.

Let’s go through a few of your Google Page Speed Insights Tool Results Issues.

Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 7 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

My results

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

So I have 1 render blocking issue, you have 12.

Those 11 additional render blocking issues will be pulling your Page Speed down (most likely the biggest issue you have), your visitors have to download all 12 JS and CSS files BEFORE the main content will load (that’s what render blocking means). Fixing this Page Speed Insights Tool Issue should be very high priority.

Remove render-blocking JavaScript:


Do you notice anything about these issues? Five are part of one of the plugins you use which you think shouldn’t result in your Page Speed issues, I’m afraid it’s Nextgen Gallery plugin that’s causing most PageSpeed Insights Tool Issues. The other two Jquery issues are also because you use NextGen Gallery plugin (that plugin uses Jquery, Stallion Responsive by default doesn’t).

So all the above are caused by NextGen Gallery plugin.

Optimize CSS Delivery of the following:


Another two render-blocking issues for the NextGen Gallery plugin. Because you use the Nextgen plugin you have 9 render-blocking js/CSS files!

If you have disabled the plugin and rerun the Google Page Speed Insights test be aware the results are cached. Try running the test on another webpage of your site or wait for the cache to clear.

I’m afraid if you want the flashy image features that Nextgen offer, you’ll take a page speed hit.

There’s three render-blocking CSS files that’s part of Stallion Responsive, this can be reduced to one (can’t get below one) by using a plugin that combines and minifies CSS files. I use and recommend the W3 Total Cache plugin (it’s better SEO wise than WP Super Cache which you currently use), see other comments for settings to combine and minify these three files into one CSS file. You might be able to combine your NexGen plugin CSS files as well, you’ll need to test.

Can say you’ll probably have issues with combine and minify all those JS files (minifying js tends to be problematic, you might be able to combine them, unlikely to minify).

IF you can combine all the CSS files into one and all the JS files into one using the W3 Total Cache plugin you’ll be left with 2 render-blocking issues. Want to reduce it to one, disable the NextGen plugin.

Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 102.9KiB (65% reduction).


These are caused by a server setting. You might be able to fix these with the W3 Total Cache plugin, if not it’s a server setting to enable and setup Gzip or Deflate module correctly under your hosting account: can’t help you with this beyond advice what you are trying to achieve and possible issues.

Note there’s nothing wrong with the above files, this is a case of your server hasn’t compressed them. The fact they are all js files suggests you are lacking the right server rule for js files, I had the same issue even though W3 Total Cache has added the right rules into my .htaccess file (I don’t know why it didn’t work for me, might work for you) and had to add this to my servers httpd.conf file.

<IfModule mod_deflate.c>
# Force compression for mangled headers.
<IfModule mod_setenvif.c>
<IfModule mod_headers.c>
SetEnvIfNoCase ^(Accept-EncodXng|X-cept-Encoding|X{15}|~{15}|-{15})$ ^((gzip|deflate)\s*,?\s*)+|[X~-]{4,13}$ HAVE_Accept-Encoding
RequestHeader append Accept-Encoding "gzip,deflate" env=HAVE_Accept-Encoding
# Compress all output labelled with one of the following MIME-types
# (for Apache versions below 2.3.7, you don't need to enable `mod_filter`
# and can remove the `<IfModule mod_filter.c>` and `</IfModule>` lines
# as `AddOutputFilterByType` is still in the core directives).
<IfModule mod_filter.c>
AddOutputFilterByType DEFLATE application/atom+xml \
application/javascript \
application/json \
application/rss+xml \
application/ \
application/x-font-ttf \
application/x-web-app-manifest+json \
application/xhtml+xml \
application/xml \
font/opentype \
image/svg+xml \
image/x-icon \
text/javascript \
text/css \
text/html \
text/plain \
text/x-component \

You’d only need to go to your servers httpd.conf file if the W3 Total Cache .htaccess rules don’t work.

Since mod_deflate is working for other resources (CSS files etc…) suggests you are only missing the javascript rules from the above. You won’t need all the above, in your servers httpd.conf file you’ll find a set of rules like those above, you need to find these rules and make sure it includes:

application/javascript \


text/javascript \

I bet it’s the last one you are missing.

What these rules do is tell the Apache mod_deflate module which types of files to compress, W3 Total Cache adds something similar to the .htaccess file rules which worked for me other than some js files. This is what W3 Total Cache adds to your .htaccess file:

AddOutputFilterByType DEFLATE text/css text/x-component application/x-javascript application/javascript text/javascript text/x-js text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon application/json

application/javascript and text/javascript are both there, so should have worked.

Anyway, went off on a slight tangent there :-)

Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:


The first two issues are on your site, the other two are not on your site, so you have no control over them.

Leverage browser caching is another server setting. What you have here is it looks like images don’t have an expire date set,

W3 Total Cache should be able to set these. Been a while since I used WP Super Cache, but felt sure it could set expire headers, maybe you have turned an option of. WP Super Cache is a good performance plugin, W3 Total Cache is a really good performance plugin, it’s one of the few WordPress plugins I consider a must use WordPress SEO plugin.

If W3 Total Cache plugin didn’t exist I’d have to find/build multiple performance features to add to Stallion, can not overstate how important using W3 Total Cache is to gaining full WordPress SEO performance.

Going to skip Minify JavaScript, W3 Total Cache might be able to minify your JS files (minifying can break js files, ideally the plugin developer would minify their JS before release), again it’s NextGen Gallery plugin js files, tells you the developers haven’t minified their JS files, had Nextgen minified before release you wouldn’t have the Page Speed issue to fix.

Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1.3KiB (18% reduction).

You have one image that’s not optimized c1.jpg. That’s your custom header image, you can either use a plugin like EWWW Image Optimizer plugin and run it so it checks all your sites images, or optimize c1.jpg on your PC and upload again via FTP.

That’s pretty much all your Page Speed Insight issues. You can see most of them are the Nextgen Gallery plugin and a few server settings. If you turn off Nextgen and fix the server settings your Page Speed Insights results will be better than mine because you aren’t taking a hit with social media like buttons and Google Analytics.

Also see my comment about Using Asynchronous AdSense Ad Code, the default Stallion AdSense code can be improved upon.