TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Web.dev by Google

699 点作者 mxschumacher超过 6 年前

62 条评论

bitofhope超过 6 年前
This is useless to me because I have a website, not a web application. I got a 46&#x2F;100 on PWA which is astonishing because the site being tested is not a progressive web application at all. Imagine vim getting a 40&#x2F;100 score in the category of web browsers. Weirdly good score.<p>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.<p>I understand this is not made for people who serve static HTML files and handmade CSS from ~&#x2F;sites&#x2F; but I&#x27;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&#x27;s next, I get points for breaking the back button too? Why is using HTTPS and redirecting HTTP to it a PWA thing?<p>I&#x27;d hate to see the site that aces this audit.
评论 #18439804 未加载
评论 #18442686 未加载
评论 #18442214 未加载
评论 #18471838 未加载
评论 #18440565 未加载
评论 #18441663 未加载
评论 #18462999 未加载
评论 #18440722 未加载
yandrypozo超过 6 年前
I just ran their audit to <a href="https:&#x2F;&#x2F;mail.google.com" rel="nofollow">https:&#x2F;&#x2F;mail.google.com</a>, you guys (googlers) need to speed up your websites first, Gmail is terrible slow lately, just saying...
评论 #18435970 未加载
评论 #18436035 未加载
评论 #18436688 未加载
评论 #18437158 未加载
评论 #18436362 未加载
评论 #18439317 未加载
评论 #18439426 未加载
评论 #18436292 未加载
评论 #18438867 未加载
评论 #18437791 未加载
billyhoffman超过 6 年前
This 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.<p>Good because Lighthouse has some reasonable best practices to follow, and a few good performance timings, so lowering the barriers of entry is nice.<p>Bad because many of Lighthouses best practices aren&#x27;t always applicable (our major media customers constantly say &quot;stop telling me a need a #$%ing Service Worker!&quot;). And while Speed Index and Start Render are great, Time-to-interactive, First CPU idle, and estimated keyboard latency are still fairly fluid&#x2F;poorly defined, and of different value.<p>This all also overlooks the value that something like the Browser&#x27;s User Timings provides (Stop trying to figure out what&#x27;s a &quot;contentful&quot; or &quot;meaningful&quot; paint, and let me just use performance.mark to tell you &quot;my hero image finished and the CTA click handler registered at X&quot;), which Lighthouse doesn&#x27;t surface up.<p>What is interesting is the monitoring side. WebPageTest, Lighthouse, Page Speed Insights, YSlow, etc are just point-in-time assessments that is largely commoditized. Tracking this stuff over time and extracting meaningful data is valuable, so that&#x27;s pretty cool.<p>Disclaimer: I work in the web performance space. People replace homegrown Lighthouse, puppeteer, or WPT instances with our commercial software, so I&#x27;m biased. However I like a lot of the raising awareness and trail blazing about what Performance&#x2F;UX means that Google is doing.
评论 #18436916 未加载
评论 #18442877 未加载
评论 #18436659 未加载
zwaps超过 6 年前
PLEASE PLEASE PLEASE WEBDEVS, STOP LOADING YOUR WEBSITE WITH CRAP TO MAKE THEM BETTER<p>I fed a large news site that is not terrible to use into this, and it gave it 14&#x2F;100 rating. This news site is perfectly fine, has a good design, good typography and loads without any scripts if you need it to. It loads quite fast.<p>Among other things, Google recommends - Lazy loading: NOOOO, just load my document. I hate this bullcrap. It never works correctly and then you just get a laggy and slow scrolling site where you have to wait all the time you use it. It&#x27;s a news site. Just load the whole thing, it takes a couple of ms but then the site is actually usable! It&#x27;s an actual document you can scroll through.<p>- Ask the user to install as an app, add offline usage etc? Why even?<p>- Dynamically compress everything? YES GOOGLE, when saving 8kb per picture, but in the end we need to pull 10mb of javascript libraries from sixty different sources all over the web to even display a text with one small picture ITS ALL WORTH IT<p>I don&#x27;t make websites except my personal stuff. I understand you want to present your knowledge and skills. But please, the websites are getting worse and worse. The best way to present almost any information is in a classic html webpage. It wouldn&#x27;t need to be like this, but almost any modern websdesign approach seemingly leads to slow, laggy and partly unusable websites, that do end up loading something, but often not the thing I actually want to read.<p>I am actually trained now to feel a sense of relief if I come across a straight html website, just because the user experience is so terrible now thanks to javascript.<p>As a consumer, I will continue to beg for simple websites that stay true to the idea of displaying a scrollable document with data and text.<p>Please, only use all these animations, loadings, dynamics, off-site frameworks, custom browser controls and single page documents if you are making a) a portfolio b) an actual application that is mostly simple buttons and does not present significant amounts of text or data<p>thank you<p>its bad guys
评论 #18441723 未加载
NelsonMinar超过 6 年前
Talk about breaking the back button! Do a measurement on a website. Then click one of the Guide links like &quot;Links do not have a discernible name&quot;. Page navigates away from the report to some documentation. Click back, report is gone.<p>I get it, it&#x27;s a single page webapp. But if you do that you need to make all the simple navigations open new tabs. There is a &quot;open link in new button&quot; icon next to each link, but that&#x27;s really not good enough.
评论 #18436558 未加载
评论 #18440088 未加载
评论 #18437186 未加载
alib超过 6 年前
This site didn&#x27;t load properly in Firefox on a Samsung Galaxy S8 just now, and the accessibility section is &quot;coming soon&quot;. I&#x27;m sorry Google, but if you&#x27;re letting key basics like this slip... Accessibility is not a bolt-on for afters, and chrome isn&#x27;t the only web browser. Deep down you know this too. Those who preach are held to higher standards, and you&#x27;ve let yourselves down badly here.
评论 #18437234 未加载
tinyvm超过 6 年前
Google is really pushing Hard on PWA.<p>My biggest concern is the support outside of chrome.<p>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 &quot;native&quot; app..<p>Windows announced support for PWA natively a while ago [0] but there has been no news since then.<p>On Apple side it&#x27;s silence radio...iOS have some support but for Mac it seems unlikely to happen...<p>[0]<a href="https:&#x2F;&#x2F;blogs.windows.com&#x2F;msedgedev&#x2F;2018&#x2F;02&#x2F;06&#x2F;welcoming-progressive-web-apps-edge-windows-10&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blogs.windows.com&#x2F;msedgedev&#x2F;2018&#x2F;02&#x2F;06&#x2F;welcoming-pro...</a>
评论 #18436847 未加载
评论 #18436776 未加载
评论 #18436145 未加载
评论 #18439430 未加载
评论 #18437200 未加载
crazygringo超过 6 年前
Why am I getting:<p>Error: 403 from Lighthouse API: Forbidden<p>whenever I try to run the audit on any of my sites hosted on Digital Ocean? They all load normally in my browser...<p>Anyone else having the same issue?
评论 #18437864 未加载
评论 #18437749 未加载
评论 #18437859 未加载
评论 #18438027 未加载
评论 #18437937 未加载
评论 #18437628 未加载
评论 #18437688 未加载
iambateman超过 6 年前
This looks kinda cool.<p>I have a hard time believing this is &quot;for web developers&quot; when most web developers used `.dev` for local development, which was broken because Google decided they wanted to own `.dev` for themselves.<p>Bad taste in my mouth.
评论 #18435982 未加载
评论 #18436730 未加载
评论 #18436400 未加载
stupidbird超过 6 年前
I can&#x27;t wait for one of the executives in my company to run into this, understand nothing but the numbers, and then complain about our numbers not being higher despite the fact that half of these metrics aren&#x27;t applicable to our web app.<p>I already have a boilerplate response to &quot;why isn&#x27;t our google pagespeed score higher&quot; that I copy and paste.<p>I know Google&#x27;s happy about performance nagging, but I wish they were better at knowing what is&#x2F;isn&#x27;t applicable.
评论 #18443077 未加载
amaccuish超过 6 年前
ICANN were foolish to go down the new TLD root. Why should Google have ownership over web.dev, and not mozilla (MDN) or w3c?
评论 #18437515 未加载
评论 #18439240 未加载
评论 #18436844 未加载
评论 #18438440 未加载
paulddraper超过 6 年前
Will someone please elucidate which Google resources are still relevant?<p>* <a href="https:&#x2F;&#x2F;web.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;web.dev&#x2F;</a><p>* <a href="https:&#x2F;&#x2F;developers.google.com&#x2F;speed&#x2F;" rel="nofollow">https:&#x2F;&#x2F;developers.google.com&#x2F;speed&#x2F;</a><p>* <a href="https:&#x2F;&#x2F;developers.google.com&#x2F;web&#x2F;" rel="nofollow">https:&#x2F;&#x2F;developers.google.com&#x2F;web&#x2F;</a> (including <a href="https:&#x2F;&#x2F;developers.google.com&#x2F;web&#x2F;tools&#x2F;lighthouse&#x2F;" rel="nofollow">https:&#x2F;&#x2F;developers.google.com&#x2F;web&#x2F;tools&#x2F;lighthouse&#x2F;</a>)
评论 #18436170 未加载
xg15超过 6 年前
&gt; <i>Easily discoverable<p>Ensure users can find your site easily through search.</i><p>&gt; <i>Installable<p>Be on users’ home screens with no need for an app store.</i><p>It&#x27;s nice that they educate devs on the rules they themselves came up with. I just wouldn&#x27;t call it &quot;how to build a better web&quot; then.
arendtio超过 6 年前
&gt; Accessible to all - Coming Soon<p>Probably the frontend joke of the last two decades... And a bad one too.
fhdhehfhzhe超过 6 年前
Looks like this - <a href="https:&#x2F;&#x2F;webhint.io" rel="nofollow">https:&#x2F;&#x2F;webhint.io</a> Why not collaborate with the people who’ve made this first, google?
评论 #18437356 未加载
评论 #18438267 未加载
scrame超过 6 年前
I tried my rather large work website and it was unable to fetch it after a couple tries.<p>Also this is the same company that brought us AMP and didn&#x27;t use closing tags on their landing page to &quot;save bandwidth&quot;, and tried to push a java -&gt; JavaScript nightmare of a gui toolkit. I don&#x27;t get why they are trying to push for this unless it&#x27;s trying to strongarm devs into making more shitty AMP pages.
RugnirViking超过 6 年前
The hacker news homepage gets a 23 on accessibility (Idk I mean there are probably some issues I hadn&#x27;t thought of but the fact that its primariliy no-nonsense text makes it quite accessible by default)<p>It does however get 100 on performance (quite rightly) The PWA score is around 50 but most of the complaints are really silly. It almost makes me wonder if the entire category of PWA is silly.<p>Finally, I checked GOV.UK, the website so lauded here on hacker news as of late. It also got around 58 on PWA - what is the point? If those complaints for PWA actually meant anything, surely they could fit into one of accessibility, best practises, or performance.
hornetblack超过 6 年前
&quot;Imagine if your favorite game took forever to load because you were on a slow network connection, it wouldn&#x27;t be your favorite game for very long. &quot;<p>I can inform you that games I play take forever to load on slow networks. (Overwatch, Darksouls). Although I guess it&#x27;s not downloading the game. It&#x27;s just trying to login to the servers.
Whitestrake超过 6 年前
I find myself disappointed that they took away `.dev` as local development TLD, and this is what they start using it for.
TonnyGaric超过 6 年前
I get the message &quot;Error: 500 from Lighthouse API: Internal Server Error&quot; when I try to run audit for my personal website <a href="https:&#x2F;&#x2F;tonnygaric.com" rel="nofollow">https:&#x2F;&#x2F;tonnygaric.com</a><p>Anyone any clue why? Other websites I enter seem to run without a problem.
pestkranker超过 6 年前
It&#x27;s actually Lighthouse under the hood.
评论 #18435843 未加载
apatheticonion超过 6 年前
Tried to run it on my site and got &quot;Error: 403 from Lighthouse API: Forbidden&quot;
seanhunter超过 6 年前
I&#x27;m amazed by how far off-base they have managed to make this. The recommendations are bizarrely inaccurate.<p>1)it says that my (black) text doesn&#x27;t have sufficient contrast against my (white) background. 2)It says that my page could benefit from having more of its resources served by http 2 (more than 100% presumably). 3)It says that links should have a name (this is not supported by html5) 4)It says my (100% valid) robots.txt file is not valid 5)it says my 100% no javascript static webpage which isn&#x27;t a PWA should return a 200 when offline. Not sure how they think I should do that.
crooked-v超过 6 年前
I wonder how many things will break when .dev domains become broadly available.
评论 #18436104 未加载
d--b超过 6 年前
Interesting that they’re not selling AMP in there. They most likely didnt dare
评论 #18437857 未加载
nh2超过 6 年前
&gt; Accessible to all<p>The website itself doesn&#x27;t seem to take that too seriously.<p>For example, it loses scroll position when navigating:<p>* go there from HN * scroll down a bit * press the Back button in the browser to go back to HN * press the Forward button in the browser to go to the site again * you are now scrolled the very top again, instead of where you scrolled to<p>Tested in curren Chrome and Firefox on Linux.<p>Also note how HN doesn&#x27;t have this problem, it will remember your scroll position so you can continue reading where you left off.<p>Browsers are smart, they have accessibility built-in. Too clever JavaScriptery destroys it.
shinryuu超过 6 年前
I get that the site can&#x27;t be reached.. ? Is it a valid site?
评论 #18436350 未加载
评论 #18436315 未加载
cyberferret超过 6 年前
Getting Chrome SSL warnings on both the OP link and <a href="https:&#x2F;&#x2F;get.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;get.dev&#x2F;</a><p>Doesn&#x27;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?<p>UPDATE: Apologies - My bad, not Google&#x27;s fault. I had a local Valet&#x2F;NGINX redirect for local .dev domains setup for Laravel development projects that was causing the issue.
评论 #18435866 未加载
评论 #18435929 未加载
评论 #18439696 未加载
评论 #18435949 未加载
评论 #18435908 未加载
评论 #18436693 未加载
评论 #18435826 未加载
iamunr超过 6 年前
So sad to see .dev go. :(
评论 #18435595 未加载
评论 #18437809 未加载
weinzierl超过 6 年前
It only accepts https URLs. Lighthouse in the DevTools can do both, http and https.
评论 #18436155 未加载
robdodson超过 6 年前
Hey folks, I wanted to share a quick status update to let y&#x27;all know which issues we&#x27;re seeing and working on. Apologies for the hiccups and thank you all for trying the beta!<p><a href="https:&#x2F;&#x2F;medium.com&#x2F;dev-channel&#x2F;web-dev-status-update-11-12-18-f9b42a693f65" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;dev-channel&#x2F;web-dev-status-update-11-12-1...</a>
评论 #18440097 未加载
modernerd超过 6 年前
Web.dev looks incredible for educating web developers, exposing Lighthouse to devs who aren&#x27;t already familiar with it, and for automating basic website testing over time.<p>But it will be a nightmare for support teams working at any kind of web service.<p>As Google doesn&#x27;t provide support for this tooling and site owners invariably fixate on the scores it provides, product support teams for everything from WordPress themes to CDNs end up fielding support questions that Google should be helping with via resources pitched at the non-technical folks who inevitably use these tools (as well as, you know, help from an actual human support team).<p>As it stands, support teams will now be inundated with questions unrelated to their product from customers who have no interest or technical background to read the current educational sections of web.dev, and whose time would be better spent crafting landing pages, great content, or reducing the 38 social plugins they&#x27;re using instead of making all the dials turn green.<p>I can already foresee the support requests from the web.dev scores:<p>“Google says my WordPress site isn&#x27;t installable. Where&#x27;s the option for that in your theme?”<p>“Your website says Cloudflare improves load time. But my first meaningful paint time went up by 1.5 seconds after setting it up! I&#x27;m going to write bad reviews about you.”<p>“Google says I need to theme my browser&#x27;s address bar to match my branding. I added that tag they mention but don&#x27;t see any change in my browser.”<p>It&#x27;s great to build awareness of ways to make the web faster and better, but it needs to be backed with guidance that&#x27;s pitched at the ability of the people who will be using these automated testing tools.<p>For example, why not detect the technology behind the site and — for stuff like WordPress — recommend plugins or other tech-specific resources that could help fix problems like lack of image lazy-loading? There are lots of ways education could be enhanced for non-developers.
评论 #18437146 未加载
LolNoGenerics超过 6 年前
Over a decade of experience... with service workers! Nice trick, leave time travel to spock et al.
bhartzer超过 6 年前
There&#x27;s so much wrong with this report, it can be confusing to many people.<p>For example, some of what they&#x27;re calling &quot;SEO&quot; really has nothing to do with SEO. It should be checking: - if the page is crawlable - if there is a valid title tag - if there is a valid meta description tag - if there is a valid canonical tag<p>But instead, it checks for a valid viewport meta tag? And if the font sizes are legible? I could see that it might be an issue if the site is hiding text on the page, but viewport and font sizes really have nothing to do with SEO.
评论 #18441468 未加载
ramshanker超过 6 年前
Error: 403 from Lighthouse API: Forbidden
skunkworker超过 6 年前
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.
yoz-y超过 6 年前
I have a question. How can I really figure out whether my (static) website uses http2? The google audit tells me that I should use http2 for all of my resources but loading my site in Safari or Chrome shows me that it uses the h2 protocol. Or are these unrelated?<p>Weirdly it also points out that my elements have non-unique Ids which is false and the list of failing elements shows that, it looks like they are stopping their search at the colon character, but they should not.
pasta超过 6 年前
Has anyone viewed the report? It&#x27;s full of elements never used on the sites I checked.<p>While it is still in beta (like all Google products are) don&#x27;t take this serious.
masswerk超过 6 年前
Regarding accessibility: Are skip links still a thing, or has this been superseded by landmark roles? Is there still an advantage in using a link as compared to selecting a region?<p>Edit: Meaning, if I have already a main region, does adding a skip link to main actually complicate things?
mangatmodi超过 6 年前
The tool is having scaling issues due to their seemingly unexpected fame on HN - <a href="https:&#x2F;&#x2F;medium.com&#x2F;dev-channel&#x2F;web-dev-status-update-11-12-18-f9b42a693f65" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;dev-channel&#x2F;web-dev-status-update-11-12-1...</a>
thinkloop超过 6 年前
The results are significantly different from the lighthouse audit in chrome&#x27;s web developer tools, the latter shows my site as PWA compatible with great performance whereas this tool shows that my site is not PWA ready and has medium performance.
artiya4u超过 6 年前
Error: 403 from Lighthouse API: Forbidden If you&#x27;re using Cloudflare.
评论 #18437759 未加载
评论 #18437732 未加载
ithrewthat4351超过 6 年前
How about we just give back .dev for registration free? :)
评论 #18435604 未加载
k__超过 6 年前
Only works for HTTPS.
评论 #18436550 未加载
zimpenfish超过 6 年前
Bizarrely refuses to use HTTP&#x2F;2 to my nginx (curl, Firefox, Safari all use HTTP&#x2F;2 happily) and then dings me for it. Seems a bit unfair.
stabbles超过 6 年前
Try and compare cnn.com with lite.cnn.com. Or (if you&#x27;re Dutch) compare nos.nl with noslite.nl. All hail text only news websites.
评论 #18463333 未加载
voycey超过 6 年前
Still pissed that they registered .dev as a TLD
koib超过 6 年前
What if there&#x27;s a login&#x2F;auth wall before getting to the actual page you want to test?
bananatron超过 6 年前
This is just lighthouse? You can run these tests in chrome under dev tools &gt; audit.
codesternews超过 6 年前
Wow amazon.com results are quite impressive. Have not thought it has 95 performance.
vini超过 6 年前
Error: 500 from Lighthouse API: Internal Server Error<p>Is all get when I try to test my website.
technion超过 6 年前
Given this says it&#x27;s in beta, can anyone see where I can report a bug?
NKCSS超过 6 年前
I think I broke Google<p>&gt; Error: 500 from Lighthouse API: Internal Server Error
评论 #18437327 未加载
zwaps超过 6 年前
PWA = Poorly made Web Application<p>for those who don&#x27;t know
intea超过 6 年前
Google only scores 80 in the SEO Category...
jjordan超过 6 年前
Must be nice to have all the money in the world to purchase any domain you want.
rblion超过 6 年前
won&#x27;t load...
thetruthseeker1超过 6 年前
doesn’t work on http
progressiveweb超过 6 年前
My question is, why do we need a React&#x2F;Redux for PWAs all the time? It is slow on cellular data, freezes phones without the latest Chrome, all in all feels laggy compared to a native app.<p>The thing is you can easily add &quot;Progressiveness&quot; to your website with Service workers and using open source libraries to add instant on-page navigation without repaint.<p>The only place I find an SPA is appropriate is anywhere else but e-commerce websites, which is one of the main target of Google&#x27;s PWA initiative, to build a collective resistance to Amazon, which has one of the highest converting pages.<p>Your conversion rates will naturally go up when people are able to checkout quickly with minimal cognitive load, this does not mean that a React app is appropriate or feasible, especially when e-commerce businesses that rely on older phones, when smartphones are approaching 1000 USD
throwaway487548超过 6 年前
Which framework is this? Material-what? What is Google&#x27;s Bootstrap alternative?<p>It does not look like Angular (which is a J2EE all over again), at least.<p>Update: I did some research<p><pre><code> cd material-components-web-codelabs&#x2F;mdc-101&#x2F;complete grep version package-lock.json |wc -l 943 </code></pre> No. Just no.
keyle超过 6 年前
Wow. From the people that have been botching the web for 20 years...<p>I mean it&#x27;s only recently that they&#x27;ve started getting their things together. And arguably their flat design isn&#x27;t always usable. Now let&#x27;s talk speed....
hardwaresofton超过 6 年前
In case you&#x27;re wondering what&#x27;s in it for google with PWAs&#x2F;App manifests&#x2F;&quot;Installable apps&quot;[0], it&#x27;s answered in another recent HN post[1] and comment[2].<p>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&#x2F;access to the user millions of times a second), but I couldn&#x27;t figure out why they would push app manifests (the only interesting part of the actual comment).<p>[0]: <a href="https:&#x2F;&#x2F;web.dev&#x2F;installable" rel="nofollow">https:&#x2F;&#x2F;web.dev&#x2F;installable</a><p>[1]: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=18434639" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=18434639</a><p>[2]: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=18435412" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=18435412</a>