Live data from Hacker News

Web.dev by Google

web.dev

51–60 of 264 posts

Re: Web.dev by Google

#51

This looks kinda cool. I have a hard time believing this is "for web developers" when most web developers used `.dev` for local development, which was broken because Google decided they wanted to own `.dev` for themselves. Bad taste in my mouth.

It might be time to let this one go.

Re: Web.dev by Google

#52

It only accepts https URLs. Lighthouse in the DevTools can do both, http and https.

Yep that's our mistake (one of the web.dev devs). We auto added https to every URL. Oops! Gonna fix that as soon as we are out of our code freeze

> one of the web.dev devs

web.dev^2

Re: Web.dev by Google

#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 really not good enough.

Re: Web.dev by Google

#54

It only accepts https URLs. Lighthouse in the DevTools can do both, http and https.

Yep that's our mistake (one of the web.dev devs). We auto added https to every URL. Oops! Gonna fix that as soon as we are out of our code freeze

I assumed that was intentional to push everyone to use https.

Re: Web.dev by Google

#57

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…

Ah yeah that's something we want to fix. If you're signed in it keeps the report around but if you're signed-out it's stateless. It's definitely on our to-do list to fix.

Re: Web.dev by Google

#58

This looks kinda cool. I have a hard time believing this is "for web developers" when most web developers used `.dev` for local development, which was broken because Google decided they wanted to own `.dev` for themselves. Bad taste in my mouth.

It might be time to let this one go.

Some of us are still tickets once a month or so over this. Kinda hard to let it go.

Re: Web.dev by Google

#59

Will someone please elucidate which Google resources are still relevant? * https://web.dev/ * https://developers.google.com/speed/ * https://developers.google.com/web/ (including https://developers.google.com/web/tools/lighthouse/ )

Heyo! One of the web.dev devs here. The new web.dev site is an experiment from our team to see if we can improve the interactivity of our docs. We link to developers.google.com/web in a number of places. Over time, if folks seem to enjoy the web.dev model, we may explore moving more of our docs over there. But for now it's just a fun experiment

I like that material design. Can you share the tech stack it was built with?

Re: Web.dev by Google

#60

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.

Google Pagespeed once recommended that I enable gzip compression on an embedded Google map.

https://johnrockefeller.net/google-pagespeed-_/

Post reply on HN