ex-Head of Frontend Development @gdsteam. Passionate about #webperf & F1. @TheRealNooshu@hachyderm.io / @therealnooshu.bsky.social. Opinions my own.
Jan 9, 2023 • 27 tweets • 10 min read
<🧵>1/26 GOV.UK stats for December‡ (1-31):
- Chrome - 49.31%
- Safari - 31.09%
- Edge - 11.3%
- Samsung Internet - 4.67%
- Firefox - 1.3%
- Android Webview - 0.75%
- Safari (in-app) - 0.68%
- Opera - 0.27%
100% = 77,255,399 #browser#browserstats
2/26
‡ Note: since December 2019 GOV.UK requires explicit opt-in for tracking which introduces bias. This is especially true for mobile devices, since the cookie banner takes up more screen estate and is more likely to be accepted.
May 6, 2022 • 25 tweets • 7 min read
<🧵> GOV.UK stats for April‡ (1-30):
- Chrome - 47.62%
- Safari - 33.62%
- Edge - 9.08%
- Samsung Internet - 6.01%
- Firefox - 1.38%
- Android Webview - 0.65%
- Internet Explorer - 0.58%
- Safari (in-app) - 0.56%
100% = 118,055,607 #browser#browserstats
‡ Note: since December 2019 GOV.UK requires explicit opt-in for tracking which introduces bias. This is especially true for mobile devices, since the cookie banner takes up more screen estate and is more likely to be accepted.
100% = 143,123,441 #browser#browserstats
‡ Note: since December 2019 GOV.UK requires explicit opt-in for tracking which introduces bias. This is especially true for mobile devices, since the cookie banner takes up more screen estate and is more likely to be accepted.
Mar 31, 2022 • 11 tweets • 5 min read
🧵As I mentioned last week GOV.UK removed jQuery as a dependency for all frontend apps, meaning 32 KB of minified & compressed JS was removed. So let's see what difference this has made for users by examining our RUM data. Thread will mainly focus on JS CPU time.
A good place to start is users on low spec devices. The Universal Credit sign-in page shows a lot of this traffic, as seen in the images below.
Great to see some fantastic #webperf work happening on GOV.UK at the moment. The team have been gradually removing the shard domain for critical assets, and it's made quite a difference! Images from Chrome on a 3G connection and S4 on 3G. 1/4
Considering where we were at the start of Feb: HTTP/1.1, SRI, shard domain, ~13 TCP connections. Now down to just 1 TCP connection in many cases. 2/4
Apr 7, 2020 • 16 tweets • 3 min read
Haven't published GOV.UK browser stats since the change to analytics tracking in Dec (opt-in only). Look to be getting ~30-40% of traffic we were before the change.
So what have Feb / Mar looked like with since the coronavirus outbreak?
So I finished @tunetheweb's book "HTTP/2 in Action" yesterday. A real tome of a book that teaches you all the intricate details of the new protocol (plus much much more).
For anyone interested in how HTTP works (and networks in general) it's a must-read.
One of many key learnings for me:
• HTTP/1.1 has Head-of-line blocking (HOL blocking) do to the synchronous nature of HTTP.
• HTTP/2 removes HOL blocking from the HTTP level, but it is still present in the TCP level.
• ...continued below...