responded here:https://twitter.com/FredKSchott/status/1157388801515200512 …
-
-
So I'd add <link rel=preconnect to the GTM and GA origins. Chrome is scheduling them at lowest priority and it doesn't connect eagerly, preconnect should move it forward I'd also self host fontawesome, and consider loading Google Fonts async if you cope with the font reflow
2 replies 1 retweet 4 likes -
I'd preload GA, not just preconnect
1 reply 0 retweets 0 likes -
But why? Preloading GA means everything else gets a lower priority (particularly on poor connections) Surely the site content is more important than the analytics?
1 reply 0 retweets 0 likes -
Having GA run earlier while other content is being downloaded means it's not contended with other JS that is trying to run after DomContentLoaded.
1 reply 0 retweets 0 likes -
Sorry for the slow reply. Here's the 3G trace on the same hardware: https://www.webpagetest.org/result/190802_7Q_3a7b3a5321251394011376ae4f1798be/ … I have some questions!
1 reply 0 retweets 0 likes -
Replying to @slightlylate @mikesherov and
Looking at the filmstrip, it seems that the big ticket item is the search result: https://www.webpagetest.org/video/compare.php?tests=190802_7Q_3a7b3a5321251394011376ae4f1798be-r:1-c:0 …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @mikesherov and
It *looks* as though that isn't getting fetched until `fetch.js` comes in, which doesn't seem to get requested until relatively late. On the analytics stuff, honestly, I'd move that *below* the critical content.
2 replies 0 retweets 1 like -
Replying to @slightlylate @mikesherov and
...otherwise, on a slow link like this, you're spending a lot of your bandwidth in the critical moments on connection setup on stuff that doesn't actually improve the user experience.
2 replies 0 retweets 0 likes -
thanks for taking the time to look at this. There's a good chance you caught the search API endpoint on a restart / cold start (i had just deployed around the time it ran). I re-ran on 3G and saw a much more reasonable 446ms response time for that endpoint
1 reply 0 retweets 0 likes
Right, I'm not so stressed about that latency (backend is much easier to fix!), it's when the request gets kicked off that I'm highlighting.
-
-
agreed, this weekend I'd like to pull out GA + Google Fonts + Font Awesome and see what the performance is like, and then add them back one at a time more carefully
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.