Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query metrics: Chapter 7. Performance #88

Closed
24 tasks done
rviscomi opened this issue Jul 23, 2019 · 3 comments · Fixed by #174
Closed
24 tasks done

Query metrics: Chapter 7. Performance #88

rviscomi opened this issue Jul 23, 2019 · 3 comments · Fixed by #174
Assignees
Labels
analysis Querying the dataset ASAP This issue is blocking progress

Comments

@rviscomi
Copy link
Member

rviscomi commented Jul 23, 2019

Part Chapter Authors Reviewers Tracking Issue
II. User Experience 7. Performance @rviscomi @zeman @JMPerez @OBTo @sergeychernyshev #9

READ ME!

All of the metrics in the table below have been marked as Able To Query during the metrics triage. The analyst assigned to each metric is expected to write the corresponding query and submit a PR to have it reviewed and added to the repo.

In order to stay on schedule and have the data ready for authors, please have all metrics reviewed and merged by August 5.

Assignments

ID Metric description Analyst Notes
07.01 global distribution of FCP fast/avg/slow @rviscomi  
07.02 global distribution of FID fast/avg/slow @rviscomi  
07.03 % of fast FCP websites @rviscomi  
07.04 % of fast FID websites @rviscomi  
07.05 % of fast FCP+FID websites, per PSI definition @rviscomi  
07.06 % of websites with offline experiences @rviscomi  
07.07 country/region comparison of any/all of the above @rviscomi  
07.08 mobile vs desktop comparison of any/all of the above @rviscomi  
07.09 ECT comparison of any/all of the above @rviscomi  
07.10 first/last painted hero @raghuramakrishnan71  
07.11 H1 rendering time @raghuramakrishnan71  
07.12 Largest Image @raghuramakrishnan71  
07.13 Largest Background Image @raghuramakrishnan71  
07.14 Visually Complete @raghuramakrishnan71 summary_pages, visualComplete
07.15 First CPU Idle @raghuramakrishnan71 lighthouse, reports
07.16 Time To Interactive @raghuramakrishnan71 lighthouse, reports
07.17 Blocking CSS requests @raghuramakrishnan71  
07.18 Blocking JS request @raghuramakrishnan71  
07.19 Time To First Byte (Backend) @raghuramakrishnan71 summary_pages, ttfb
07.20 Scripting CPU time @raghuramakrishnan71 pages, payload
07.21 Layout CPU time @raghuramakrishnan71 pages, payload
07.22 Paint CPU time @raghuramakrishnan71 pages, payload
07.23 Loading CPU time @raghuramakrishnan71  
07.24 Lighthouse Performance Score @raghuramakrishnan71 lighthouse, reports

Checklist of metrics to be merged

  • 07.01 global distribution of FCP fast/avg/slow
  • 07.02 global distribution of FID fast/avg/slow
  • 07.03 % of fast FCP websites
  • 07.04 % of fast FID websites
  • 07.05 % of fast FCP+FID websites, per PSI definition
  • 07.06 % of websites with offline experiences
  • 07.07 country/region comparison of any/all of the above
  • 07.08 mobile vs desktop comparison of any/all of the above
  • 07.09 ECT comparison of any/all of the above
  • 07.10 first/last painted hero
  • 07.11 H1 rendering time
  • 07.12 Largest Image
  • 07.13 Largest Background Image
  • 07.14 Visually Complete
  • 07.15 First CPU Idle
  • 07.16 Time To Interactive
  • 07.17 Blocking CSS requests
  • 07.18 Blocking JS request
  • 07.19 Time To First Byte (Backend)
  • 07.20 Scripting CPU time
  • 07.21 Layout CPU time
  • 07.22 Paint CPU time
  • 07.23 Loading CPU time
  • 07.24 Lighthouse Performance Score
@rviscomi rviscomi added the analysis Querying the dataset label Jul 23, 2019
@rviscomi rviscomi added this to the Content written milestone Jul 23, 2019
@rviscomi rviscomi self-assigned this Jul 23, 2019
@raghuramakrishnan71
Copy link
Contributor

@rviscomi i have not used git for creating PR (i assume PR is a pull request) earlier. Can you please point me to documentation/steps which can help me get started? I can then start adding queries assigned to me.

@rviscomi
Copy link
Member Author

@raghuramakrishnan71 sure, the GitHub Help site has a lot of useful docs:

https://help.github.com/en/articles/fork-a-repo
https://help.github.com/en/articles/about-pull-requests
https://help.github.com/en/articles/creating-a-pull-request

Worst case scenario, you can use the GitHub web UI to start the pull request by uploading files directly. Go to https://github.com/HTTPArchive/almanac.httparchive.org/tree/master/sql/2019/07_Performance and select "Create a new branch for this commit and start a pull request":

image

@rviscomi rviscomi added the ASAP This issue is blocking progress label Sep 4, 2019
@rviscomi rviscomi mentioned this issue Sep 8, 2019
@rviscomi
Copy link
Member Author

rviscomi commented Sep 24, 2019

@zeman I've saved the results of the lab metric to this sheet. I'll also be adding the results of the field metrics there as well. I have some ideas for the outline of our chapter, I'll share a doc to get the ball rolling.

Also, while I'm working on the field metrics, please go through the lab results and let me know if anything looks questionable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analysis Querying the dataset ASAP This issue is blocking progress
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants