Current time: 08-09-2020, 10:15 PM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Despite caching code, Cache Static Content gets F
07-23-2013, 10:59 PM
Post: #6
RE: Despite caching code, Cache Static Content gets F
You're not going to be able to do anything about 3rd-party content on your page (well, at least while keeping the content) unless you reach out to them. For most of the Google images I wouldn't worry about it - those are very small differences and there's a good chance they are already in user's browser caches from other sites.

Looking at the waterfall, I have a few suggestions that will probably get you bigger gains:

1 - instead of you should use // for including jquery. That will get rid of the ssl negotaition time

2 - You're loading 2 versions of jquery (1.7.2 and 1.8). You should eliminate one of those.

The javascript in general could use a lot of love. There are a lot of blocking scripts and widgets that should be able to be moved or made async (like the google search box for example). You want the browser to be able to parse and render as much of you html as possible before it has to execute any script. You can leave most of the async widgets in place but it would help your rendering a lot of you moved all of the blocking script work to the end of the page.

If you look at the filmstrip you can see that most of the page doesn't render until near the end of the loading: and that's because of the blocking scripts. Fixing those would get your content rendering closer to 0.4s instead of 2s.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: Despite caching code, Cache Static Content gets F - pmeenan - 07-23-2013 10:59 PM

Forum Jump:

User(s) browsing this thread: 1 Guest(s)