I am close to Perfect A (What can i do Better ?)

I’ve made some fine tuning on my server.

  • Full IPV6 Support
  • Secured with https (Comodo)
  • Enabled Nginx(proxy) + Apache + memcached
  • Tuned nginx.cfg

Now my WebPage Test score is nice http://www.webpagetest.org/result/131121_5C_R0N/

What can I do more to get a Perfect A ?
Do you think that progressive image rendering is so important in my case or not ?

Thank you in advance for your answers !

Dear Dagalidis,

As you can see at http://www.webpagetest.org/result/131121_5C_R0N/1/performance_optimization/#progressive_jpeg, all you have to do in order to get an extra A is to optimize the images listed at the above mentioned link.

You should not worry too much though, loading time of your website is great.


Try not to focus too much on getting “straight A’s”.

There’s room for improvement, though. Images like palebrown.jpg should be converted to the PNG format. The JPG is 1.3KB, an optimized PNG can be 0.41KB. With 30+ of such images, you’ll easily shave off 20-30KB. If you can combine some of them into CSS sprites, savings are bigger as you’ll have fewer HTTP requests, which means less overhead and fewer connections, but be careful about retaining image quality if that’s of much importance. I put five of your JPGs (5 HTTP requests, total of ±6.5KB) into a PNG, effectively bringing that down to 1 HTTP request and a total of 2.5KB (about 0.5KB per pattern, so perhaps a little larger per pattern than the 0.41KB I mentioned earlier, but as long as there’s no HTTP/2.0, and you’re not using SPDY, cutting down on HTTP requests is worth it.

Thank you very much for your help.
I will try to use sprites and lower all http requests.
After all I think nginx + apache + memcache is a perfect combination for getting fast loads.

98-99% is a good goal.

I my opinion I think the grading penalty for not using progressive jpegs is weighed too heavily. while I have not yet tested my theory, it appears progressive jpegs improve the First Paint time but increase Document Complete or Fully Loaded.

The JS hosted on your site is not cached with max-age. Not a real issue as your expiration dates are far future. I prefer max-age because W3C states it takes precedence over expiration date. Implementing both would be best.

If you intend to have your site render on a mobile device you need to reduce HTTP requests.

Most of what needs to be done requires a a good working knowledge of PHP and CSS. Most of this work must be done in the Word Press content/themes PHP routines.

There is one place that will reap big payoff would be to eliminate any unused Background images in the CSS.

I assume the reason you have so many requests is due to background images in the CSS links.
Almost all the 16x16 images on this page could go into one sprite image.

There may be some problems in some Browsers with using tables and Background Image Sprites.
I would use elements to make a simple table replacement. I like the over

in many places because it defaults to both inline and block display attributes eliminating the need to use the widely unsupported display:inline-block. Replace the with and use a
in place of and remove the .

See the GTmetrix Page Speed implementation. It lists by priority all that is necessary to get an 100%. Although many times getting to 100% from 99% is just not worth the effort.