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.
Or the Google Cloud Platform
Web.dev by Google
111–120 of 264 posts
Re: Web.dev by Google
#112Earlier quoted context omitted.
Meh, these tests are just good ways to find obvious problems with your site. Fixating on the overall score seems like an indication of a different problem. For example, you can't change the caching behavior of google-analytics.js, and it's usually intractable to split apart your CSS to optimize for above-the-fold content. Oh well, you didn't get a perfect score. Stay practical.
Try selling that to a client that keeps using the test against a site that is A rated everywhere else because Google's brand has fooled them into thinking a perfect score means better SEO.
Right, that would be an example of a "different problem."
I'd be hard pressed to let stupid things client/managers can do direct how this sort of tool should work. For example, it'd be silly to demand "score inflation" just because your client is unreasonable. Or rather, if a client is making your life hard, I don't think it's the world that needs to change.
What's your solution if your client measures your success by punching their website into https://www.worthofweb.com/calculator/? And doesn't take you seriously enough to listen to you in general?
Re: Web.dev by Google
#113Looks 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.
Plus it’s open source and welcomes contributions https://webhint.io/docs/contributor-guide/
Re: Web.dev by Google
#114Earlier quoted context omitted.
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"
Same for my Cloudflare-fronted Appengine site.
Re: Web.dev by Google
#115Earlier quoted context omitted.
> 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.…
> The cookie notice only appeared after I refreshed
Maybe it's a geo thing. Are you in Europe? I see no cookie notice (US).
> I know they're strong words, but someone needed to say it.
Eh, it needs to be there but don't throw the baby out with the bathwater. It's apparently in "beta" and according to this hn thread robdodson is working on it, so odds are the accessibility section will be handled just fine.
Regardless
> Those who preach are held to higher standards
is a bad take. You can criticize a tutorial site without standing on such a flimsy soapbox.
Re: Web.dev by Google
#116ICANN were foolish to go down the new TLD root. Why should Google have ownership over web.dev, and not mozilla (MDN) or w3c?
Foolish how? Sure, it kind of ruins DNS, but ICANN made a lot of money, and isn’t that the important thing?
Re: Web.dev by Google
#117Earlier quoted context omitted.
When Gmail first came out I was amazed at how fast it was, so much faster than the native outlook client I used at the time, wow! How is that even possible in javascript! Now gmail is slower than most any other website I use regularly. Can't even refresh the inbox in less than three seconds. I've noticed the same slower by a bit every year pattern with google maps too. I'm afraid to click anything when I have a map o…
The difference in performance between Fastmail and the new Gmail interface right now is freaking stunning. I still load Gmail every few days to see if I have email there, and it's like waiting for Windows 98 to boot.
The main Gmail desktop website is sort of like a desktop application. Most active users keep it permanently open. Try https://mail.google.com/mail/u/0/x/ , https://mail.google.com/mail/u/0/h/ or https://mail.google.com/mail/u/0/mu/ (on mobile these will redirect unless you enable "request desktop site")
Re: Web.dev by Google
#118I 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, 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.
Re: Web.dev by Google
#119In case you're wondering what's in it for google with PWAs/App manifests/"Installable apps"[0], it's answered in another recent HN post[1] and comment[2].
I wrote and deleted a pretty vitriolic comment about not trusting google as stewards of anything, people who care about the user (outside of selling data/access to the user millions of times a second), but I couldn't figure out why they would push app manifests (the only interesting part of the actual comment).
[0]: https://web.dev/installable
Re: Web.dev by Google
#120Error: 403 from Lighthouse API: Forbidden
If you're using Cloudflare.