71–80 of 264 posts
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.
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.
how's this any different than devs using 123.123.123.123 for test purposes (instead of private network addresses), then getting upset when they found out it has been allocated to China Unicom?
Earlier quoted context omitted.
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?
tracking
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)
Getting 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 got a ERR_SSL_VERSION_INTERFERENCE briefly before the page successfully reloading. I have uBlock Origin installed, so it may be it.
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…
There have been news since February.
UWP hosted apps got replaced with PWAs, including access to UWP APIs if signed, documentation and tooling support is now available.
https://developer.microsoft.com/en-us/windows/pwa
https://docs.microsoft.com/en-us/microsoft-edge/progressive-...
This is what made me have another look at PWAs, start experimenting with them and starting to see, that for plain CRUD applications PWAs are probably the way to go.
Earlier 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.
> Error: 500 from Lighthouse API: Internal Server Error
ICANN were foolish to go down the new TLD root. Why should Google have ownership over web.dev, and not mozilla (MDN) or w3c?