[phxgigsParticipant]

it seems that if I could just get this fixed the site would load at a good speed. the error is
Eliminate render-blocking JavaScript and CSS in above-the-fold content how can this be fixed?

[phxgigsParticipant]

using the tool you listed (https://tools.pingdom.com) I see these errors. So how do we fix this?
f 25 Remove query strings from static resources
f 28 Specify a Vary: Accept-Encoding header

[phxgigsParticipant]

thx you for all your help and time. We are now at 98 of 100 on both cells, and desktops. Still those errors to fix if we can.
f 25 Remove query strings from static resources
f 28 Specify a Vary: Accept-Encoding header

look forward to your reply.

[phxgigsParticipant]

I was wrong, the plugin Cache Enabler was active and was producing a blank white page again, so had to turn that off and now the speed is back down to 69 of 100. dam I figured we had it. so bad to needing your help.

[RadModerator]

Hi there,

Before we continue, performances as a whole are affected by multiple plugins from different authors which we don’t have direct control and can affect the theme too. That score doesn’t mean your site is slow, it’s only set of standard that the tools suggest you to change. And that suggestion should be applied on all plugins and not just on the theme. There is no universal solution and you can’t tell each plugin’s author to do it that way, WordPress doesn’t work that way. Hence, there is a separate category of plugins that deals with optimization and caching. This is, to close the gap of modular features that comes from different authors.

I’ll try discussing this one by one 🙂 (According to page speed)

1. Reduce server response time : In our test, your server responded in 0.32 seconds.

I then checked it through Pingdom tools and confirmed that DNS is resolving by 450ms ( 0.45 seconds ). Since this is DNS related, then you have to contact your domain registrar. This is network part and not related to the theme, or WordPress, not even on your hosting.

2. Leverage browser caching

https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://maps.googleapis.com/maps/api/js?v=3&ver=4.6.1 (30 minutes)

These files are certainly not from the theme since they hosted outside your site. If it’s strict requirement, then google should do it on their map, they should always expect that their maps are embedded to the site they require leverage caching.

3. Minify CSS

Minifying http://www.arroyotransportation.com/…blic/assets/css/settings.css?ver=2.1.0.1 could save 2.5KiB (29% reduction) after compression.
Minifying http://www.arroyotransportation.com/…public/assets/css/settings.css?ver=5.2.6 could save 2.1KiB (28% reduction) after compression.

These are from bundled plugins, not part of the theme. Again, WordPress site is modular and the feature can be from different authors where the theme has no direct control. But optimization plugin should handle them, it’s their purpose. You should check your optimization plugin why they are skipping these files. They should handle the files regardless of plugins or theme.

Same goes for this

Minifying http://www.arroyotransportation.com/…public/assets/js/lightbox.js?ver=2.1.0.1 could save 2.7KiB (21% reduction) after compression.

Then while on Pingdom, there are the different set of suggestion compared to Google Page insight. It recommends that you should combine all CSS files into one CSS file. Same goes for javascript files. Again, you can’t do this since files are from different plugins with different authors, it’s not an issue caused by the theme. It’s how WordPress works, but again, there are optimization plugins or even hosting features that can fix this (not actually fixing since it’s not an issue, but the recommendation).

All those optimizations should be done by your plugin or any feature you’re utilizing to optimize your site.

4. Remove query strings from static resources

That’s how WordPress works, it adds version to the files. And it’s part of WordPress standard, but you can check it here https://wordpress.org/support/topic/remove-query-strings-from-static-resources-9/. Again, that only applies to resources that are loaded by WP Enqueue feature. If other resources aren’t affected by that (means they are static), then you’ll have to edit the coding manually (eg. plugin from the different author).

Please also note that some query strings have its own purpose, and removing them may affect what it’s doing. You may also check some topic of SEO Query strings, it may be affected as well.

5. Specify a Vary: Accept-Encoding header

Your optimization plugin or feature should do it too since they also require htaccess entries. But you can check it here http://stackoverflow.com/questions/3641197/how-to-specify-vary-accept-encoding-header-in-htaccess

———

As you’ll notice, those recommendations are not theme related. And you should be contacting your webmaster for optimization. The score only shows the grade but not the actual speed. If you’re more concern with loading speed, then what you should check is how long a single file or resource load through browser developer’s network tool, or Pingdom’s File requests logs and see which takes longer to load.

Thanks!

[Author]

Posts