-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audits Meta: Feature parity with PSI, MFT, DevTools #909
Comments
some basic info added, more to come. |
Not from I. This seems like a good time to modernize them :) |
Adds basic CSS rule usage tracking gatherer and audit. Moves toward parity with Audits 1.0 as per #909.
Updated the list with the css usage tracking. That's imminent. |
Adds basic CSS rule usage tracking gatherer and audit. Moves toward parity with Audits 1.0 as per #909.
Re, parity.. Looking at the list, I think there are two audits missing: |
Thanks @igrigorik. Added those to the top. |
Addresses one of several concerns around image bloat and another step towards PSI parity (#909). Gathers all sameorigin or data URI images off of the network and runs them through canvas to determine a stripped down JPEG and WebP size. Audit will fail if one of the conditions are met: * There is at least one JPEG or bitmap image that was larger than canvas encoded JPEG. * There is at least one image that would have saved more than 50KB by using WebP. * The savings of moving all images to WebP is greater than 100KB.
Adds basic CSS rule usage tracking gatherer and audit. Moves toward parity with Audits 1.0 as per GoogleChrome#909.
#1452 addresses unoptimized images, though it would be nice to have a place to track building on that to try to quantify the load time added by not using better compression. |
As of 2.8.0 nearly all the parity audits are complete! Boom. |
We good here. Follow the linked issues above for individual audits. |
updated by @paulirish jan 2018
For parity with Pagespeed Insights
Prioritize visible content(docs)Minify HTMLFor parity with Mobile-Friendly Test:
For parity with legacy DevTools Audit panel:
The text was updated successfully, but these errors were encountered: