Now, if you just dumped your other ad networks and ran everything through us, I bet it would be load much faster and that badge might magically disappear..."
Now, if you just dumped your other ad networks and ran everything through us, I bet it would be load much faster and that badge might magically disappear..."
We mention that ad scripts are a common type of problematic 3rd-party resource but we use the phrase “3rd-party resource” because there are lots of other common problematic scripts, like A/B tests, social media widgets, and analytics scripts.
Disclosure: I work on web.dev
This sort of basic advice (use browser features to defer loading, and plead with the masters not to ask for so much JavaScript) is obviously already considered by the HN audience and so this link is basically useless.
I sincerely doubt 100% of the HN audience always considers those things.
You might think some of those things are basic, but that doesn't make them useless.
This kind of lack of empathy for new learners can make it incredibly difficult to teach concepts to those who don't have as much knowledge as you may have.
See https://www.youtube.com/watch?v=OkmNXy7er84 for a great video by 3blue1brown on this topic.
My experience with everything google has touched lately suggest that this wouldn't improve speed any. Gmail and youtube make continental drift look speedy and even the search page takes 1.4MB and takes over a second to load for me (maybe corporate network issue), that's approaching the size of doom to display a dozen links.
Google doesn't have any moral authority when it comes to bloat.
Edit - for reference HN takes about the same time to load, but that has to cross the pacific ocean whereas google supposedly has local data centers.
That said, if your search page takes over a second, you're right, it might be an issue with your network.
(Note that the table gets cut off on narrow mobile screens... I’ll file a bug)
FCP is 20% of the score. The other metrics capture different milestones in the loading experience. For example Total Blocking Time is intended to bring awareness to sites that may look complete but can’t respond to user input (because the main thread is busy running JS).
The metrics overview that we just launched provides more detail about how our metrics were designed to capture the end-to-end loading experience (or at least that’s what we’re working towards): https://web.dev/user-centric-performance-metrics/
So in the case of your site-that-just-loads-a-spinner example, yes it might have a good FCP time, but it’s LCP time probably wouldn’t be that good, and therefore the overall Performance score would be mediocre.
Long story short, I don’t think it’s as easy to game a good Performance score as you might think
Disclosure: I work on web.dev
HN is behind Cloudflare, and so also has local DCs