New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 755702 link

Starred by 1 user
Status: WontFix
Owner:
█ phulce@chromium.org
Last visit > 30 days ago
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Performance Audit suggests experimental technologies

Reported by phoe...@codecombat.com, Aug 15 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
1. Run Perfomance Audit on any page with large non-web images
2. View the audit results
3. See that is suggests to serve images as WebP

What is the expected behavior?
I expected the suggestion to use the WebP image format to include a note that WebP is experimental and not widely supported at all.

What went wrong?
The audit results suggest using WebP without any warning that it is not widely supported, leading me to believe that I can simply make this change with little to no negative impact.

Did this work before? No 

Chrome version: 60.0.3112.90  Channel: stable
OS Version: OS X 10.11.6
Flash Version:
Screen Shot 2017-08-15 at 1.34.34 PM.png
96.9 KB View Download

Comment 1 by l...@chromium.org, Aug 16 2017

Owner: phulce@chromium.org
Status: WontFix (was: Unconfirmed)
Thanks for the report.  It looks like a similar concern was raised in the LH github issue repo:
https://github.com/GoogleChrome/lighthouse/issues/2044

If it's still the case, it seems like V2 won't have WebP suggestions, according to the thread.  In that case, it sounds like there's a plan to fix this.  I think you may get more attention from LH folks if you post further comments on the LH github thread than here, so I'll mark this as WontFix, but please feel free to ask questions on the github link.

Assigning phulce@, in case what I'm saying is incorrect.

Comment 2 by phulce@chromium.org, Aug 17 2017 

The outcome of the linked issue is the current state of affairs you see in the DevTools panel. WebP suggestions have been split into their own audit (separate bar from optimize images under "Opportunities") so as to enhance filterability. We currently don't have any plans to remove the WebP suggestions, but as luoe@ has stated, we'd welcome any feedback on the criteria for performance opportunities over on the GitHub repo (https://github.com/GoogleChrome/lighthouse/issues/new) where the discussion will be a bit more visible to other stakeholders.
►

Sign in to add a comment