cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3079
Views
5
Helpful
8
Replies
2 Accepted Solutions

Accepted Solutions

Philip D'Ath
VIP Alumni
VIP Alumni

I live in New Zealand, quite a distance from "HQ".  However we have excellent Internet connectivity.

When I run this page through Google Chrome audit I find it loads 127 elements.  127!

I see you are now using Cloudflare.  The audit shows CloudFlare took 16s (yes, 16 seconds) to deliver up the first page.  However this was unusually bad.  Usually it is much better than this.

There seems to be (what feels like) bazillions of components being used being served up on servers far from me (with pings times of 200ms or more).  If you could get these companies to serve up components via CDN it would also help (call this my list of "shame"):

www.ciscofeedback.vovici.com
bam.nr-data.net
imp2.ads.linkedin.com
analytics.ziftsolutions.com
dc.ads.linkedin.com
s3.amazonaws.com (used by Zift Solutions - have these guys not heard of CloudFront?)
bat.bing.com
bat.r.msn.com
sp.analytics.yahoo.com
s177775138.t.eloqua.com
cisco-tags.cisco.com
d.agkn.com
engine.adzerk.net
seg.sharethis.com
engine.adzerk.net
p.rfihub.com
p.adsymptotic.com
idsync.rlcdn.com

Remember - this is only the list of domains with a response time GREATER than 200ms.  I suspect that you'll have trouble driving much better page load speeds when you are using so many components which such poor response times.  I think I would personally dump any component that couldn't deliver a global response within 100ms unless I badly needed it.

If you want to do some further testing I can setup a machine with TeamViewer on so you can try it the site from a different location.

View solution in original post

OK, I can do some analysis for you. So, I configured my browser to use HTTP proxy (the list is extracted from proxy's log), flushed browser cache, turned off AddBlock.

Then opened https://supportforums.cisco.com/discussion/13072671/june-updates.

See Table 1 for list of proxy's log records. Note the single record may cover several HTTP requests (because of HTTP persistent connection feature utilized).

Don't hesitate to ask for more data if you wish.

Table 1
  1. [20:19:30] "POST http://ss.symcd.com/ HTTP/1.1" 200 1608
  2. [20:19:30] "POST http://vassg142.ocsp.omniroot.com/ HTTP/1.1" 200 1746
  3. [20:19:33] "POST http://clients1.google.com/ocsp HTTP/1.1" 200 463
  4. [20:19:33] "POST http://gt.symcd.com/ HTTP/1.1" 200 1455
  5. [20:19:33] "POST http://ocsp.godaddy.com/ HTTP/1.1" 200 1776
  6. [20:19:34] "POST http://vassg142.ocsp.omniroot.com/ HTTP/1.1" 200 1746
  7. [20:19:34] "POST http://gn.symcd.com/ HTTP/1.1" 200 1418
  8. [20:19:35] "POST http://gn.symcd.com/ HTTP/1.1" 200 1418
  9. [20:19:34] "CONNECT sharethis.nexac.com:443 HTTP/1.1" 502 1216
  10. [20:19:35] "POST http://ocsp.godaddy.com/ HTTP/1.1" 200 1777
  11. [20:19:35] "POST http://ss.symcd.com/ HTTP/1.1" 200 1608
  12. [20:19:35] "CONNECT img.en25.com:443 HTTP/1.1" 200 -
  13. [20:19:36] "POST http://ocsp.msocsp.com/ HTTP/1.1" 200 1757
  14. [20:19:36] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  15. [20:19:36] "POST http://ss.symcd.com/ HTTP/1.1" 200 1608
  16. [20:19:36] "POST http://vassg142.ocsp.omniroot.com/ HTTP/1.1" 200 1746
  17. [20:19:36] "POST http://sg.symcd.com/ HTTP/1.1" 200 1696
  18. [20:19:36] "POST http://sg.symcd.com/ HTTP/1.1" 200 1696
  19. [20:19:36] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  20. [20:19:37] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  21. [20:19:37] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  22. [20:19:35] "CONNECT cisco-tags.cisco.com:443 HTTP/1.1" 200 -
  23. [20:19:39] "POST http://gn.symcd.com/ HTTP/1.1" 200 1418
  24. [20:19:39] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  25. [20:19:40] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  26. [20:19:43] "POST http://ocsp.godaddy.com/ HTTP/1.1" 200 1776
  27. [20:19:37] "CONNECT s3.amazonaws.com:443 HTTP/1.1" 200 -
  28. [20:19:37] "CONNECT s3.amazonaws.com:443 HTTP/1.1" 200 -
  29. [20:19:35] "CONNECT s3.amazonaws.com:443 HTTP/1.1" 200 -
  30. [20:19:37] "CONNECT s3.amazonaws.com:443 HTTP/1.1" 200 -
  31. [20:19:34] "CONNECT ib.adnxs.com:443 HTTP/1.1" 200 -
  32. [20:19:40] "CONNECT secure.adnxs.com:443 HTTP/1.1" 200 -
  33. [20:19:35] "CONNECT bat.bing.com:443 HTTP/1.1" 200 -
  34. [20:19:36] "CONNECT bat.r.msn.com:443 HTTP/1.1" 200 -
  35. [20:19:35] "CONNECT stags.bluekai.com:443 HTTP/1.1" 200 -
  36. [20:19:32] "CONNECT www.googletagmanager.com:443 HTTP/1.1" 200 -
  37. [20:19:34] "CONNECT s.zkcdn.net:443 HTTP/1.1" 200 -
  38. [20:19:34] "CONNECT cm.g.doubleclick.net:443 HTTP/1.1" 200 -
  39. [20:19:35] "CONNECT s.yimg.com:443 HTTP/1.1" 200 -
  40. [20:19:35] "CONNECT stats.g.doubleclick.net:443 HTTP/1.1" 200 -
  41. [20:19:32] "CONNECT engine.adzerk.net:443 HTTP/1.1" 200 -
  42. [20:19:37] "CONNECT www.google.cz:443 HTTP/1.1" 200 -
  43. [20:19:35] "CONNECT www.google.com:443 HTTP/1.1" 200 -
  44. [20:19:36] "CONNECT analytics.twitter.com:443 HTTP/1.1" 200 -
  45. [20:19:36] "CONNECT www.facebook.com:443 HTTP/1.1" 200 -
  46. [20:19:33] "CONNECT seg.sharethis.com:443 HTTP/1.1" 200 -
  47. [20:19:35] "CONNECT seg.sharethis.com:443 HTTP/1.1" 200 -
  48. [20:19:34] "CONNECT idsync.rlcdn.com:443 HTTP/1.1" 200 -
  49. [20:19:27] "CONNECT supportforums.cisco.com:443 HTTP/1.1" 200 -
  50. [20:19:33] "CONNECT www.google-analytics.com:443 HTTP/1.1" 200 -
  51. [20:19:36] "CONNECT sp.analytics.yahoo.com:443 HTTP/1.1" 200 -
  52. [20:19:40] "CONNECT www.linkedin.com:443 HTTP/1.1" 200 -
  53. [20:19:39] "CONNECT www.bizographics.com:443 HTTP/1.1" 200 -
  54. [20:19:40] "CONNECT eu-west-1.dc.ads.linkedin.com:443 HTTP/1.1" 200 -
  55. [20:19:38] "CONNECT dc.ads.linkedin.com:443 HTTP/1.1" 200 -
  56. [20:19:41] "CONNECT imp2.ads.linkedin.com:443 HTTP/1.1" 200 -
  57. [20:19:38] "CONNECT analytics.ziftsolutions.com:443 HTTP/1.1" 200 -
  58. [20:19:33] "CONNECT l.sharethis.com:443 HTTP/1.1" 200 -
  59. [20:19:09] "CONNECT assets-cdn.github.com:443 HTTP/1.1" 200 -
  60. [20:19:38] "CONNECT bam.nr-data.net:443 HTTP/1.1" 200 -
  61. [20:19:37] "CONNECT tags.bluekai.com:443 HTTP/1.1" 200 -
  62. [20:20:16] "CONNECT fonts.gstatic.com:443 HTTP/1.1" 200 -
  63. [20:19:29] "CONNECT sadmin.brightcove.com:443 HTTP/1.1" 200 -
  64. [20:19:33] "CONNECT ws.sharethis.com:443 HTTP/1.1" 200 -
  65. [20:19:29] "CONNECT ws.sharethis.com:443 HTTP/1.1" 200 -
  66. [20:19:34] "CONNECT t.sharethis.com:443 HTTP/1.1" 200 -
  67. [20:19:34] "CONNECT sb.scorecardresearch.com:443 HTTP/1.1" 200 -
  68. [20:19:34] "CONNECT www.cisco.com:443 HTTP/1.1" 200 -
  69. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  70. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  71. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  72. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  73. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  74. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  75. [20:19:35] "CONNECT j.6sc.co:443 HTTP/1.1" 200 -
  76. [20:19:36] "CONNECT c.6sc.co:443 HTTP/1.1" 200 -
  77. [20:19:35] "CONNECT sjs.bizographics.com:443 HTTP/1.1" 200 -
  78. [20:19:36] "CONNECT s177775138.t.eloqua.com:443 HTTP/1.1" 200 -
  79. [20:19:36] "CONNECT b.6sc.co:443 HTTP/1.1" 200 -
  80. [20:19:37] "CONNECT snap.licdn.com:443 HTTP/1.1" 200 -
  81. [20:19:36] "CONNECT tags.bluekai.com:443 HTTP/1.1" 200 -
  82. [20:19:36] "CONNECT s2026391005.t.eloqua.com:443 HTTP/1.1" 200 -
  83. [20:19:38] "CONNECT js-agent.newrelic.com:443 HTTP/1.1" 200 -

 

   - 1 --

The POST lines are OCSP requests. Remember - single HTTPS connection setup may fire several OCSP requests. The page components should not be taken from so much different sources because of it. Overall time to establish SSL connections to all those sources (including OCSP verification) take about 7 seconds on my computer.

On the other side, the OCSP responses are cached for a while. So no every page is delayed because of them.

   - 2 --

I can load the same page with AdBlock turned on. In such case the single(!) connection to supportforums.cisco.com transfers all necessary data (HTTP persistent connection feature shows it's power here).It decrease time to load substantially.

Although it's off-topic in this thread, allow me small notice about the AdBlock usage here. Feel free to ignore it.

I'm missing no valuable part of page because of AdBlock turned on. Just all those superfluous, abusive and wasteful components are not here (and those components are hidden even if not disabled). Well, I understand your marketing department wish to track users, but why for the hell you need to have five or so tracking systems on the page ? But things are even worse. Why sharethis, twitter, facebook, microsoft, google, linked-in and several others should be notified whenever I open the page ? Sorry, you know no borders, thus I'm blocking tracking data for all including Cisco itself. Moreover it cut page loading time to half.

View solution in original post

8 Replies 8

Philip D'Ath
VIP Alumni
VIP Alumni

Yay, the handbrake was been half taken off.  :-)

Philip D'Ath
VIP Alumni
VIP Alumni

I live in New Zealand, quite a distance from "HQ".  However we have excellent Internet connectivity.

When I run this page through Google Chrome audit I find it loads 127 elements.  127!

I see you are now using Cloudflare.  The audit shows CloudFlare took 16s (yes, 16 seconds) to deliver up the first page.  However this was unusually bad.  Usually it is much better than this.

There seems to be (what feels like) bazillions of components being used being served up on servers far from me (with pings times of 200ms or more).  If you could get these companies to serve up components via CDN it would also help (call this my list of "shame"):

www.ciscofeedback.vovici.com
bam.nr-data.net
imp2.ads.linkedin.com
analytics.ziftsolutions.com
dc.ads.linkedin.com
s3.amazonaws.com (used by Zift Solutions - have these guys not heard of CloudFront?)
bat.bing.com
bat.r.msn.com
sp.analytics.yahoo.com
s177775138.t.eloqua.com
cisco-tags.cisco.com
d.agkn.com
engine.adzerk.net
seg.sharethis.com
engine.adzerk.net
p.rfihub.com
p.adsymptotic.com
idsync.rlcdn.com

Remember - this is only the list of domains with a response time GREATER than 200ms.  I suspect that you'll have trouble driving much better page load speeds when you are using so many components which such poor response times.  I think I would personally dump any component that couldn't deliver a global response within 100ms unless I badly needed it.

If you want to do some further testing I can setup a machine with TeamViewer on so you can try it the site from a different location.

Wow.

I know we have too many components and we are working on this.

However, these > 200ms ping times are unacceptable.

Can you send me a screen shot or export of this report?

Rick

I can't do that so easily, as 127 components takes up many many screens.  However rest assured the list of shame above contributes to the majority of the page load time.

I have attached one of the Chrome summary graphs for you.  This shows you Chrome spends 6s just waiting for all those different sites to respond.  That is 74% of the entire page load time.

OK, I can do some analysis for you. So, I configured my browser to use HTTP proxy (the list is extracted from proxy's log), flushed browser cache, turned off AddBlock.

Then opened https://supportforums.cisco.com/discussion/13072671/june-updates.

See Table 1 for list of proxy's log records. Note the single record may cover several HTTP requests (because of HTTP persistent connection feature utilized).

Don't hesitate to ask for more data if you wish.

Table 1
  1. [20:19:30] "POST http://ss.symcd.com/ HTTP/1.1" 200 1608
  2. [20:19:30] "POST http://vassg142.ocsp.omniroot.com/ HTTP/1.1" 200 1746
  3. [20:19:33] "POST http://clients1.google.com/ocsp HTTP/1.1" 200 463
  4. [20:19:33] "POST http://gt.symcd.com/ HTTP/1.1" 200 1455
  5. [20:19:33] "POST http://ocsp.godaddy.com/ HTTP/1.1" 200 1776
  6. [20:19:34] "POST http://vassg142.ocsp.omniroot.com/ HTTP/1.1" 200 1746
  7. [20:19:34] "POST http://gn.symcd.com/ HTTP/1.1" 200 1418
  8. [20:19:35] "POST http://gn.symcd.com/ HTTP/1.1" 200 1418
  9. [20:19:34] "CONNECT sharethis.nexac.com:443 HTTP/1.1" 502 1216
  10. [20:19:35] "POST http://ocsp.godaddy.com/ HTTP/1.1" 200 1777
  11. [20:19:35] "POST http://ss.symcd.com/ HTTP/1.1" 200 1608
  12. [20:19:35] "CONNECT img.en25.com:443 HTTP/1.1" 200 -
  13. [20:19:36] "POST http://ocsp.msocsp.com/ HTTP/1.1" 200 1757
  14. [20:19:36] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  15. [20:19:36] "POST http://ss.symcd.com/ HTTP/1.1" 200 1608
  16. [20:19:36] "POST http://vassg142.ocsp.omniroot.com/ HTTP/1.1" 200 1746
  17. [20:19:36] "POST http://sg.symcd.com/ HTTP/1.1" 200 1696
  18. [20:19:36] "POST http://sg.symcd.com/ HTTP/1.1" 200 1696
  19. [20:19:36] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  20. [20:19:37] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  21. [20:19:37] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  22. [20:19:35] "CONNECT cisco-tags.cisco.com:443 HTTP/1.1" 200 -
  23. [20:19:39] "POST http://gn.symcd.com/ HTTP/1.1" 200 1418
  24. [20:19:39] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  25. [20:19:40] "POST http://ocsp.digicert.com/ HTTP/1.1" 200 471
  26. [20:19:43] "POST http://ocsp.godaddy.com/ HTTP/1.1" 200 1776
  27. [20:19:37] "CONNECT s3.amazonaws.com:443 HTTP/1.1" 200 -
  28. [20:19:37] "CONNECT s3.amazonaws.com:443 HTTP/1.1" 200 -
  29. [20:19:35] "CONNECT s3.amazonaws.com:443 HTTP/1.1" 200 -
  30. [20:19:37] "CONNECT s3.amazonaws.com:443 HTTP/1.1" 200 -
  31. [20:19:34] "CONNECT ib.adnxs.com:443 HTTP/1.1" 200 -
  32. [20:19:40] "CONNECT secure.adnxs.com:443 HTTP/1.1" 200 -
  33. [20:19:35] "CONNECT bat.bing.com:443 HTTP/1.1" 200 -
  34. [20:19:36] "CONNECT bat.r.msn.com:443 HTTP/1.1" 200 -
  35. [20:19:35] "CONNECT stags.bluekai.com:443 HTTP/1.1" 200 -
  36. [20:19:32] "CONNECT www.googletagmanager.com:443 HTTP/1.1" 200 -
  37. [20:19:34] "CONNECT s.zkcdn.net:443 HTTP/1.1" 200 -
  38. [20:19:34] "CONNECT cm.g.doubleclick.net:443 HTTP/1.1" 200 -
  39. [20:19:35] "CONNECT s.yimg.com:443 HTTP/1.1" 200 -
  40. [20:19:35] "CONNECT stats.g.doubleclick.net:443 HTTP/1.1" 200 -
  41. [20:19:32] "CONNECT engine.adzerk.net:443 HTTP/1.1" 200 -
  42. [20:19:37] "CONNECT www.google.cz:443 HTTP/1.1" 200 -
  43. [20:19:35] "CONNECT www.google.com:443 HTTP/1.1" 200 -
  44. [20:19:36] "CONNECT analytics.twitter.com:443 HTTP/1.1" 200 -
  45. [20:19:36] "CONNECT www.facebook.com:443 HTTP/1.1" 200 -
  46. [20:19:33] "CONNECT seg.sharethis.com:443 HTTP/1.1" 200 -
  47. [20:19:35] "CONNECT seg.sharethis.com:443 HTTP/1.1" 200 -
  48. [20:19:34] "CONNECT idsync.rlcdn.com:443 HTTP/1.1" 200 -
  49. [20:19:27] "CONNECT supportforums.cisco.com:443 HTTP/1.1" 200 -
  50. [20:19:33] "CONNECT www.google-analytics.com:443 HTTP/1.1" 200 -
  51. [20:19:36] "CONNECT sp.analytics.yahoo.com:443 HTTP/1.1" 200 -
  52. [20:19:40] "CONNECT www.linkedin.com:443 HTTP/1.1" 200 -
  53. [20:19:39] "CONNECT www.bizographics.com:443 HTTP/1.1" 200 -
  54. [20:19:40] "CONNECT eu-west-1.dc.ads.linkedin.com:443 HTTP/1.1" 200 -
  55. [20:19:38] "CONNECT dc.ads.linkedin.com:443 HTTP/1.1" 200 -
  56. [20:19:41] "CONNECT imp2.ads.linkedin.com:443 HTTP/1.1" 200 -
  57. [20:19:38] "CONNECT analytics.ziftsolutions.com:443 HTTP/1.1" 200 -
  58. [20:19:33] "CONNECT l.sharethis.com:443 HTTP/1.1" 200 -
  59. [20:19:09] "CONNECT assets-cdn.github.com:443 HTTP/1.1" 200 -
  60. [20:19:38] "CONNECT bam.nr-data.net:443 HTTP/1.1" 200 -
  61. [20:19:37] "CONNECT tags.bluekai.com:443 HTTP/1.1" 200 -
  62. [20:20:16] "CONNECT fonts.gstatic.com:443 HTTP/1.1" 200 -
  63. [20:19:29] "CONNECT sadmin.brightcove.com:443 HTTP/1.1" 200 -
  64. [20:19:33] "CONNECT ws.sharethis.com:443 HTTP/1.1" 200 -
  65. [20:19:29] "CONNECT ws.sharethis.com:443 HTTP/1.1" 200 -
  66. [20:19:34] "CONNECT t.sharethis.com:443 HTTP/1.1" 200 -
  67. [20:19:34] "CONNECT sb.scorecardresearch.com:443 HTTP/1.1" 200 -
  68. [20:19:34] "CONNECT www.cisco.com:443 HTTP/1.1" 200 -
  69. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  70. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  71. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  72. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  73. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  74. [20:19:35] "CONNECT tags.tiqcdn.com:443 HTTP/1.1" 200 -
  75. [20:19:35] "CONNECT j.6sc.co:443 HTTP/1.1" 200 -
  76. [20:19:36] "CONNECT c.6sc.co:443 HTTP/1.1" 200 -
  77. [20:19:35] "CONNECT sjs.bizographics.com:443 HTTP/1.1" 200 -
  78. [20:19:36] "CONNECT s177775138.t.eloqua.com:443 HTTP/1.1" 200 -
  79. [20:19:36] "CONNECT b.6sc.co:443 HTTP/1.1" 200 -
  80. [20:19:37] "CONNECT snap.licdn.com:443 HTTP/1.1" 200 -
  81. [20:19:36] "CONNECT tags.bluekai.com:443 HTTP/1.1" 200 -
  82. [20:19:36] "CONNECT s2026391005.t.eloqua.com:443 HTTP/1.1" 200 -
  83. [20:19:38] "CONNECT js-agent.newrelic.com:443 HTTP/1.1" 200 -

 

   - 1 --

The POST lines are OCSP requests. Remember - single HTTPS connection setup may fire several OCSP requests. The page components should not be taken from so much different sources because of it. Overall time to establish SSL connections to all those sources (including OCSP verification) take about 7 seconds on my computer.

On the other side, the OCSP responses are cached for a while. So no every page is delayed because of them.

   - 2 --

I can load the same page with AdBlock turned on. In such case the single(!) connection to supportforums.cisco.com transfers all necessary data (HTTP persistent connection feature shows it's power here).It decrease time to load substantially.

Although it's off-topic in this thread, allow me small notice about the AdBlock usage here. Feel free to ignore it.

I'm missing no valuable part of page because of AdBlock turned on. Just all those superfluous, abusive and wasteful components are not here (and those components are hidden even if not disabled). Well, I understand your marketing department wish to track users, but why for the hell you need to have five or so tracking systems on the page ? But things are even worse. Why sharethis, twitter, facebook, microsoft, google, linked-in and several others should be notified whenever I open the page ? Sorry, you know no borders, thus I'm blocking tracking data for all including Cisco itself. Moreover it cut page loading time to half.

I just tried AdBlock Plus.

What a difference.  On this site the Chrome Developer tools reports the time spent "idle" waiting for all those sites to responds drops from 6s to 3s.

That is almost twice as fast!

Wow, thats nice job done !

I hoped for a comment from Cisco, but it seems we will receive no one.

OK.

For those wishing to block abusive components - I'm using following set of AdBlock rules:

  • cisco.com##.sharethis.last
  • ||adzerk.net^$third-party
  • ||js-agent.newrelic.com^$third-party
  • ||brightcove.com^$third-party
  • ||sspgdev.atlassian.net^$third-party
  • ||sharethis.com^$third-party
  • ||cisco.com/web/fw/m/metrics.min.js?*
  • ||googletagmanager.com^$third-party

All remaining components are served from supportforums.cisco.com so only single single stream can carry all of them (if browser supports pipelining).