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

Add performance budget guidance #451

Closed
1 task done
jeddy3 opened this issue Jan 3, 2019 · 3 comments · Fixed by #608
Closed
1 task done

Add performance budget guidance #451

jeddy3 opened this issue Jan 3, 2019 · 3 comments · Fixed by #608
Projects

Comments

@jeddy3
Copy link
Contributor

jeddy3 commented Jan 3, 2019

As a consumer of the design system
I want guidance on performance budgets
So that I can ensure my product is fast and consistent with other products

Description

Possible metrics:

First Contentful Paint - under 2s
First Meaningful Paint - under 2s
Time to Interactive - under 3s

Links and resources

Acceptance Criteria

  • Add guidance
@olliewright
Copy link

olliewright commented Jan 4, 2019 via email

@jeddy3 jeddy3 added this to Backlog in Board Jan 18, 2019
@jeddy3 jeddy3 moved this from Backlog to To do in Board Feb 8, 2019
@jeddy3 jeddy3 moved this from To do to In progress in Board Feb 15, 2019
Board automation moved this from In progress to Done Feb 15, 2019
@jeddy3
Copy link
Contributor Author

jeddy3 commented Apr 10, 2019

Who has the fastest website in F1?:

It's great to see HTTPS, HTTP/2, gzip, minification, and decent caching widely used. These are things folks in the performance community have been pushing for a long time, and it seems like it's paid off.

@jeddy3
Copy link
Contributor Author

jeddy3 commented Apr 12, 2019

Performance budgets that stick:

To be effective, a performance budget has to be concrete, meaningful, integrated, and enforced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Board
Done
Development

Successfully merging a pull request may close this issue.

2 participants