Post

We’ve decided to take another break for the Web Almanac this year. This wasn’t an easy call to make, but we feel it’s the right one given the huge effort the project takes and not wanting to half-commit. There’s a lot going on at the moment and we’re all pretty busy and many of you are too. 1/4 🧵

discuss.httparchive.orgHTTP ArchiveA place to explore and discuss the web performance trends and best practices.

HTTP Archive 💾

@httparchive.org

16 June

In the meantime we’re going to chip away at some automation to try to take some of the manual effort out of the onerous data querying part of the project so we can consider picking it up again at some point in the future. 2/4

discuss.httparchive.orgHTTP ArchiveA place to explore and discuss the web performance trends and best practices.

HTTP Archive 💾

@httparchive.org

Meanwhile, the HTTP Archive itself isn’t going anywhere! If you have any burning questions about the state of the web in 2026, you can still add new Wappalyzer detections and custom metrics and add new reports (we encourage you to do so!!). 3/4

discuss.httparchive.orgHTTP ArchiveA place to explore and discuss the web performance trends and best practices.

16/6/26, 6:44 pm0 reposts0 likes

HTTP Archive 💾

@httparchive.org

16 June

You can also continue to query the dataset, and share your findings with the community—our Slack and discuss.httparchive.org are always open for new posts. 4/4 🏁

discuss.httparchive.orgHTTP ArchiveA place to explore and discuss the web performance trends and best practices.