Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Web.dev by Google

web.dev

Post reply on HN
Print view View original

91–100 of 264 posts

Re: Web.dev by Google

#91

Post by exodust »

modernerd wrote: post #90

Web.dev looks incredible for educating web developers, exposing Lighthouse to devs who aren't already familiar with it, and for automating basic website testing over time. But it will be a nightmare for support teams working at any kind of web service. As Google doesn't provide support for this tooling and site owners invariably fixate on the scores it provides, product support teams for everything from WordPress the…

But it's a resource for web devs, mostly used by web devs. Reinforced by the web.dev domain name, which surprised me. I've never seen .dev domain before.

All audit tools make recommendations that many of us will ignore. I have zero intention of using webp images for example.

I don't think your claim that "nightmares" will happen is warranted. Shiny new site audit tools are fun. Enjoy it, there's no nightmare!

Re: Web.dev by Google

#92

Post by logicallee »

yandrypozo wrote: post #18

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...

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, reliable performance regardless of network quality.

"Loading..." (in yellow at the top, after clicking a search result. Indefinitely.)

(some other non-quoted parts are OK)

>Accessible to all

>[Build] a site that works for all of your users.

Re: Web.dev by Google

#93

Post by alib »

This site didn't load properly in Firefox on a Samsung Galaxy S8 just now, and the accessibility section is "coming soon". I'm sorry Google, but if you're letting key basics like this slip... Accessibility is not a bolt-on for afters, and chrome isn't the only web browser. Deep down you know this too. Those who preach are held to higher standards, and you've let yourselves down badly here.

Re: Web.dev by Google

#94

Post by exodust »

NelsonMinar wrote: post #53

Talk about breaking the back button! Do a measurement on a website. Then click one of the Guide links like "Links do not have a discernible name". Page navigates away from the report to some documentation. Click back, report is gone. I get it, it's a single page webapp. But if you do that you need to make all the simple navigations open new tabs. There is a "open link in new button" icon next to each link, but that's…

Good to see someone else mention this, and also for the Google web.dev.dev to reply.

Re: Web.dev by Google

#95

Post by arendtio »

tinyvm wrote: post #28

Google is really pushing Hard on PWA. My biggest concern is the support outside of chrome. While other browsers tend to come on pair with chrome in terms of features , chrome right now is the only one which supports PWA as "native" app.. Windows announced support for PWA natively a while ago [0] but there has been no news since then. On Apple side it's silence radio...iOS have some support but for Mac it seems unlike…

> chrome right now is the only one which supports PWA as "native" app..

What do you mean with "'native' app" exactly? When I use my PWA with a Firefox on Android I can't see that it is a PWA. It just looks like any other Andoird app.

Granted that is only one more browser and on the desktop side Firefox still has a lot to do, but at least there is one more player in the race ;-)

Re: Web.dev by Google

#98

Post by magicalist »

alib wrote: post #93

This site didn't load properly in Firefox on a Samsung Galaxy S8 just now, and the accessibility section is "coming soon". I'm sorry Google, but if you're letting key basics like this slip... Accessibility is not a bolt-on for afters, and chrome isn't the only web browser. Deep down you know this too. Those who preach are held to higher standards, and you've let yourselves down badly here.

> This site didn't load properly in Firefox on a Samsung Galaxy S8 just now

Check your extensions. It loads fine for me.

> you've let yourselves down badly here.

...because an article on accessibility is "coming soon"?

Re: Web.dev by Google

#99

Post by stupidbird »

I can't wait for one of the executives in my company to run into this, understand nothing but the numbers, and then complain about our numbers not being higher despite the fact that half of these metrics aren't applicable to our web app.

I already have a boilerplate response to "why isn't our google pagespeed score higher" that I copy and paste.

I know Google's happy about performance nagging, but I wish they were better at knowing what is/isn't applicable.

Re: Web.dev by Google

#100

Post by fantyoon »

philtar wrote: post #87
jopsen wrote: post #73

Earlier quoted context omitted.

https://developers.google.com/fonts/faq#what_does_using_the_... I'm no lawyer, but I read that as it is not used for tracking users. (full disclosure: I work at Google, on something unrelated)

Do you have a guess why those assets are not cached more aggressively?

This is a complete guess but I suppose one request everyday would be enough to get atleast some idea of how popular any given font is. The page says its to keep them updated but I highly doubt that would be the reason.
Post reply on HN