GoogleChrome / GoogleChrome/lighthouse

Too large background images should trigger responsive image audit not offscreen audit

Open
#11,480 2 comments 0 reactions 0 assignees View on GitHub
bug P3
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 14h
Merged PRs (30d)
20

Description

This image is actually loaded via a background css rule with a class in the body and oddly it should be in most cases not needed to be lazy loaded as is visible on the top, either way I used the unveilhooks plugin of lazysizes.
link to the website: www.otzerling.com

![002341_25092020](https://user-images.githubusercontent.com/32283036/94295057-12af8b80-ff37-11ea-9fe4-3cbb6fc4f763.jpg)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the audit behavior on www.otzerling.com, focusing on the background CSS image and the lazysizes unveilhooks plugin described in the report. Compare whether the image is classified as an offscreen image or a responsive-image opportunity. Done means oversized background images are reported by the responsive image audit rather than the offscreen audit, with the existing behavior for genuinely offscreen images preserved.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.