News for hackers. Stuff that matters.
Re:Moving towards a faster web by ipython on Monday November 11, 2019 @03:33PM (#21508594)
This reads to me as an attempt from Google to further balkanize the web. This looks a lot like the "blue bubbles" effect from Apple iMessage.

Did Google run out of actual features to implement? How about reacting to real user concerns such as controlling the privacy of their personal data on the web? Rhetorical question, I know...

Re:Moving towards a faster web by BLKNSLVR on Monday November 11, 2019 @07:35PM (#21510405)
"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.

Re:Moving towards a faster web by Arnt on Tuesday November 12, 2019 @03:57AM (#21512641)
I 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.

Re:Moving towards a faster web by judge2020 on Monday November 11, 2019 @08:23PM (#21510660)
At 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.
Re:Moving towards a faster web by ouid on Monday November 11, 2019 @09:21PM (#21510958)
The 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.
Re:Moving towards a faster web by lkbm on Monday November 11, 2019 @03:40PM (#21508649)
Speaking as a real user, let me assure you that website speed definitely falls under real user concerns. I don't know how much I'd use this indicator, but loading speed matters to me. Loading speed matters a lot.

This won't win me back from Firefox, but I don't consider it a bad move.

Re:Moving towards a faster web by taeric on Monday November 11, 2019 @03:49PM (#21508750)
You know what loads fast? Web pages. What doesn't? User tracking applications that happen to host some content. :(
Re:Moving towards a faster web by robbrown451 on Monday November 11, 2019 @04:16PM (#21508992)
If you are against user tracking, great, you've got many on your side.

But what loads fast is web pages that are made to load fast. If they are able to load fast despite user tracking (which is entirely possible), then it is simply a different issue, and this should not be flagging them as slow. If they are flagged, it should be by something different.

If Google is going to implement this (which I support in general because so many sites are painfully slow because there aren't enough incentives to make them fast), what they should be measuring is speed of loading, independent of whether it is slow because of user tracking, slow because the developers do other obnoxious stuff (fill it with click bait images, have videos autoplay, etc), use frameworks sloppily, put too much contents on the page, have a high res background image or video, have a crappy server or use a slow backend language, or whatever it is.

While Google does a lot of user tracking, I think the normal way they do it is actually pretty fast. Fault them for user tracking, but if they are able to allow site owners show Google ads without slowing down the page load significantly, don't lump them in with all these other ones that both track users, as well as make the site a painful user experience.

Re:Moving towards a faster web by taeric on Monday November 11, 2019 @04:43PM (#21509209)
I don't want to be stonewalling progress. But evidence is that any savings win here will be wasted by the same parties that are bringing the savings.

Google lost a ton of good will by making Gmail a laughably bad experience on load.

Re:Moving towards a faster web by mattkevan on Monday November 11, 2019 @06:29PM (#21510053)
When I had to use gmail for work I switched back to the plain html interface. It was startlingly fast

As far as I could see all the complicated front-end stuff added zero to the user experience. Ok, so yeah, you needed a page load to view a message or whatever, but it was quick and hardly noticeable. All they needed to do was freshen up the stylesheet and call it a day. But, I guess, all those developers and product managers needed something to do in between building a new messaging app and killing the previous one.

Re:Moving towards a faster web by graphememes on Monday November 11, 2019 @07:50PM (#21510476)
Just switched over to the HTML view, and wow. I'm never going back.
Re:Moving towards a faster web by segmondy on Monday November 11, 2019 @04:18PM (#21509022)
Then demand for smaller sites, nothing will make for a faster web if web pages are larger than operating systems from just a few years ago. do you know how ridiculous it is to have web pages that are tens and hundreds of megs?

The issue is not with the browsers, it's with the damn stupid sites out there. 3G is pretty much useless out there, let alone 2G.

Re:Moving towards a faster web by zeroxfe on Monday November 11, 2019 @04:24PM (#21509074)
How do you demand for smaller sites? To whom do you plead? Why will they listen to you?
Re:Moving towards a faster web by youareostriches on Monday November 11, 2019 @04:34PM (#21509149)
You demonstrate your intent by paying for content subscriptions rather than visiting sites entirely supported by online advertisements.
Re:Moving towards a faster web by alexis_fr on Monday November 11, 2019 @05:55PM (#21509813)
There is no paid site that matches the quality of HN. Same goes for most social network: What gives them value is contributions, and contributions only seem to happen if the access is free. Otherwise you don’t reach a high-enough density of people.
Re:Moving towards a faster web by youareostriches on Tuesday November 12, 2019 @12:32AM (#21511773)
It should’ve been obvious I was talking about news sites. Even if I wasn’t, you assumed I was talking about social media without any supporting basis.
Re:Moving towards a faster web by koz_ on Monday November 11, 2019 @06:00PM (#21509847)
This is an attempt by Google to influence the bloated websites out there, rather than a browser feature intended to attract users. It's probably mildly helpful as a user to know if a site is slow (as opposed to it just being slow for you), but it's a big incentive for a website owner to speed up their site if this badge of shame appears it for a majority of users.
Re:Moving towards a faster web by weare138 on Monday November 11, 2019 @07:22PM (#21510336)
Except of course unless it's one of Google's sites...

https://developers.google.com/speed/pagespeed/insights/?url=...

Gmail scores a 50% on Google's own PageSpeed. And that's just the login screen. If Google can't even meet their own metrics and standards then they have no place telling other people what they should be doing with their websites.

Re:Moving towards a faster web by Avamander on Monday November 11, 2019 @07:32PM (#21510394)
> If Google can't even meet their own metrics and standards then they have no place telling other people what they should be doing with their websites.

The fact that they are failing their own if anything, shows that the tests don't discriminate. It's defeatist to say that we shouldn't strive for faster websites if some webpage fails. I really like how dumb f*s making 40MiB pages are now finally punished.

Re:Moving towards a faster web by jvzr on Tuesday November 12, 2019 @02:44AM (#21512278)
Yes, but Gmail doesn't really have to compete in Google Search, does it? So, in their eyes, it's OK for Gmail to score low because it has its own link in basically every navigation toolbar/header Google owns. This won't improve the speed at which Gmail loads, whereas all non-Google websites will have to improve their speed.
Re:Moving towards a faster web by koz_ on Tuesday November 12, 2019 @06:11PM (#21519266)
It's not that Gmail has a dominant position and so doesn't need to care about its rating - Gmail is an app not a page and it's less important for apps to load quickly than pages. Apps tend to be long lived and so a slow startup time is tolerable, whereas one is constantly opening new pages.

That is to say, I don't think e.g. Trello would really care if their site was "slow to load" either.

Re:Moving towards a faster web by dmitriid on Monday November 11, 2019 @06:47PM (#21510159)
This is an attempt by Google to force everyone into AMP and nothing else.
Re:Moving towards a faster web by alwillis on Tuesday November 12, 2019 @02:19AM (#21512164)
You might be surprised how fast web pages load when the browser you’re using blocks the tracking scripts, especially on a mobile device. Brave runs on iOS and Android; the iOS version with the Brave Rewards wallet is expected to be released imminently.

You might want to take a look at Brave, which uses Chromium underneath, has Tor built-in, is compatible with Chrome’s plugins and even has a business model based on paying people to view ads only if they opt-in: https://brave.com/features/

Re:Moving towards a faster web by holtalanm on Monday November 11, 2019 @04:54PM (#21509296)
I have never seen a site that loaded hundreds of megs of data. That seems a little exaggeratory.
Re:Moving towards a faster web by TeMPOraL on Monday November 11, 2019 @05:00PM (#21509356)
You've been lucky and didn't encounter sites loading 1080p videos as "hero images". Or perhaps you haven't browsed a news site with ad blocker off?
Re:Moving towards a faster web by tim58 on Monday November 11, 2019 @09:46PM (#21511097)
> Or perhaps you haven't browsed a news site with ad blocker off?

Yeah, it's been years and years since I did much browsing with an ad blocker off.

Re:Moving towards a faster web by shantly on Monday November 11, 2019 @05:55PM (#21509809)
Memory size is a problem, too. Even a small amount of Javascript can allocate a ton of memory. I'd love to see a more memory-efficient language replace JS, then a reasonable but lowish memory limit put in place. Say, 8MB, which still seems generous to me.

The only trouble is you'd have to find some way to keep developers from using the DOM as extra memory. But the capabilities of Web scripting languages, outside perhaps some very strict and explicitly enabled on a case-by-case basis sandbox, really ought to be limited more anyway.

Re:Moving towards a faster web by icebraining on Tuesday November 12, 2019 @05:53AM (#21513136)
JS is not necessarily heavy. For example, the Espruino is a platform running JS on microcontrollers with less than 100KB of RAM: https://www.espruino.com/
Re:Moving towards a faster web by reaperducer on Monday November 11, 2019 @04:25PM (#21509079)
Do you really need your browser to tell you a site is loading slowly? You're staring at the screen; don't you know if it's slow just by existing and moving forward through time?

Or is this just a way for Google to kill off the progress bar, too?

Re:Moving towards a faster web by theevilsharpie on Monday November 11, 2019 @08:23PM (#21510662)
Based on my understanding, Google would be communicating _why_ the site is loading slowly (the network, or the site itself), which isn't something that would be immediately obvious.
Re:Moving towards a faster web by jefftk on Monday November 11, 2019 @05:51PM (#21509772)
If I'm staring at the screen waiting for a page to load, a loading indicator can help me figure out if I should keep waiting longer or give up. That's very useful!

If this gets site owners to work more on loading speed so they can get a badge that's great. I used to work on mod_pagespeed and one of the big problems was that publishers just didn't care that much about loading speed.

(Disclosure: I work for Google)

Re:Moving towards a faster web by jfoster on Monday November 11, 2019 @08:26PM (#21510676)
Based on what this feature is and the scenario you described, I think it may disincent site owners from speeding up slow sites. At the moment, a user doesn't know if a site will ever load. If Chrome reassures that "this site usually loads slowly" they may stick around since they are then reassured that it probably will eventually load, it's just taking a while.
Re:Moving towards a faster web by jefftk on Monday November 11, 2019 @09:36PM (#21511044)
Maybe users will respond that way, but that's still a good outcome. Giving users a better idea about what to expect so they can make more informed decisions? Great!
Re:Moving towards a faster web by close04 on Tuesday November 12, 2019 @08:23AM (#21513838)
> Giving users a better idea about what to expect

Can I expect Google to do the same about data that may be sent by Chrome to Google without users realizing, just so users can make informed decisions?

Re:Moving towards a faster web by jefftk on Tuesday November 12, 2019 @10:05AM (#21514624)
Is https://myactivity.google.com/myactivity what you're looking for?
Re:Moving towards a faster web by close04 on Wednesday November 13, 2019 @03:01AM (#21521947)
No. I mean a badge that pops up for Google products warning you that they may send your personal data to Google even without any user interaction, when the user does not reasonably expect this. What happened to "Giving users a better idea about what to expect so they can make more informed decisions"? I guess profit has a stronger scent and we can all assume that Google is tricking users with those "slow loading page" warnings just to get more for themselves. I feel that you are being willfully ignorant about this.

> Both Android and Chrome send data to Google even in the absence of any user interaction. Our experiments show that a dormant, stationary Android phone (with Chrome active in the background) communicated location information to Google 340 times during a 24-hour period, or at an average of 14 data communications per hour. In fact, location information constituted 35% of all the data samples sent to Google.[0]

[0] https://digitalcontentnext.org/wp-content/uploads/2018/08/DC...

Re:Moving towards a faster web by buboard on Monday November 11, 2019 @07:27PM (#21510366)
If their speed assessment works as "great" as their "mobile usability" tool works, i doubt their indicator will be actually meaningful. YEah speed matters a lot , but it's self-correcting. If a website cannot load after a minute on a spotty cellular connection , i ll just close the browser and they lose the impresison
Re:Moving towards a faster web by Angostura on Tuesday November 12, 2019 @09:16AM (#21514228)
I agree speed is a concern. It takes me at least second to tap the tittle AMP banner and then tap on the real website address.
Re:Moving towards a faster web by themoonbus on Monday November 11, 2019 @03:54PM (#21508820)
Walled gardens and proprietary software can allow for fantastic user experiences in a way that open platforms often cannot match. However, I feel focusing on the user experience misses the main point - the web is an open platform, and this is an example of Google exerting an authority that many may not feel comfortable with.
Re:Moving towards a faster web by lkbm on Monday November 11, 2019 @04:02PM (#21508880)
In what way is "indicate that this website is slow" a walled garden or contrary to openness?
Re:Moving towards a faster web by skywhopper on Monday November 11, 2019 @04:08PM (#21508921)
Because the criteria will inevitably be biased towards technology and techniques that favor Google, Chrome, AMP, etc. If you trust Google to be an unbiased arbiter of objective measurements of website efficiency, you are giving them a lot more credit than I would at this point.
Re:Moving towards a faster web by jefftk on Monday November 11, 2019 @10:02PM (#21511184)
Visit an AMP page in Lighthouse and you won't see an especially good score. Lighthouse doesn't special-case AMP or pick metrics that would make AMP look good.
Re:Moving towards a faster web by adrianN on Tuesday November 12, 2019 @12:33AM (#21511774)
Just because a monopoly is not acting maliciously today, that doesn't mean that it won't tomorrow.
Re:Moving towards a faster web by dredmorbius on Monday November 11, 2019 @08:18PM (#21510635)
In the United States, the role of a central bank is to manage two measures: inflation and unemployment.

The US Federal Reserve Bank does not measure inflation or unemployment. Rather, the US Department of Labour, an independent organisation (and a branch of government rather than a freestanding entity) computes both measures.

This is the principle of division of responsibility and measurement or judgement. You cut, I choose.

Google are both measuring, and rewarding, website performance, as well as designing and distributing the principle tools that benefit by both choices. That's an extreme locus of power. And, history shows, generally a Bad Idea which Ends Poorly.

Re:Moving towards a faster web by mr__y on Tuesday November 12, 2019 @06:44AM (#21513350)
>Google are both measuring, and rewarding, website performance, as well as designing and distributing the principle tools

Also given their market share as a search engine, they also get to decide which websites you will be able to "discover" additionally incorporating their performance metrics into their website ranking. So not only a website will get a "slow badge" but will also be downranked into oblivion.

Re:Moving towards a faster web by themoonbus on Monday November 11, 2019 @04:10PM (#21508937)
Because Google is the decider of what constitutes "slow"? You have a single organization deciding what the threshold is between slow and fast. And, they also have a Google-approved solution (amp) that I'm sure they will tie into the recommended actions for "slow" pages.

I'm not saying it's a walled garden (that's a more extreme situation on the continuum between open and closed), I was just using the phrase to illustrate my point that the end-user experience isn't the only factor to consider.

Re:Moving towards a faster web by tomComb on Monday November 11, 2019 @04:07PM (#21508913)
If Google didn't have a long history of this sort of thing (interpret that as you may) the open web would have lost the battle for mainstream users to the proprietary platforms long ago.
Re:Moving towards a faster web by themoonbus on Monday November 11, 2019 @04:12PM (#21508962)
I don't love using slippery slope arguments, but I feel that it's appropriate here...
Re:Moving towards a faster web by _bxg1 on Monday November 11, 2019 @03:54PM (#21508818)
It reads to me as an attempt from Google to further shame people into following better practices, like when they started factoring HTTPS into search rankings.

I think the principle is a fine one (though it is a bit odd considering the web's main source of slowness is ads/tracking tech, and... that's Google's main business). But in practice I'd bet that - like most of Google's broad-strokes efforts - there will be many edge cases/outliers where people get penalized unjustly, and there won't be an appeals process.

Re:Moving towards a faster web by codyogden on Monday November 11, 2019 @04:03PM (#21508884)
> further shame people into following better practices

"Better" as prescribed by who? At this point, I'm under the impression that if you're not implementing AMP for content, Google is going to rank you lower and now publicly shame you to users. They _say_ this is not the case, but it's impossible to ignore now that they're introducing naming and shaming. It just seems like features way outside the scope of what a web browser should be providing to users.

Editing to add my other thought:

I've built websites that routinely score horribly on Google's proprietary PageSpeed Insights despite fixing everything within my power (usually Google's own analytics scripts score badly), but also score very high on every other reasonable industry test of similar nature. It's hard to convince me that they alone should be an arbiter for this type of feedback given to users.

Re:Moving towards a faster web by jefftk on Monday November 11, 2019 @05:54PM (#21509804)
> Google's proprietary PageSpeed Insights

The previous version of PageSpeed Insights was open source (https://github.com/pagespeed/page-speed) and the current version is a wrapper around Lighthouse which is also open source (https://github.com/GoogleChrome/lighthouse).

(Disclosure: I work for Google)

Re:Moving towards a faster web by codyogden on Monday November 11, 2019 @07:38PM (#21510421)
I believe you, obviously. I have historically received drastically different results between, for example, web.dev / Lighthouse and PageSpeed Insights with the latter outputting a very low arbitrary 'rating' or 'score' and the former providing results I would expect. Like a lot of efforts at Google, things seem duplicated. As an outsider, it is a frustrating experience catering to Google's performance ideals because the tools and 'best practice' positions do not seem to be unified in one place.
Re:Moving towards a faster web by jefftk on Monday November 11, 2019 @08:06PM (#21510566)
I wonder if you might have had a bad experience with the old rules-based PageSpeed Insights? It wasn't as good as the current one, being more of a checklist of "have you done all these things that usually help" and not "we loaded the page, computed metrics, and this is how well it did".
Re:Moving towards a faster web by processing on Monday November 11, 2019 @06:03PM (#21509872)
I just checked one of my sites with their tools. Performance 34/100. Biggest issue Google's own ad tech. Third party code blocking the main thread.

https://imgur.com/a/RM8JkbI

Re:Moving towards a faster web by _bxg1 on Monday November 11, 2019 @06:42PM (#21510140)
Yep. Looking at it cynically, this could be a way of playing hard-ball with web admins: "if you want to keep using Google stuff, and you don't want this badge of shame, you better use AMP"
Re:Moving towards a faster web by vast on Monday November 11, 2019 @07:29PM (#21510374)
This is Googles blueprint to eradicate apple. They want Web apps to dominate because they already have a standing there and apple has a large marketshare in native apps.
Re:Moving towards a faster web by tannhaeuser on Monday November 11, 2019 @08:41PM (#21510763)
I will agree with you that Google has killed the web, news groups, federated chat, and so many other things, but I find the term "balkanization" both very disrespectful and at the same time a bad fit for describing Google subverting nearly all communication channels.