Wow amazon.com results are quite impressive. Have not thought it has 95 performance.
Web.dev by Google
171–180 of 264 posts
Re: Web.dev by Google
#172This is powered by Google Lighthouse, with the benefit of it being done via a web UI instead of a Dev Tools Audit. Which is both good and bad. Good because Lighthouse has some reasonable best practices to follow, and a few good performance timings, so lowering the barriers of entry is nice. Bad because many of Lighthouses best practices aren't always applicable (our major media customers constantly say "stop telling…
Why don't you want to implement a basic service worker? A couple of cache strategies among these ones seem like a net positive? https://developers.google.com/web/fundamentals/instant-and-o... (ex: "Cache, falling back to network" for CDN'd libraries, "Cache then network" for content like news articles)
Standard caching headers should be enough?
Re: Web.dev by Google
#173I 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...
>Gmail is terrible slow lately, just saying...
Recently I started using the html only version of Gmail because for my user case is faster than the web app.
Re: Web.dev by Google
#174Google 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…
PWA is "Progressive Web Applications".
Re: Web.dev by Google
#175I get the message "Error: 500 from Lighthouse API: Internal Server Error" when I try to run audit for my personal website https://tonnygaric.com
Anyone any clue why? Other websites I enter seem to run without a problem.
Re: Web.dev by Google
#176Earlier 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…
Not web dev related, but related to Google not focusing on performance: the latest Android release of Google Maps is actually non-functional on my Galaxy S7 because of how slow it is. It completely overloads RAM and crashes. Every time. Hilarious.
Gosh, thanks for this note! I thought it was just me and my 2.5 years old HTC that can't keep up. It is totally unusable as you say, for a few weeks now (crashes, slow, markers/directions not show at all while the app thinks it does)...
Re: Web.dev by Google
#177This is just lighthouse? You can run these tests in chrome under dev tools > audit.
Re: Web.dev by Google
#178This is useless to me because I have a website, not a web application. I got a 46/100 on PWA which is astonishing because the site being tested is not a progressive web application at all. Imagine vim getting a 40/100 score in the category of web browsers. Weirdly good score.
The accessibility audit is garbage as well. Apparently I should add an image to the site just so I can put an alt attribute in it. I should include audio so I could have a transcription to go with it. Not sure whether Lighthouse decided that 16px or 20px is less than 12px but apparently one of them is and makes up over 60% of the page.
I understand this is not made for people who serve static HTML files and handmade CSS from ~/sites/ but I'm pretty sure I hate the kinds of sites this is designed for. Should have a custom splash screen? Respond with 200 when offline? What's next, I get points for breaking the back button too? Why is using HTTPS and redirecting HTTP to it a PWA thing?
I'd hate to see the site that aces this audit.
Re: Web.dev by Google
#179> Easily discoverable
Ensure users can find your site easily through search.
> Installable
Be on users’ home screens with no need for an app store.
It's nice that they educate devs on the rules they themselves came up with. I just wouldn't call it "how to build a better web" then.
Re: Web.dev by Google
#180Getting Chrome SSL warnings on both the OP link and https://get.dev/ Doesn't really evoke confidence, if this is a Google initiative. Can someone post a short precis as to what this is about for those of us who cannot visit the URLs? UPDATE: Apologies - My bad, not Google's fault. I had a local Valet/NGINX redirect for local .dev domains setup for Laravel development projects that was causing the issue.
I get DNS error here. *.dev is probably reserved for local domains by admins. Not the greatest choice of tld for real sites.