They’re all pretty similar so it’s up to you which you prefer to use.
If you want to track your scores over time, the website is nice for that.
If you just want to do a quick check, you can either use the site, or use DevTools itself.
I believe this audit is checking if any anchors, <a href=”…”>, on the page are missing an accessible name. For instance, if you have an anchor that just contains a background image, it will be announced as “link” to a screen reader, without any context as to where the link goes to.
They all use the same tool under the hood (Lighthouse). Currently the version on web.dev doesn’t let you change the configuration settings, it runs with the same default settings as the extension and the devtools version. So, if you’re ok with the defaults then they should all give similar results.
Under the hood we’re using a tool called Lighthouse (https://developers.google.com/web/tools/lighthouse/) which tracks a subset of SEO issues that are easy for a machine to check. We’re planning to add an “Understanding your score” section so folks know what we’re able to check and what they will still need to check manually.
In the blog post we mention that we’re working on the h2 issue, the tracking bug is here: https://github.com/GoogleChrome/lighthouse/pull/6564
We also opened up our site’s repo last night if you’d like to file issues there, https://github.com/googlechrome/web.dev
We’ll be adding links to our pages to make it easier for folks to file issues.
Under the hood we’re using a tool called Lighthouse (https://developers.google.com/web/tools/lighthouse/) to run these tests. Lighthouse doesn’t test all 200 ranking factors, it’s a subset of things that are easy to test with a machine. I think we’re going to add an “understanding your score” section so folks know…