2 ms·
"Did Google run out of actual features to implement?" That question is kind of coming in at the wrong angle. Google has identified the speed at which web site
by BLKNSLVR 7y ago
"Did Google run out of actual features to implement?"
That question is kind of coming in at the wrong angle. Google has identified the speed at which web sites load as a problem, and have determined that is a problem worth their while to try and solve.
The problem is that it's all the tracking and advertising that's the cause of the slow loading and Google, being as that tracking and advertising pays their bills, can't solve that as the fundamental problem, so they're doing a very odd looking Twister-Limbo set of actions in trying to reframe what the problem is: speed of page loading.
Google are attempting to treat the symptoms, because they profit from the cause.
Google needs to solve the speed symptom before someone else solves the ad and tracking cause (ad blockers, PiHole, etc.) in a more fundamentally non-technical-user accessible way.
- judge2020 7y agoAt least based on the picture, the 'slow' badge should only show during the TTFB, ie. before any paint occurs. Since Google Ads loads after the paint websites likely won't have issues of mis-labeling.
- ouid 7y agoThe vast majority of people that I know who don't use adblock do so because they are A) afraid that it will slow down their web browsing, or B) believe that it magically generates money for content creators.
- Arnt 7y agoI disagree strongly with your analysis. Advertising is a contributor, but it's far from being the cause. AFAICT there are five causes, namely slow DNS lookups due to inappropriately low TTLs, a lack of caching both serverside and clientside, page bloat, an overdose of javascript and an overdose of tracking/advertising (which contributes to bloat and javascript). Making a Rails site pleasantly fast was more work than it should've been. Rails didn't make it easy to cache page components, didn't make it easy to cache the entire page either, made it easy to inadvertently wait on the database. And here's the key, this doesn't seem to be regarded as a big problem. The rails developers and users don't regard slow speed as a big problem. Is that unusual? Do Django, Magnolia, Magento have a different culture? I haven't noticed (but I might not). Assuming not, the root cause is an inattention to making sites pleasantly fast, and that inattention has simply allowed advertising to have the same problem as the rest of the site's software.