Current time: 12-18-2017, 04:59 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Optimisation suggestions
01-12-2017, 06:43 AM
Post: #1
Optimisation suggestions
Test results here: https://www.webpagetest.org/result/17011...1/details/

What would you say would would improve the performance of pageload time for this test result?
Find all posts by this user
Quote this message in a reply
01-13-2017, 04:04 AM
Post: #2
RE: Optimisation suggestions
What metric are you looking to optimize? The RUM first paint has fired at 1.29s. So important things load up fast.

There is a huge 3rd party burden: http://requestmap.webperf.tools/render/1...ea12cf8e41

However, it would be a longer conversation since it could be driving revenue. So this is not a very straight forward issue of fixing the issue but a deeper conversation on what tags matter and what can be removed or deferred.

Follow me on twitter: @rakshay
Visit this user's website Find all posts by this user
Quote this message in a reply
01-13-2017, 08:09 PM
Post: #3
RE: Optimisation suggestions
Thanks. Yes 3rd party scripts are big and agree separate conversation, although I think any 3rd parties can be deferred until after domContentLoaded.

I'm interested in reducing domInteractive and domContentLoaded. Is there anything specific there that would help? So the 1st party parts are as optimised as possible while the 3rd party scripts work is ongoing. Also, fonts is there a better way to load?
Find all posts by this user
Quote this message in a reply
01-31-2017, 12:39 AM
Post: #4
RE: Optimisation suggestions
Hmm, you have to break it down piece by piece and do something about the parts that are taking to much time. As a start I would do what you already mentioned, reduce domInteractive.
Find all posts by this user
Quote this message in a reply
01-31-2017, 05:46 AM
Post: #5
RE: Optimisation suggestions
Optimization 1
In your critical render path (requests 1-22, colored green in "Request Details" section for run 7), there are 5 3rd party domain names. Is it possible to move the code over to your primary independent.co.uk domain?

  1. ak.sail-horizon.com
  2. code.jquery.com
  3. sc.independent.co.uk
  4. stag.mdotlabs.com
  5. tags.bkrtx.com

For example, you are connecting to code.jquery.com just for the latest Jquery script. You could copy it over to your static domain and reduce one extra domain lookup+connection.

Optimization 2
You are using preload resource hint for the fonts. This is good for FF and Chrome. If optimization#1 is not possible, you could add a preconnect hint for the 3rd party domains. This should reduce a little bit of time in loading of the resources. You would need to preconnect to the tags in critical path - so this would be following domains:
  • ak.sail-horizon.com
  • code.jquery.com
  • sc.independent.co.uk
  • stag.mdotlabs.com
  • tags.bkrtx.com
  • static.independent.co.uk

General Optimizations
You could consider the following for long term changes:
  1. Combine the JS and CSS to reduce round trips
  2. Move site to HTTPs and then turn on HTTP/2
  3. Enable gzip compression across all resources - and ask 3rd parties to compress as well.

Hope this helps.

Follow me on twitter: @rakshay
Visit this user's website Find all posts by this user
Quote this message in a reply
02-01-2017, 06:11 PM
Post: #6
RE: Optimisation suggestions
(01-31-2017 05:46 AM)akshayranganath Wrote:  Optimization 1
In your critical render path (requests 1-22, colored green in "Request Details" section for run 7), there are 5 3rd party domain names. Is it possible to move the code over to your primary independent.co.uk domain?

  1. ak.sail-horizon.com
  2. code.jquery.com
  3. sc.independent.co.uk
  4. stag.mdotlabs.com
  5. tags.bkrtx.com

For example, you are connecting to code.jquery.com just for the latest Jquery script. You could copy it over to your static domain and reduce one extra domain lookup+connection.

Optimization 2
You are using preload resource hint for the fonts. This is good for FF and Chrome. If optimization#1 is not possible, you could add a preconnect hint for the 3rd party domains. This should reduce a little bit of time in loading of the resources. You would need to preconnect to the tags in critical path - so this would be following domains:
  • ak.sail-horizon.com
  • code.jquery.com
  • sc.independent.co.uk
  • stag.mdotlabs.com
  • tags.bkrtx.com
  • static.independent.co.uk

General Optimizations
You could consider the following for long term changes:
  1. Combine the JS and CSS to reduce round trips
  2. Move site to HTTPs and then turn on HTTP/2
  3. Enable gzip compression across all resources - and ask 3rd parties to compress as well.

Hope this helps.

I would say the second method is probably more advisable for this situation.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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