"- Don't use question marks in a resource URL (.css?v=234)"
why? if you get the cache headers right, this is the way to go to let it cache forever. that's a nice thing.
(i don't really get why they do not use a caching proxy in front, there even is a wordpress plugin for varnish, so wordpress behind a caching proxy does not suck that much.)
unfortunately some suggestions are not possible with wordpress, so that alone could be a thing worth replacing.
Comments
You missed:
- Write compact efficient CSS (arguably the current CSS file is far too big)
- Combine all CSS files
- Don't use question marks in a resource URL (.css?v=234)
- Write valid compact efficient HTML (duplicate meta tags like: ICBM, unnecessary tags like Google verify, inline CSS, depricated HTML: align="left")
- Dont use spacer divs (div clear="all" style="padding-top: 5px") for a better render flow
- Delay loading javascript to the body of your site.
- Combine javascript files
- Compress javascript and CSS files.
- asynchronous loading of web fonts and analytics code.
- Load all CSS files before JS files.
For the unoptimized 1000 images you can use a Wordpress plugin or roll your own batch script.
"- Don't use question marks in a resource URL (.css?v=234)"
why? if you get the cache headers right, this is the way to go to let it cache forever. that's a nice thing.
(i don't really get why they do not use a caching proxy in front, there even is a wordpress plugin for varnish, so wordpress behind a caching proxy does not suck that much.)
unfortunately some suggestions are not possible with wordpress, so that alone could be a thing worth replacing.