-
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
DBW: site uses responsive images #978
Comments
which viewports & dpr are you referring to? viewport: mobile, ipad, desktop? |
Also potentially sharing overlap with #876? Perhaps that just becomes a proposed solution to a failed responsive image audit |
@wardpeet yea, I was thinking reasonable defaults for each of those. I think we'd have use device emulation for the DPR. Checking dpr 1 vs. 2 would be good for starters. @patrickhulce There's probably overlap. Possibly a shared gatherer for the image stuff. I filed separate bugs b/c #876 is also closely related to #718. They could be the start to a set of audits for initial page load perf. NBU, reduce bytes transferred, awesome. |
k i'll get started on some of these |
Cool. I'll take #718 from the "save bandwidth" side |
enables more device emulation adds use-responsive-images audit to dobetterweb addresses GoogleChrome#978
Tracked Features
Detectimg
elements that use assets that are too large for their displayed size (DBW: Responsive Images Audit #1497)ORIGINAL
It would be nice to have an audit for testing if a site sends responsive images. We could test for different common viewports and DPR and see if the images served by the page vary in size.
Suggest techniques like
<img srcset>
, cssimage-set()
, and<picture>
.Perhaps it could share a gatherer with #718
The text was updated successfully, but these errors were encountered: