Google can't pass its own page speed test

Re:Google can't pass its own page speed test by uses on Saturday June 05, 2021 @11:22AM (#27405798)

One of the frustrating things about being a web developer is that I can do a ton of advanced optimization to the point of code splitting my js with dynamic import() or doing page level caching, lazyloading, and splitting non-critical CSS. But other departments of my org can squash it by adding a chat plugin with a disgusting level of resource abuse which obliterates all the advances I've made.

My approach is to just explain what I can or can't do, and explain the trade-offs for everything. I'll give the decision-makers the info but I'm not going to be the curmudgeon going to war over something the marketing people say we need to survive.

[ Parent | on HN ]

Re:Google can't pass its own page speed test by kmeisthax on Saturday June 05, 2021 @03:17PM (#27407773)

DNS resolution 12ms

First-byte time 64ms

CSS & JavaScript 148ms

Analytics 3,157ms

Images 250ms

someone who is good at the web please help me budget this. my store is slow

[ Parent | on HN ]

Re:Google can't pass its own page speed test by cocoafleck on Saturday June 05, 2021 @03:32PM (#27407884)

Well clearly we can't remove analytics, and if we changed analytics to a different (faster) provider someone would have a cow... We could lower our image sizes, but let's be honest that would result in the dreaded JPGing. Our Javascript is a hand crafted wonder that we just rebuilt for the 6th time in the past decade in a new modern better framework so clearly that cannot be the problem. Therefore I'm leaning towards adding a CDN to lower the first byte time, or yelling at our DNS provider to speed up their side. /s

[ Parent | on HN ]

Re:Google can't pass its own page speed test by easrng on Saturday June 05, 2021 @07:15PM (#27409209)

Just load the analytics async, ezpz

[ Parent | on HN ]