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

101–110 of 264 posts

Re: Web.dev by Google

#101

Post by hornetblack »

"Imagine if your favorite game took forever to load because you were on a slow network connection, it wouldn't be your favorite game for very long. "

I can inform you that games I play take forever to load on slow networks. (Overwatch, Darksouls). Although I guess it's not downloading the game. It's just trying to login to the servers.

Re: Web.dev by Google

#102

Post by hanoz »

e40 wrote: post #65
sumoboy wrote: post #50

Earlier quoted context omitted.

You think gmail is slow, try the new adwords interface.

Or the g suite admin console. Cripes, it's insanely frustrating to use.

Google seems to be increasingly giving the impression of collapsing under its own weight.

Re: Web.dev by Google

#103

Post by m3nu »

partiallypro wrote: post #23
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...

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.

Doesn't work against my S3-hosted static site?

"Error: 500 from Lighthouse API: Internal Server Error"

Re: Web.dev by Google

#105

Post by skunkworker »

If you have an old version of Pow installed. Make sure to either upgrade to Puma-dev (Which moves .dev to .test, the correct subdomain for local machine testing) or uninstall it first.

Re: Web.dev by Google

#106

Post by scrame »

I tried my rather large work website and it was unable to fetch it after a couple tries.

Also this is the same company that brought us AMP and didn't use closing tags on their landing page to "save bandwidth", and tried to push a java -> JavaScript nightmare of a gui toolkit. I don't get why they are trying to push for this unless it's trying to strongarm devs into making more shitty AMP pages.

Re: Web.dev by Google

#107

Post by feb »

fhdhehfhzhe wrote: post #97

Looks like this - https://webhint.io Why not collaborate with the people who’ve made this first, google?

The similarities with webhint are striking. For example they have mostly the same categories :

* Performance (exactly same as webhint)

* PWA (exactly same name as webhint)

* Accessibility (exactly same as webhint)

* Best Practices

* SEO

Webhint also has categories Interoperability and Security. Not sure what web.dev uses for those.

Re: Web.dev by Google

#108

Post by alib »

magicalist wrote: post #98
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"?

I can't replicate it in private browsing. I'm not running any mobile extensions and my internet is as good as it comes. First time I loaded it the blue line at the top was there for ages. I was scrolling the site for a good 20 secs marvelling at the irony of a site teaching performance not performing. It felt like something to do with the service worker not working. The cookie notice only appeared after I refreshed. Now it works fine, and loads fine each time. So it was something to do with the initial caching of assets.

And yes, the accessibility section coming soon sends the wrong message very subtly but powerfully. It's something we all need to be better at, and when you've got the resources of Google there just isn't any excuse. Those two small words on that missing section quietly absolve us all. Because if Google can't do it right, why should we? It just isn't good enough, so yes, they have let themselves and our community down. I know they're strong words, but someone needed to say it.

Re: Web.dev by Google

#109

Post by tehlike »

arkitaip wrote: post #63
rocky1138 wrote: post #60

Earlier quoted context omitted.

Google Pagespeed once recommended that I enable gzip compression on an embedded Google map. https://johnrockefeller.net/google-pagespeed-_/

Most performance profilers will penalize you for embedding Google Analytics and Google Fonts because they have poor caching settings. What's so important about those resources that they can't be cached for longer periods?

Easier bug fix presumably. Meaning if there is a bad release url is cached for little. If urls were versioned and were changable by google, it would have been done.

https://www.google-analytics.com/analytics.js

Google cannot bust this in case of a bug. They can mitigate this by having a loader with built in functionality that always looks out for "is there a newer version" but that has its limitations.

Post reply on HN