Recommended when site testing at gtmetrix PgSpd 98 YSlow 94
Resources with a “?” in the URL are not cached by some proxy caching servers. Remove the query string and encode the parameters into the URL for the following resources:
(1) http://www.xxxxxxxxxxx.com/wp-content/themes/vantage/fontawesome/font/fontawesome-webfont.woff?v=3.2.1
(2) http://www.xxxxxxxxxxx.com/wp-content/themes/vantage/icons/vantage-icons.woff?-9o183q
________________________________________________________________
124.2KiB of JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering.
(1) http://www.xxxxxxxxxx.com/wp-content/cache/minify/000000/dY1bFoJADEM3xFg9rKhCxOJ0BqfltXtF_eLgX9PcJDX1zxFlrerfEVS6wo6TSqou5Nk5xjVcc36gJTaDG_W2M97kPIRmNM-KEgomwWxHv-pMEyfnDlvLd_N0i1gsSovymT1ExCdp7a_vdyiCsqQdMhSojEpYvLAR97yEJqsi-U5twRc.js (121.4KiB)
(2) http://www.xxxxxxxxx.com/wp-content/cache/minify/000000/M9AvS8wrSUxP1S8oSs3NLM3VT60oKUos1s_NT8rMSc1LLNPPQuLo5WbmAQA.js (2.2KiB)
(3) http://www.xxxxxxxxxx.com/ (540B of inline JavaScript)
_____________________________________________________________
The following resources are missing a cache validator. Resources that do not specify a cache validator cannot be refreshed efficiently. Specify a Last-Modified or ETag header to enable cache validation for the following resources:
(1) http://fonts.googleapis.com/css?family=Autour+One:400|Voltaire:400|Oldenburg:400
_____________________________________________________________
Please point me in the right direction, and if at all within my abilities i will attend to matter. Unsure about these as i dont if these are something i have access to repair. the other issues i fixed throughout the day and brought several items that were 60 …to 99 and 100s.
After GT test i am going to assure mobile testing, but so far looking fine !
Hi oldasdirtuser
Glad to hear you’re making progress and getting your site ready to roll.
We’re keen to help out wherever possible. The items you’ve highlighted here go to the core of Vantage and how’s its been put together. It’s potentially possible to re-work these elements but it’s unfortunately outside the scope we can help with right now. Here is an overview of what’s going on, perhaps you’ll find it helpful.
1. The first item you mentioned, Font Awesome, to resolve that you’d need to use a child theme, “deregister” Font Awesome and then re-register it without the “?” in the url.
2. Similar to point 1.
1, 2, 3: These items are potentially all coming from a caching plugin. Item 3 in that list…Vantage doesn’t output any inline JS so that’s potentially coming from a plugin.
1, final point: Not sure here, that’s super standard way of loading a Google Font. The top answer here: http://stackoverflow.com/questions/17382333/cache-validator-for-google-webfonts seems to go over why this can’t be done with Google Fonts, perhaps check it out.
!! Thanks Andrew !!!
(closed thread – issues identified)
Thanks for your understanding here, much appreciated.