browser caching of static assets passes in gtmetrix but not in webpagetest
|
11-23-2015, 03:44 AM
Post: #1
|
|||
|
|||
browser caching of static assets passes in gtmetrix but not in webpagetest
I see this result in webpagetest.org (truncated for brevity)
FAILED - (No max-age or expires) - http://thewinegod.com/wp-gdb-content/the...ive.min.js FAILED - (No max-age or expires) - http://thewinegod.com/wp-gdb-content/the...rtfolio.js FAILED - (No max-age or expires) - http://thewinegod.com/wp-gdb-content/plu...tyPhoto.js FAILED - (No max-age or expires) - http://thewinegod.com/wp-gdb-content/the.../custom.js FAILED - (No max-age or expires) - http://thewinegod.com/wp-gdb-content/plu...r_front.js I know for a fact that browser caching has been enabled ok for the site as gtmetrix and PageSpeed Insights essentially show no problems for these files. Is this a webpagetest.org bug or something I'm missing |
|||
01-05-2016, 11:39 AM
Post: #2
|
|||
|
|||
RE: browser caching of static assets passes in gtmetrix but not in webpagetest
I have the same probem. Webpagetest reports the following:
Quote:FAILED - (No max-age or expires) - http://websitetechnology.com.au/wp-conte...s-logo.png Chrome developer tools shows the following in the response headers for https://websitetechnology.com.au/wp-cont...k-logo.png Code: accept-ranges:bytes |
|||
01-06-2016, 03:11 AM
Post: #3
|
|||
|
|||
RE: browser caching of static assets passes in gtmetrix but not in webpagetest
Do you have links to the actual test results? The headers should be available there as well.
|
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)