Comments (9)
from almanac.httparchive.org.
Added @henrisGH (Henri Helvetica) as an author π and invited to @HTTPArchive/authors
from almanac.httparchive.org.
Added @flowlabs as a reviewer π
from almanac.httparchive.org.
@khempenius @henrisgh @paulcalvano @flowlabs we're hoping to have the list of metrics for each chapter finalized today. There are only 3 metrics listed for this chapter at #20 (comment). Could you take one last look and when you think it's in a good place tick the last TODO checkbox and close this issue? Thanks!
Also @henrisgh could you please go to https://github.com/HTTPArchive and accept your invitation to the Authors team? This ensures that you get author-specific communications, I can assign issues to you, and you can edit issues like this one.
from almanac.httparchive.org.
TLDR; I'll take care of updating & closing this issue. For those curious below was my thought process on this:
I thought the entire analysis and writeup was due today so these were the metrics I ended up already calculating:
- Distribution of resource size: (p10, p25, p50, p75, p90) x (total, JS, CSS HTML, Fonts). In addition, how this has changed over the past year.
- Distribution of resource quantity: (p10, p25, p50, p75, p90) x (total, JS, CSS HTML, Fonts). In addition, how this has changed over the past year and since the release of H2.
I found that the number of CSS & JS resources has increased moderately since H2's release, but I don't think that's enough to draw a conclusion from (It is it H2? Or is it just sites getting larger?)
If we wanted to go deeper on this H2 detail (this is interesting, but I don't think it's essential to talking about page weight), I would propose these metric(s):
- Determine which sites serve the majority of their first-party content using H2. (This % alone would be interesting. I also wonder if there would be a significant difference between using .5 and .9 as the threshold.)
- For those sites using H2, look at how CSS & JSS resource quantities varied before and after H2 adoption
from almanac.httparchive.org.
No just the metrics are due today π See this timeline for a better idea of when everything comes together.
Thanks for closing this out Katie!
For those sites using H2, look at how CSS & JSS resource quantities varied before and after H2 adoption
We do have historical data but no guarantee that the pre-H2 data exists for a given page. The URL corpus thrashed quite a bit over the last year as we transitioned from Alexa to CrUX. So these results might be inconclusive.
from almanac.httparchive.org.
Two other things came to mind:
If you're interested in writing the queries for this chapter, can I also add you to the Data Analyst team? Would you also be interested in writing the queries for #21?
In case you have an early draft ready to go, that might actually be helpful as a placeholder for the UX teams to start exploring data viz and other design options. Would you be open to sharing what you have so far?
from almanac.httparchive.org.
Great thanks! Added you as an editor to the Metrics Triage sheet and put your name down for this chapter's metrics. More info about triaging in #33.
from almanac.httparchive.org.
Good news, @tammyeverts is signing on as a coauthor! π Thanks Tammy! I've also sent you an invite to the Authors team on GitHub. You can accept by visiting https://github.com/HTTPArchive/
(@henrisgh you've also got an outstanding invitation to the Authors team, so follow the link above to accept.)
from almanac.httparchive.org.
Related Issues (20)
- Write 2022 foreword
- Credit contributors of closed chapters
- "2022" hangs off the edge on the home hero
- Put class name in `code`
- (nit) Issue with the 2022 seo chapter HOT 1
- Provide 2022 social sharing image HOT 1
- Hosting HOT 4
- Broken query link in 2022 JS fig 2.7 HOT 2
- Search results page lists years out of order HOT 3
- webassembly - @luckybai HOT 1
- Jamstack chapter: Netlifyβs conflict of interest should be clearer HOT 4
- Investigate 0 web mentions HOT 6
- Update Lighthouse methodology to include desktop testing HOT 1
- Multiline blockquotes have different font sizes HOT 2
- Center align featured stats HOT 2
- Clean up stale branches HOT 1
- Feedback about dynamic `import()` in JS chapter HOT 3
- Publication dates are relative to client's timezone
- Accessibility 2022: "Half of all web searches are performed by voice" doesnβt fact-check
- Issue with the 2022 sustainability chapter Figure 20.6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from almanac.httparchive.org.