You might ask @addyosmani; honestly, we're years late in delivering meaningful, on-by-default indications of page quality in either the browser UI or devtools -- but hope spring eternal.
-
-
Replying to @slightlylate @ianand and
Put differently, the folks who are naturally the regulators and user's advocates have (to my mind) been more-or-less fully captured by the JS-industrial-complex.
1 reply 0 retweets 1 like -
-
-
Replying to @slightlylate @ianand and
Specifically, it's fast-enough when loaded via the Search Results Page (and other pre-loading viewers) because of a huge pile of ultra-careful end-to-end optimisation which aren't available in the cold-load-from-origin scenarios. So I can't yet recommend it for your own site.
1 reply 0 retweets 3 likes -
Replying to @slightlylate @tomskitomski and
Yes this is why we cross compile to it (for SERP benefit). But starting to think it’s better in cold start case than leaving devs to tie a perf noose otherwise.
1 reply 0 retweets 0 likes -
Replying to @ianand @slightlylate and
The UK site is a good example. It’s not scalable that govt can have a perf engineer like
@dracos on every page they publish. AMP compliance is.3 replies 0 retweets 1 like -
Replying to @ianand @tomskitomski and
That's why the UK Govt has tended, instead, to opt for blanket policies and tool choices that make those sorts of outcomes unusual: https://www.gov.uk/service-manual
2 replies 0 retweets 3 likes -
Replying to @slightlylate @ianand and
The thing about this specific http://gov.uk subsite that makes it such a sore thumb is that the *rest* of the sprawling enterprise has avoided exactly this sort of pratfall.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @ianand and
Here, for example, is the UK gov's primary COVID page: https://www.gov.uk/coronavirus And traces: https://www.webpagetest.org/result/200417_MQ_0ad46129a386d547f296065a9dadcc24/ … It's *really bloody fast*, just like nearly all the rest of http://gov.uk because (until, it seems, very recently) this sort of JS bloat was verboten.
4 replies 0 retweets 1 like
If there's a lesson here, it's "'modern' frontend: not even once"
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.