WebPagetest Forums

Full Version: Website converted to HTML5
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
We have updated our website to a new responsive design. We hope to launch our newly updated website sometime this week.
The test results seem ok.
See here: http://www.webpagetest.org/result/150825_YK_17NX/

The question is:
What if anything would you do to make this site load any faster?
Thank you for your time.
Brian...
Could I answer a broader question... What would I do with this site?

- TTFB of 1.3s indicates potential infrastructure tuning problems, especially considering pagespeed is enabled.
- you're running pagespeed, look at the sprite support to lower the file count
- you're using nginx, which makes it really simple to enable SPDY
- If running SPDY, then deliver as many external resources ( jquery for example ) from your server
- try deferring .js and .css to get the site displaying faster
- validator.w3.org reports over 300 errors on the home page
- rename your cdn to a domain-specific URL ( will need a wildcard cert, or dumping the cdn altogether if you run SPDY. This is no big deal as the page isn't big, and your expires headers are well set )

( these last 2 - plus fixing https - are really important to google )

Sizewise the page is great ( although the menu is a bit off looking at it through firefox, and the add to cart button has no text on it ), and https is broken for the home page ( http://allfont.net/cache/css/arial-narrow.css is loaded ).

SSL wise, you could use a more complex DH key and you could improve on selected ciphers, but that's just nitpicking.
(08-26-2015 04:21 PM)GreenGecko Wrote: [ -> ]Could I answer a broader question... What would I do with this site?

- TTFB of 1.3s indicates potential infrastructure tuning problems, especially considering pagespeed is enabled.
- you're running pagespeed, look at the sprite support to lower the file count
- you're using nginx, which makes it really simple to enable SPDY
- If running SPDY, then deliver as many external resources ( jquery for example ) from your server
- try deferring .js and .css to get the site displaying faster
- validator.w3.org reports over 300 errors on the home page
- rename your cdn to a domain-specific URL ( will need a wildcard cert, or dumping the cdn altogether if you run SPDY. This is no big deal as the page isn't big, and your expires headers are well set )

( these last 2 - plus fixing https - are really important to google )

Sizewise the page is great ( although the menu is a bit off looking at it through firefox, and the add to cart button has no text on it ), and https is broken for the home page ( http://allfont.net/cache/css/arial-narrow.css is loaded ).

SSL wise, you could use a more complex DH key and you could improve on selected ciphers, but that's just nitpicking.
Thank you so much. I will work on the issues you pointed out.
Reference URL's