search

HTTPArchive / almanac.httparchive.org

HTTP Archive's annual "State of the Web" report made by the web community
https://almanac.httparchive.org
Apache License 2.0
617 stars 178 forks source link

Media 2021 #2144

Closed rviscomi closed 2 years ago

rviscomi commented 3 years ago

Part I Chapter 5: Media

Media illustration

If you're interested in contributing to the Media chapter of the 2021 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor.

Content team

Lead Authors Reviewers Analysts Editors Coordinator
@eeeps @eeeps @dougsillars @Navaneeth-akam @akshay-ranganath @tpiros @addyosmani @eeeps @dougsillars @akshay-ranganath - @rviscomi
Expand for more information about each role - The **[content team lead](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Content-Team-Leads'-Guide)** is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress. - **[Authors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Authors'-Guide)** are subject matter experts and lead the content direction for each chapter. Chapters typically have one or two authors. Authors are responsible for planning the outline of the chapter, analyzing stats and trends, and writing the annual report. - **[Reviewers](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Reviewers'-Guide)** are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases. - **[Analysts](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Analysts'-Guide)** are responsible for researching the stats and trends used throughout the Almanac. Analysts work closely with authors and reviewers during the planning phase to give direction on the types of stats that are possible from the dataset, and during the analyzing/writing phases to ensure that the stats are used correctly. - **[Editors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Editors'-Guide)** are technical writers who have a penchant for both technical and non-technical content correctness. Editors have a mastery of the English language and work closely with authors to help wordsmith content and ensure that everything fits together as a cohesive unit. - The **[section coordinator](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Section-Leads'-Guide)** is the overall owner for all chapters within a section like "User Experience" or "Page Content" and helps to keep each chapter on schedule. _Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors._ For an overview of how the roles work together at each phase of the project, see the [Chapter Lifecycle](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle) doc.

Milestone checklist

0. Form the content team

1. Plan content

2. Gather data

3. Validate results

4. Draft content

5. Publication

Chapter resources

Refer to these 2021 Media resources throughout the content creation process:

📄 Google Docs for outlining and drafting content 🔍 SQL files for committing the queries used during analysis 📊 Google Sheets for saving the results of queries 📝 Markdown file for publishing content and managing public metadata

IsaacSichangi commented 3 years ago

hello id like to take up an analyst role in the media chapter

boosef commented 3 years ago

I can help review and/or edit! :)

eeeps commented 3 years ago

I reviewed in 2019 and pitched in as a last-minute author in 2020. I would love to be involved at an earlier stage, this year, either as an author or reviewer.

Navaneeth-akam commented 3 years ago

I was a reviewer for media in 2020 and would like to be reviewer for this year as well. Along with that, i would like to take up the editor role as well

akshay-ranganath commented 3 years ago

Hi Rick,

I'd like to help build this chapter. I am a Solution Architect at Cloudinary and used to be a web performance consultant at Akamai prior to my current role.

Thanks!

rviscomi commented 3 years ago

Thanks everyone! Feel free to start brainstorming content for this chapter by requesting edit access to the doc and adding your thoughts.

rviscomi commented 3 years ago

@trevorfsmith mentioned that WebXR might be an interesting topic to explore this year. As a follow-up to the question of what can be quantified, does anyone know of use counters that track WebXR usage? For example XRDOMOverlay seems like it may be relevant. The top chart shows the percent of page loads in Chrome that make use of that feature. The bottom chart is empty in this case, indicating that none of the pages in HTTP Archive use it, or that we're unable to trigger the conditions needed to use it (like if it depends on real user interactions).

@trevorfsmith @Yonet would either of you be interested in authoring/reviewing this chapter? And would your focus strictly be WebXR or might you be interested in Media topics as a whole (images, video, etc)?

TrevorFSmith commented 3 years ago

I found a few relevant use counters:

Some of the old XR counters are for WebVR which is no longer shipping in Chromium-based browsers. WebXR is the actually standardized replacement for WebVR. The old API counters trend toward zero like XRRequestDevice.

I'm interested in editing the XR-related parts of the almanac (or co-editing with @Yonet).

rviscomi commented 3 years ago

Thanks @TrevorFSmith those use counters are a good place to start. Could you add a WebXR section to the chapter outline and list these use counters in the metrics section of the chapter doc?

Editing is a non-technical role—do you mean authoring or reviewing?

rockeynebhwani commented 3 years ago

@TrevorFSmith @rviscomi - Last year, I had added detection of webAR in Wappalyzer to track usage on eCommerce sites but on eCommerce sites uses tend to be on Product Detail page which we don't crawl so I didn't end up covering this in the chapter. https://github.com/AliasIO/wappalyzer/issues/3216

rviscomi commented 3 years ago

@eeeps thanks for your interest in authoring this chapter! As the content team lead, you'll be responsible for the scope and direction of the chapter and keeping it on schedule. We automatically monitor the staffing and progress of each chapter based on the state of the initial comment so please keep that updated as you add new contributors and meet each milestone.

We've created a Google Doc for this chapter, which you're encouraged to use to collaborate with the content team on the initial outline, metrics, and ultimately the final draft.

Next steps for this chapter are:

There's not currently a section coordinator for this chapter, so I'll be periodically checking in with you directly to make sure the chapter is staying on schedule. Reach out here in this issue if you have any questions about the process.

More information about the content team lead and author roles and responsibilities are available for reference in the wiki if needed.

To anyone else interested in contributing to this chapter, please comment below to join the team!

Yonet commented 3 years ago

@rviscomi @TrevorFSmith and I want to be authors. I've asked for edit access for both of us for the Media chapter doc to add WebXR and metrics section.

If someone else would like to contribute to Media chapter as an author and I am happy to contribute as a reviewer as well.

rviscomi commented 3 years ago

Ok great. thanks @Yonet and @TrevorFSmith, I've given you both edit access to the doc.

@eeeps is now the content team lead and is in charge of assigning authors/reviewers as needed, so I'll defer to them on the final call. If WebXR will be a big part of this chapter I'd recommended adding one or both as coauthors. @eeeps could you update the contributor info in the top comment of this issue with your decision either way?

rviscomi commented 3 years ago

ℹ️ FYI 2019/2020 contributors: @dougsillars @colinbendell @ahmadawais @kornelski @tpiros @bseymour @nhoizey @smatei

This year's Media chapter is looking pretty good in terms of staffing, but I wanted to ping you all in case you'd still like to contribute as reviewers or analysts. It's great to have input from past years' contributors. Let us know!

dougsillars commented 3 years ago

Rick, I'd be happy to focus on video as a part of the media chapter.

tpiros commented 3 years ago

@rviscomi 👋 I'd be happy to sign up as a reviewer this year, if that's an option!

rviscomi commented 3 years ago

@dougsillars @tpiros great to have you both back! I'll defer to @eeeps as content team lead to loop you both in.

rviscomi commented 3 years ago

Hi @eeeps just checking in. Here are some tips to help keep the chapter on track:

Also as an FYI for the content team, we have an existing #web-almanac-media channel on Slack from last year. So if you'd find it useful to coordinate on there, feel free to get that going again.

eeeps commented 3 years ago

@rviscomi Thanks for the nudge (and sorry for the slow start!)

I'm super-excited about the prospect of WebXR content in the chapter, and have added @TrevorFSmith and @Yonet as co-authors.

@dougsillars What is your level of commitment? If you by any chance have the bandwidth to tackle video as a co-author, rather than as an editor, just let me know.

I'll organize a kick-off sometime in the next couple of weeks. @IsaacSichangi @boosef @Navaneeth-akam @akshay-ranganath I don't see you in the HTTP Archive Slack, or #web-almanac-media channel. I'd like to coordinate, there. Here's the invite link: https://join.slack.com/t/httparchive/shared_invite/zt-45sgwmnb-eDEatOhqssqNAKxxOSLAaA – let me know if you have any issues or if Slack won't work for you for whatever reason.

dougsillars commented 3 years ago

@eeeps i would be up for video as co author

rviscomi commented 3 years ago

@eeeps @TrevorFSmith @Yonet @dougsillars the doc is looking good so far! I'd suggest you take some of the ideas and put them in the outline section to get a sense for how the content will be organized. I think that'll help you fill out the complete skeleton of the chapter and indicate which topics require additional metrics. The due date for completing the chapter outline (Milestone 1) is June 15 to leave enough room for making changes to the runtime tests that start on July 1. Let me know if you have any questions!

rviscomi commented 3 years ago

Hi @eeeps. Checking in. The doc is still looking good and I'm glad to see early progress on the custom metrics (Milestone 2). Are you feeling good about closing out Milestone 1 by June 15?

heymarkreeves commented 3 years ago

Hi, @eeeps! I'll look for you in Slack tomorrow to talk about the Analysts role.

eeeps commented 3 years ago

@heymarkreeves Fantastic! I've added you as an analyst in the OP. I was AFK all afternoon but I'll make some time to sync tomorrow.

@rviscomi Unfortunately, we're falling a bit behind. I know @dougsillars is working on the Video section of the outline, and I'm working on the Images section. I need to connect with @TrevorFSmith and @Yonet about WebXR, and make sure they're in good shape w/r/t custom metrics.

rviscomi commented 3 years ago

Thanks for the update @eeeps. Please tick the Milestone 1 box above ASAP when you feel that the outline is solid.

rviscomi commented 3 years ago

@eeeps how's the outline looking? Which parts are still being worked on? Getting close to the hard deadline for custom metrics, so it'd be great to get the outline locked down ASAP.

addyosmani commented 3 years ago

Impact of modern image formats anyone? :)

Perhaps it would be interesting this year to look at whether there are correlations between the usage of deployed modern image formats (WebP, AVIF) and Largest Contentful Paint?. One could potentially look at pages where the LCP element is an image, served in one of the above {.webp, .avif} (...or where content negotiation has served one of them) and compare it to pages where an older image format is in use. This is of course all complicated by image quality not being easily comparable across sites, but throwing the idea out anyway :)

tunetheweb commented 3 years ago

This is of course all complicated by image quality not being easily comparable across sites, but throwing the idea out anyway :)

Surely it's not just image quality and there's a million other factors at play here so making such a statement would be very hard unless we had a like for like comparison between the sites with old format and without?

Plus do sites that use newer formats care more about performance anyway?

Reminds me a lot of this discussion.

jyrkialakuijala commented 3 years ago

Could we have a decomposition of image quality in the media analysis? This would give us guidance for developing and optimizing new image formats and make recommendations on their use. Currently there is a lot of confusion on what image qualities would actually matter on the web, and different teams are optimizing different ends of the quality spectrum.

Tracing what is the quality (or just bpp if we are unable to decide about quality) of an image byte in the internet would be one way to achieve this. Similar to this: https://www.spiedigitallibrary.org/ContentImages/Proceedings/11137/111370K/FigureImages/00163_PSISDG11137_111370K_page_3_1.jpg

Seeing the long trends over years on quality of images -- if it is increasing or decreasing, what are the differences in optimized vs. unoptimized sites, etc. would be interesting to me.

eeeps commented 3 years ago

@jyrkialakuijala I was able to get a BPP custom metric in place (just) in time this year, so we'll be able to, for the first time, talk about the BPP of all images surveyed in this year's crawl!

Lacking a time machine, we do not have this information for previous years' crawls.

I've brainstormed the idea of taking a statistically significant random sample of crawled image URLs, re-downloading the actual image resources, and getting various quality metrics from those. That kind of analysis was way beyond what the crawler (and custom metric hooks) can handle, though. If you know anyone who could help with this – that would be amazing.

But -- I can't wait to dive into the BPP data, which should be fascinating all on its own.

eeeps commented 3 years ago

@addyosmani:

Perhaps it would be interesting this year to look at whether there are correlations between the usage of deployed modern image formats (WebP, AVIF) and Largest Contentful Paint?

After talking with @siakaramalegos (who's heading up the Performance chapter), we decided a good rule of thumb for how to divide up subjects which deal with both images and performance was: if the topic is about how images are affecting whole page performance (e.g., as measured by CWV), Performance gets first dibs; if it's about how images themselves are performing, Media gets first dibs. With a healthy dose of cross-linking where appropriate.

If Performance doesn't tackle this correlation, I'd love to!

eeeps commented 3 years ago

August 13 update:

If any of our reviewers (@boosef @Navaneeth-akam @akshay-ranganath @tpiros) want to take a gander at the outline and leave comments, please do!

Otherwise, time for @dougsillars and I (and anyone else who'd like to pitch in!) to get cracking on the queries.

rviscomi commented 3 years ago

👋 Hi @eeeps @Yonet @dougsillars @IsaacSichangi @heymarkreeves, just checking in on the chapter progress. How is the analysis coming along?

eeeps commented 2 years ago

Review team! @boosef @Navaneeth-akam @akshay-ranganath @tpiros

Sincere apologies for the late, and last-minute call for review, but: we finally have a full first draft of the chapter in the Google Doc, and it is finally in a reviewable state.

Due to my own missed deadlines, we're going to miss the launch tomorrow. But we're hoping to publish the chapter as soon as possible, so the sooner you have a chance to review, the better.

Thank you!

tpiros commented 2 years ago

Thank you Eric. I will review by the end of today.

Tamas

On Wed, 1 Dec 2021 at 06:48, Eric Portis @.***> wrote:

Review team! @boosef https://github.com/boosef @Navaneeth-akam https://github.com/Navaneeth-akam @akshay-ranganath https://github.com/akshay-ranganath @tpiros https://github.com/tpiros

Sincere apologies for the late, and last-minute call for review, but: we finally have a full first draft of the chapter in the Google Doc, and it is finally in a reviewable state.

Due to my own missed deadlines, we're going to miss the launch tomorrow. But we're hoping to publish the chapter as soon as possible, so the sooner you have a chance to review, the better.

Thank you!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2144#issuecomment-983310497, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPSWXU3QBDJO42YRHYCMXTUOWZMJANCNFSM43UFMNUA .

-- Kind Regards,

Tamas Piros

tpiros commented 2 years ago

Done. Left my thoughts in the doco! :)

On Wed, 1 Dec 2021 at 07:54, Tamas Piros @.***> wrote:

Thank you Eric. I will review by the end of today.

Tamas

On Wed, 1 Dec 2021 at 06:48, Eric Portis @.***> wrote:

Review team! @boosef https://github.com/boosef @Navaneeth-akam https://github.com/Navaneeth-akam @akshay-ranganath https://github.com/akshay-ranganath @tpiros https://github.com/tpiros

Sincere apologies for the late, and last-minute call for review, but: we finally have a full first draft of the chapter in the Google Doc, and it is finally in a reviewable state.

Due to my own missed deadlines, we're going to miss the launch tomorrow. But we're hoping to publish the chapter as soon as possible, so the sooner you have a chance to review, the better.

Thank you!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2144#issuecomment-983310497, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPSWXU3QBDJO42YRHYCMXTUOWZMJANCNFSM43UFMNUA .

-- Kind Regards,

Tamas Piros

Navaneeth-akam commented 2 years ago

Review team! @boosef @Navaneeth-akam @akshay-ranganath @tpiros

Sincere apologies for the late, and last-minute call for review, but: we finally have a full first draft of the chapter in the Google Doc, and it is finally in a reviewable state.

Due to my own missed deadlines, we're going to miss the launch tomorrow. But we're hoping to publish the chapter as soon as possible, so the sooner you have a chance to review, the better.

Thank you!

Will take a look at it and add comments

tunetheweb commented 2 years ago

@eeeps @dougsillars @Navaneeth-akam @akshay-ranganath @tpiros @addyosmani

🎉 This chapter is fully written, reviewed, edited, and ready to be launched! Thank you to all of the contributors who put in the time and effort to make this a great chapter.

When you get 5 minutes, I'd really appreciate if you could fill out our contributor survey to tell us (the project leads) about your experience. It's super helpful to hear what went well or what could be improved for next time. 🙏

Congratulations and thank you all again. I'm excited for this to launch soon!

tpiros commented 2 years ago

thank you @tunetheweb for all your help this year as well! ❤️ 🤗