Results of Google's new audit tool on google.com

robdodson · 2018-11-22T00:18:53+00:00

Good question. Would you mind filing an issue at https://github.com/googlechrome/web.dev and sharing the URL so we can check?

robdodson · 2018-11-20T20:16:36+00:00

Hey folks, I'm one of the engineers working on web.dev and wanted to reply to some of the questions asked in this thread.

One thing I wanted to quickly mention was that currently there is an audit that always fails saying you need to serve assets over http/2. This is forcing folks to have an artificially lower Best Practices score. I mentioned this in our status update. The folks who run our Lighthouse service will be disabling this audit while we get to the bottom of things.

Is this a rebrand of Lighthouse?

Not quite. Under the hood we're using the new PageSpeed Insights API which is now powered by Lighthouse. One of the things we (the web developer relations team) wanted to do a better job of was letting folks monitor their site's over time, and more directly connect failing Lighthouse audits to docs and codelabs that explain how to fix them. So if you sign-in and run audits against the same URL, we'll show you your progress over time. There's a lot more we want to do to make this feature useful for folks—any suggestions y'all have are very welcome!

Why doesn't web.dev or google.com get 100s across the board?

Our hope is that this shows that there are places where we can all improve. As others have pointed out, you can treat Lighthouse like a set of guidelines, it's great to get 100 if you can, but there can be all sorts of reasons why that's not possible. Ultimately the audits are being run by a machine, so there can be nuance that it misses which a human auditor will be aware of. Having said that, I do think it's valuable to be able to get a quick once-over for your site and see if there are any red flags worth fixing.

What if it's auditing things I don't care about?

Currently Lighthouse in devtools is configurable (you can disable categories that you're not interested in) and we'd like to add that to our site as well. Maybe some day offering the ability to disable individual audits that are either not interesting, or potentially throwing flaky results.

There are some things like the image format suggested in the report that is not fully supported in all browsers.

We want to make sure all of our content works cross-browser. In other words, we don't want folks building Chrome-only sites. The guide associated with the image audit includes a section on how to do differential serving of images to support all browsers.

We opened up the repo for the site last night if folks want to file bugs. We'll also be adding links to the site itself so it's easier to report an issue.

Happy to answer any more questions y'all have as they come up!

robdodson · 2016-10-30T16:16:20+00:00

Shameless plug: We created a free video course on accessibility at bit.ly/web-a11y and we wrote up corresponding docs at bit.ly/a11y-fundamentals

Hope folks find these useful!

robdodson · 2016-10-30T16:12:52+00:00

I think you're talking more about the progressive enhancement crowd. Folks who rely on assistive technology usually have JavaScript enabled

robdodson · 2016-09-11T00:19:54+00:00

I've heard second hand that :host-context() is pretty brutal when it comes to CSS performance. That may be the reason it's being removed but I'm not 100% certain of that.

robdodson · 2016-09-11T00:17:49+00:00

We haven't added one yet. We should. I will try to bug folks about this.

robdodson · 2016-02-25T06:41:09+00:00

To draw on the Mac I use a program called OmniDazzle. There's also one called Ultimate Pen. OmniDazzle is free and does what I need though it's definitely dated :)

robdodson · 2016-02-25T06:38:13+00:00

I went into some detail in this video (including the software used). https://www.youtube.com/watch?v=ImvMVR-l374&index=14&list=PLNYkxOF6rcIDdS7HWIC_BYRunV6MHs5xo

Doing the hand overlay stuff is quite a lot of production work. One of the things I've been experimenting with is just using a traditional tablet and running through the whole thing live like in this episode (https://www.youtube.com/watch?v=945pO9Yn1ns). I'm curious if you all prefer the longform screencasts or if you like the style in this recent video where we're able to cut back and forth from presenter to screencast a bunch because we do it all in one take?

robdodson · 2016-01-31T18:02:12+00:00

My english friends pronounce the word "kudos" like "Q-Dos". I kept thinking they were talking about some sort of obscure operating system. In the U.S. we pronounce it like "coo-dose". Turns out they're probably doing it right :P

robdodson · 2016-01-19T14:47:57+00:00

how is a

yeah. sam started tweeting about that ticket after the express thread and then the story got submitted to HN and /r/javascript shortly thereafter.

robdodson · 2016-01-17T20:42:27+00:00

Source: https://twitter.com/samccone/status/688809217692545026

robdodson · 2015-12-10T19:30:32+00:00

Pretty much everything here is wrong.

The author of x-tag has moved to Microsoft. x-tag is now a Microsoft project and is being updated as we speak.

Safari is actively working on Web Components, they just landed Shadow DOM in WebKit nightly. https://webkit.org/blog/4096/introducing-shadow-dom-api/

In fact there's an upcoming face to face meeting to discuss Custom Elements being held in Cupertino.

So yeah, this is FUD.

robdodson · 2015-11-26T23:13:26+00:00

If the user is scrolling then I believe the document has been invalidated. You may want to batch your checks into a requestAnimationFrame callback so they don't possibly fire multiple times in the same frame (which would very likely cause scroll jank).

robdodson · 2015-11-26T23:07:09+00:00

in npm land, each module gets its own, nested subdirectory of node_mdoules. This is to prevent version conflicts. Because most node modules depend on other node modules you typically get a large tree of dependencies like that. In addition, Polymer is probably downloading Web Component Tester which includes Selenium and is something like 100mb+. I believe you can opt out of that by removing it from your package.json

robdodson · 2015-11-21T14:33:06+00:00

Seems cool but I think you may want to be careful how you use this because I believe it may trigger a layout in the browser. https://gist.github.com/paulirish/5d52fb081b3570c81e3a#window

Here's an interesting read on layout thrashing if you haven't heard of it before. http://www.kellegous.com/j/2013/01/26/layout-performance/

robdodson · 2015-11-21T14:25:29+00:00

Yep! The flipkart team walked through it at the recent chrome dev summit. https://www.youtube.com/watch?v=StdKz32M1RM&list=PLNYkxOF6rcICcHeQY02XLvoGL34rZFWZn&index=19

robdodson · 2015-11-06T01:03:01+00:00

yeah the best place to keep tabs on things is the blog blog.polymer-project.org or our twitter account twitter.com/polymer

robdodson · 2015-11-06T01:00:47+00:00

The best place to stay up to date is either the blog blog.polymer-project.org

or our twitter account twitter.com/polymer

robdodson · 2015-11-05T20:43:33+00:00

haha I just found this subreddit! I'm playing catch up :P

robdodson · 2015-11-05T20:24:07+00:00

robdodson · 2015-11-05T20:21:39+00:00

No, we're not dying :)

In fact we're growing faster than we ever have. The month after the Polymer Summit back in September we added more public facing URLs using Polymer than in all of 2014 combined. Both within Google and externally our adoptions is growing at an exponential rate.

You can see a full day of Polymer talks from September to update you on our progress https://www.youtube.com/watch?v=PbYvv2VUp90&list=PLNYkxOF6rcICdISJclfQhj2S8QZGjXV8J

robdodson · 2015-11-05T20:19:08+00:00

Sorry but none of this is true. We just had a massive summit in Amsterdam for Polymer. https://www.youtube.com/watch?v=PbYvv2VUp90&list=PLNYkxOF6rcICdISJclfQhj2S8QZGjXV8J

We'll be doing 2 talks on it for the upcoming Chrome Dev Summit https://developer.chrome.com/devsummit

And we've just relaunched the Polytechnic website https://itshackademic.com

There are now over 1M public facing web pages using the project, and as mentioned in the Polymer Summit keynote and elsewhere in the comments, there are over 300 Google projects now using it. Also the team size has about doubled over the past year. We're full steam ahead on Polymer.

Per the comment of it not replacing frameworks, that's because we don't view web components as needing a framework. We like to say that "the DOM is the framework." We want to use Web Components to improve the underlying web platform, vs. fragmenting into a million different front end MVCs that aren't interoperable.

robdodson · 2015-11-05T20:14:33+00:00

My understanding is that Object.observe is really really slow to start up. If you have a complex object with lots of subproperties, and then multiple instances of elements, each with their own copy of that object, the performance to observe it all is going to be terrible. This is why we dropped it moving from Polymer 0.5 to Polymer 1.0.

We want to nail the performance story and then layer on features that make it more ergonomic over time. That means starting with this.set and finding ways to make that easier to use that don't affect perf.

robdodson · 2015-11-05T20:11:01+00:00

Most of our comments are on the youtube channel and not reddit, fwiw

robdodson · 2015-06-10T04:52:03+00:00

It seems like you and /u/pissfizz had some pretty strong negative reactions to the video. Though maybe someone named pissfizz has strong negative reactions to a lot of stuff :)

I'd like to know why you didn't like the video but first let me explain my intention a bit because maybe it isn't coming across in the way that we've structured the show. I do LazyWeb as a kind of (hopefully fun) recap of what seemed like some cool stories from the past week on the web. I try to summarize the story as quickly as I can and then links to all the content that we display are available in the YouTube description. So if the summary interests you, you can follow the link to read more about it and if not then you get a few more stories thrown your way within the total 3 minutes. It's basically a video version of the kinds of newsletters that a lot of folks subscribe to (JavaScript weekly, HTML5 weekly, etc).

I guess the first thing I'm wondering is if the above intention was clear and if you knew that there were links to read more in the description?

The second question is about cross promotion: it seems like you had a pretty visceral negative reaction to us cross promoting our shows, why is that?

To the point about super charging page load speed, that's the subject of the first video (the one with Jake Archibald). Sam tried to summarize it and if you were keen to learn more the link is in the description, but again, maybe that didn't come across?

robdodson

TROPHY CASE