Page Weight 2025

[nrllh]

Page Weight 2025

If you're interested in contributing to the Page Weight chapter of the 2025 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. You can find more details about this year’s Call for Contributions here.

💬 Please make sure to join #web-almanac-page-weight on Slack for team coordination.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@rickb110	@rickb110 @fellowhuman1101	@dwsmart @Shelliweb	@dwsmart	@anniepoohster	@Yash-Vekaria

Expand for more information about each role 👀

• The content team lead is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress.
• Authors 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 are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases.
• Analysts 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 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 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 doc.

Milestone checklist

0. Form the content team

• [x] 📆 May 18 Complete program and content committee - 🔑 Organizing committee
  • The content team has at least one author, reviewer, and analyst.

1. Plan content

• [x] 📆 June 1 First meeting to outline the chapter contents - 🔑 Content team
  • The content team has completed the chapter outline.

2. Gather data

• [x] 📆 July 1 Custom metrics completed - 🔑 Analysts
  • Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress.
• [x] 📆 July 1 HTTP Archive Crawl - 🔑 HA Team
  • HTTP Archive runs the June crawl.

3. Validate results

• [x] 📆 September 1 Query Metrics & Save Results - 🔑 Analysts
  • Analysts have queried all metrics and saved the output.

4. Draft content

• [x] 📆 October 1 First Draft of Chapter - 🔑 Authors
  • Authors has written the chapter.
• [ ] 📆 October 20 Review & Edit Chapter - 🔑 Reviewers & Editors
  • Reviewers and Editors has processed the the chapter.

5. Publication

• [ ] 📆 November 15 Chapter Publication (Markdown & PR) - 🔑 Authors
  • Authors has converted the chapter to markdown and drafted a PR.
• [ ] 📆 December 1 Launch of 2025 Web Almanac 🚀 - 🔑 Organizing committee

6. Live Stream

• [ ] 📆 December 15 Live Stream - 🔑 Content Team

Chapter resources

Refer to these 2025 page-weight resources throughout the content creation process:

• 📄 Planning doc for outlining and drafting content
• 📊 Results sheet for saving the results of queries
• 📝 Markdown file for publishing content and managing public metadata
• 🔍 SQL files for committing the queries used during analysis
• 💬 #web-almanac-page-weight on Slack for team coordination

[Yash-Vekaria]

@fellowhuman1101 @dwsmart @CSteele-gh @mordy-oberstein @drohe @ines-akrap @burakguneli @cqueern I see that you have contributed to the Page Weight chapter in previous years. Just wanted to bring this call for contributions for 2025 to your notice in can you would like to contribute to this year's Page Weight chapter.

[dwsmart]

I'd be happy to see someone else take a shot this year, but will definitely step in if needs be!

Happy to act as a reviewer, or perhaps give analysist a try this time either way.

[fellowhuman1101]

Happy to help! I want to give a new author a chance to shine this year and serve as a reviewer.

[rickb110]

Jamie bullied me into putting my name down

Happy to give author on this a crack

[fellowhuman1101]

Jamie bullied me into putting my name down

Happy to give author on this a crack

I regret nothing ಠ_ಠ

[anniepoohster]

Looking for an editor for this chapter? I could take that on.

[Shelliweb]

Also happy to help out as reviewer if you need any more eyes on it

[Yash-Vekaria]

Thanks everyone for willing to contribute towards a successful chapter for 2026 version.

Currently, we do not have a lead for this chapter. @rickb110 @dwsmart @fellowhuman1101 @Shelliweb would anyone be interested in taking a lead to drive the chapter forward?

[nrllh]

@rickb110 since you were the only author, I've assigned you as the lead for this chapter - hope that’s okay.

[rickb110]

@nrllh Yep that's fine I promise I will figure out how to get on the slack the moment I have a minute

[nrllh]

@rickb110, could you please try to schedule a meeting with the content team to draft this year's outline?

[fellowhuman1101]

@rickb110, could you please try to schedule a meeting with the content team to draft this year's outline?

@nrllh I'm going to pivot from reviewer to author so we have better coverage (and @rickb110 doesn't have to author his first chapter all by himself ;) )

[nrllh]

@nrllh I'm going to pivot from reviewer to author so we have better coverage (and @rickb110 doesn't have to author his first chapter all by himself ;) )

Great, thank you!

[nrllh]

@rickb110 we still miss the outline, could you please draft the outline with your team ASAP? Thank you!

[Yash-Vekaria]

@rickb110 I see we have the chapter outline added. However, as we passed the deadline to finalize custom metrics, just wanted to check if we are on track with custom metrics implementation? If not, could you discuss with the team to finalize them? Thank you.

[rickb110]

I think we already did this in the slack channel or am I being daft? @dwsmart @fellowhuman1101 Am I being daft?

[dwsmart]

Correct @rickb110 . The consensus was no new custom metrics were needed, so last year's are just fine, and as far as I know we don't need to submit any pull requests for that, is that correct @Yash-Vekaria? Is there some other action we need to take?

[Yash-Vekaria]

My bad, I didn't check the comments. Just reviewed the planning doc attached with this issue. Thanks @rickb110 @dwsmart for prompt replies. Yes, that's correct. If there are no new custom metrics, no need to submit any pull requests. I'll mark custom metrics as done here.