Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Optimized Images reports too much JPEG savings #1853

Closed
patrickhulce opened this issue Mar 11, 2017 · 1 comment · Fixed by #2154
Closed

Optimized Images reports too much JPEG savings #1853

patrickhulce opened this issue Mar 11, 2017 · 1 comment · Fixed by #2154
Assignees
@patrickhulce
Labels
bug

Comments

@patrickhulce
Copy link
Collaborator

At some point recently the optimized images audit has started reporting far too much savings (maybe a change in 57 stable?). For an image properly encoded at quality 80, Chrome's rendering seems to think it can be even 60% smaller.

image
@patrickhulce patrickhulce self-assigned this Mar 11, 2017
@patrickhulce
Copy link
Collaborator Author

patrickhulce commented May 4, 2017 •
edited
Loading

Update: this seems to be specific to cross-origin images fetched via getResponseBody, plan to disable for now

@patrickhulce patrickhulce mentioned this issue May 4, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@patrickhulce patrickhulce

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

perf(gatherers): skip optimization of cross origin images GoogleChrome/lighthouse
1 participant
@patrickhulce