Performance 2025

[nrllh]

Performance 2025

If you're interested in contributing to the Performance 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-Performance on Slack for team coordination.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@25prathamesh	@hfhashmi @25prathamesh @himanshujariyal	@siakaramalegos	@tannerhodges	-	@mikaelaraujo

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

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

3. Validate results

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

4. Draft content

• [ ] 📆 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 performance 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-performance on Slack for team coordination

[siakaramalegos]

I can be a reviewer

[hfhashmi]

I can be either an author, reviewer, or editor! About me: first-year CS PhD student at UCDavis, working on a measurement project correlating network performance with web performance.

[mikaelaraujo]

I can be either an author, reviewer, or editor! About me: first-year CS PhD student at UCDavis, working on a measurement project correlating network performance with web performance.

@hfhashmi Welcome. Join us at https://join.slack.com/t/httparchive/shared_invite/zt-45sgwmnb-eDEatOhqssqNAKxxOSLAaA -> Performance chapter.

[hfhashmi]

Joined!

Also, are we allowed to join other channels of interest even if we are not on the team for that chapter? (slack gave me options to choose all channels I wanted to join).

[nrllh]

Joined!

Also, are we allowed to join other channels of interest even if we are not on the team for that chapter? (slack gave me options to choose all channels I wanted to join).

Sure, all channels are public

[25prathamesh]

I can be either an author, reviewer and analyst (if needed) About me - I am a cofounder of a web performance startup, developed a RUM tool, was part of the 2022 Web Almanac performance chapter

[macioseo]

i can be author, Analyst and Translator

[mikaelaraujo]

@macioseo I'm pitching you as an analyst, but feel free to contribute as an author if you wish. Join us at: https://join.slack.com/t/httparchive/shared_invite/zt-45sgwmnb-eDEatOhqssqNAKxxOSLAaA

[macioseo]

Hi, folks. Yes, I'm interested in contributing as an Analyst and an Author. I'm a Senior Technical SEO Specialist, although I'm not a developer. Looking forward to collaborating! Regards, Jose SEO Ayres

On Thu, May 15, 2025 at 6:36 AM Nurullah Demir @.***> wrote:

nrllh created an issue (HTTPArchive/almanac.httparchive.org#4082) https://github.com/HTTPArchive/almanac.httparchive.org/issues/4082 Performance 2025

[image: Performance illustration] https://raw.githubusercontent.com/HTTPArchive/almanac.httparchive.org/main/src/static/images/2019/performance/hero_lg.jpg

If you're interested in contributing to the Performance chapter of the 2025 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Authors'-Guide, reviewer https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Reviewers'-Guide, analyst https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Analysts'-Guide, and/or editor https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Editors'-Guide. You can find more details about this year’s Call for Contributions here https://github.com/HTTPArchive/almanac.httparchive.org/discussions/4062.

💬 Please make sure to join #web-almanac-Performance https://join.slack.com/t/httparchive/shared_invite/zt-45sgwmnb-eDEatOhqssqNAKxxOSLAaA on Slack for team coordination. Content team Lead Authors Reviewers Analysts Editors Coordinator

• @hfhashmi https://github.com/hfhashmi @siakaramalegos https://github.com/siakaramalegos @macioseo https://github.com/macioseo - @mikaelaraujo https://github.com/mikaelaraujo 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 https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle#0-create-content-team

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

1. Plan content https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle#1-plan-content

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

2. Gather data https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle#2-gather-data

   • 📆 July 1 Custom metrics completed - 🔑 Analysts
     • Analysts have added all necessary custom metrics https://github.com/HTTPArchive/custom-metrics/blob/main/README.md and drafted a PR (example https://github.com/HTTPArchive/almanac.httparchive.org/pull/1087) to track query progress.
   • 📆 July 1 HTTP Archive Crawl - 🔑 HA Team
     • HTTP Archive runs the June crawl.

3. Validate results https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle#3-validate-results

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

4. Draft content https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle#4-draft-content

   • 📆 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 https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle#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 <#m_5683359124095291024_>

   • 📆 December 15 Live Stream - 🔑 Content Team

Chapter resources <#m_5683359124095291024_chapter-resources>

Google Docs, Sheets, and other resources will be added soon.

— Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/4082, or unsubscribe https://github.com/notifications/unsubscribe-auth/BSPP2Q5KKX5DUKVL4IUYDWT26RU4VAVCNFSM6AAAAAB3656ULCVHI2DSMVQWIX3LMV43ASLTON2WKOZTGAZDGMRYGQ3DSMQ . You are receiving this because you were mentioned.Message ID: @.***>

[macioseo]

Hi, Mikael, i'm in.

Jose Ayres

On Thu, May 15, 2025 at 6:37 AM Mikael Araújo @.***> wrote:

mikaelaraujo left a comment (HTTPArchive/almanac.httparchive.org#4082) https://github.com/HTTPArchive/almanac.httparchive.org/issues/4082#issuecomment-2883355531

@macioseo https://github.com/macioseo I'm pitching you as an analyst, but feel free to contribute as an author if you wish. Join us at: https://join.slack.com/t/httparchive/shared_invite/zt-45sgwmnb-eDEatOhqssqNAKxxOSLAaA

— Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/4082#issuecomment-2883355531, or unsubscribe https://github.com/notifications/unsubscribe-auth/BSPP2Q7NUWJF725XZVFQXY326RVANAVCNFSM6AAAAAB3656ULCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBTGM2TKNJTGE . You are receiving this because you were mentioned.Message ID: @.***>

[siakaramalegos]

The SEO chapter might be a better fit if you want to be an author. The performance chapter typically requires a deep knowledge of web performance and front-end development. Though you can learn more about it in an analyst role if you're strong in SQL and the author is familiar with the available data.

[macioseo]

@siakaramalegos @mikaelaraujo I gave it some more thought and came to the conclusion that it would be better to focus on the SEO chapter.

[himanshujariyal]

I would like to +1 as an author. I bring a few years of experience in web performance, along with a background in front-end development.

[mikaelaraujo]

@himanshujariyal - ok @25prathamesh I addressed you as an author.

[nrllh]

@tannerhodges I assigned you as an analyst for this chapter, thank you!

All:

Please make sure to join #web-almanac-performance on Slack for team coordination

[mikaelaraujo]

@25prathamesh Could you please take the lead role for this chapter?

[mikaelaraujo]

The team for this chapter 90% formed, so we can go ahead. I am very excited about what's to come :)

@25prathamesh @hfhashmi @himanshujariyal @siakaramalegos @tannerhodges

Please make sure to:

1. Join the Official Chapter Slack [#web-almanac-performance];
2. Schedule a first meeting for designing the chapter content.

If you have any questions or need for additional help, let me know.

[nrllh]

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

[25prathamesh]

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

Yes, added meeting link in Slack channel

[25prathamesh]

HI Team, I have updated Planning Doc

Please feel free to review it and start adding your inputs, suggestions, or comments directly in doc.

I’ve outlined the initial structure for this year’s Performance chapter, including: Updated sections from last year, which we want to use (e.g,. Core Web Vitals, LCP/INP) New proposed topics like Navigation Type, Speculation Rules, and Early Hints Data sources for new topics

As discussed over the Slack channel, we will connect today for the Kickoff Meeting