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.

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

New content about a sustainable practice to improve loading medias [2.16] #45

Closed
DocRoms opened this issue Oct 24, 2023 · 2 comments
Closed
Assignees
Labels
enhancement New guideline, success criteria, or content
Milestone

Comments

@DocRoms
Copy link

DocRoms commented Oct 24, 2023

Issue :
The section [2.16] ake a More Sustainable Approach to Media Assets has interesting criteria:

  • Assess the need for video or sound usage (including only when they add visitor value), and ban
    non-informative media (background media) including autoplaying functionality.
  • Choose the right media to display by compressing according to the visitor's requirements,
    selecting the appropriate format, ensuring it works across browsers, and avoiding embedded
    player plugins.
  • Increase visitor awareness and control by informing them of the length, format, and weight of the
    media; allowing media deactivation, and giving a choice of resolutions; all while providing
    alternative resolutions and formats.
  • Set up a media management and use policy to reduce the overall impact of audio and video, with
    criteria for media compression and file formats.

But even with these recommendations, it is possible to preload a heavy video in a recent format with a good compression ;)

Solution :
To add a criterion to propose the use of facades ( cf https://developer.chrome.com/en/docs/lighthouse/performance/third-party-facades/ ) to prevent the loading of bigger medias when this one are not used by the users :

  • Medias requiring a lot of data to be downloaded on the client side (including the media itself) must be loaded via a "facade"

Note

  • Don't hesitate to explain the procedure to me if I have followed it incorrectly (the section contributing guidelines is a bit empty :)
  • If you have any further comments, don't hesistate to add it below !
  • Sorry about my english :)
@AlexDawsonUK
Copy link
Member

I agree entirely (and yes your addition is explained perfectly!), the use of facades should be prioritized in the same way that Lazy-Loading is for images. I'll add this to be included as a Success Criteria within the next draft.

@AlexDawsonUK AlexDawsonUK added the enhancement New guideline, success criteria, or content label Oct 24, 2023
@AlexDawsonUK AlexDawsonUK added this to the v1.0-D3 milestone Oct 24, 2023
@AlexDawsonUK AlexDawsonUK self-assigned this Oct 26, 2023
@AlexDawsonUK
Copy link
Member

This Success Criteria has been added into the specification. It will be available when the next draft is published.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New guideline, success criteria, or content
Projects
None yet
Development

No branches or pull requests

2 participants