Every Byte of a TLS Connection Explained and Reproduced

Re:Every Byte of a TLS Connection Explained and Reproduced by pjc50 on Friday October 12, 2018 @11:09AM (#18201916)

Gmail was using TLS since day 1. If it's slow for you the first likely culprit is the sheer weight of Javascript and DOM work, followed by making more web requests than necessary.

[ Parent | on HN ]

Re:Every Byte of a TLS Connection Explained and Reproduced by logicallee on Friday October 12, 2018 @01:11PM (#18202919)

>the sheer weight of Javascript and DOM work, followed by making more web requests than necessary.

can you (or anyone) put this into quantitative terms? How much are we talking about here? I realize this is a bit off-topic, but the topic is "every byte explained", so I think the people who are interested are in the right place to discuss it.

[ Parent | on HN ]

Re:Every Byte of a TLS Connection Explained and Reproduced by Obi_Juan_Kenobi on Friday October 12, 2018 @02:00PM (#18203319)

You can see a lot of what's going on with a e.g. DevTools in Chrome. Right click -> inspect

You'll want to go to the performance tab, and then record and reload the page (ctrl-shift-e). For me, about 3/4ths of the time is spent 'scripting' which is 'JS and DOM work'.

It's not terribly enlightening, though, because all the JS is minified and takes some work to understand.

[ Parent | on HN ]

Re:Every Byte of a TLS Connection Explained and Reproduced by logicallee on Friday October 12, 2018 @02:40PM (#18203669)

how much time is that for you? How does it compare to another dynamic site such as the one we're on (HN) when you're logged in?

[ Parent | on HN ]