Live data from Hacker News

Web.dev by Google

web.dev

141–150 of 264 posts

Re: Web.dev by Google

#141
post #6

Earlier quoted context omitted.

Precisely the opposite -- it's going to be available for open registration soon. https://get.dev/

Do you have to use Google's registrar service? That page isn't clear, and if you have to use Google's service, I don't view that as a good precedent.

Correct me if I'm wrong, but registries can't let single registrars have exclusive access to TLDs. If Alphabet/Google were to do this it would be antitrust, and they could lose their dual registry/registrar status.

Re: Web.dev by Google

#143

Why am I getting: Error: 403 from Lighthouse API: Forbidden whenever I try to run the audit on any of my sites hosted on Digital Ocean? They all load normally in my browser... Anyone else having the same issue?

Probably an issue with the actual scanning service. web.dev itself gets the same error.

Re: Web.dev by Google

#144

Why am I getting: Error: 403 from Lighthouse API: Forbidden whenever I try to run the audit on any of my sites hosted on Digital Ocean? They all load normally in my browser... Anyone else having the same issue?

I have a feeling they've hit some kind of API limit for their own Lighthouse service ironically.

Re: Web.dev by Google

#145

I just ran their audit to https://mail.google.com , you guys (googlers) need to speed up your websites first, Gmail is terrible slow lately, just saying...

Google's pagespeed service is hot garbage. You can do things that make the page load significantly slower and get a perfect score than if you had a lower pagespeed score with a much faster page load. I also find it strange how I can get an A on every other page speed service, including GTMetrix, but get an F on Google's tes(s). Totally useless.

I said this in reply to QUIC apparently ignoring hardware TLS offload...

Is this for real?

Even Quick Assist?

I am watching the internet be developed by the giants for the giants. In my memory, giants didn't act like giants. "At scale" wasn't a preprocessor. Browser developer tools were written to help you participate in conversation, not play unending catch up in translation, the meaning lost in acoustics of auditoria for the life of me I would think giants could make intelligible.

Re: Web.dev by Google

#146
post #127

Earlier quoted context omitted.

Recent Ad Words user here. It is quite possibly the worst application I've used in years. I get that they offer a LOT of products and that the nature of the business is complicated. But, man, was everything about that process awful. And the UI is unbearably slow.

I agree, it’s painful, but the new AdWords UI is still far ahead of the old one.

They don't want users. They need the layer of apologists to obscure the grand systematic internalisation game. SI is subject to financial services law in the UK, at least...

Re: Web.dev by Google

#147

Why am I getting: Error: 403 from Lighthouse API: Forbidden whenever I try to run the audit on any of my sites hosted on Digital Ocean? They all load normally in my browser... Anyone else having the same issue?

I got a "no such site" first and then this 403 error.

Re: Web.dev by Google

#148

Why am I getting: Error: 403 from Lighthouse API: Forbidden whenever I try to run the audit on any of my sites hosted on Digital Ocean? They all load normally in my browser... Anyone else having the same issue?

Ironically, my static site hosted on Google Cloud Storage is returning 403 Forbidden.

Re: Web.dev by Google

#149
post #118

Earlier quoted context omitted.

I think it is in poor taste for Google to publish https://web.dev/ during the new desktop Gmail. >Google's web platform team has spent over a decade learning about user needs. Now we want to make it as easy as possible for you to master the defining standards of web development today. >Fast load times >Guarantee your site loads quickly to avoid user drop off. "Loading Gmail" >Network resilience >See consistent, relia…

A Gmail account has has 10+GB of data. Users for the most part don't want 10GB in browser local storage. Gmail's speed problems are in the backend, not the web UI.

what you've written is totally false. It worked fine on the old UI, and also still works fine in simple HTML mode.

You can see this yourself here: http://mail.google.com/mail/h/ (direct link to html view. you have to already be signed in for this link to work.)

Side note: I'm sure you would have mentioned it, but you don't happen to work at Google on the new Gmail front-end, do you? (Since I could see someone who is, trying to deflect blame for their current bugs by "blaming the back-end".) Just want to make sure...

Post reply on HN