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

Web performance #102

Open
ascott1 opened this issue Feb 5, 2016 · 1 comment
Open

Web performance #102

ascott1 opened this issue Feb 5, 2016 · 1 comment
Assignees

Comments

@ascott1
Copy link
Member

ascott1 commented Feb 5, 2016

Related to #99. Notes from the front-end team meeting held on 02/05

How do we get there?

  • There’s a number of grunt/gulp tasks to measure performance while in Development.
  • There’s gulp tasks for setting performance budgets. Can we talk about those in the standards?
  • Is everyone aware of the throttling capability in DevTools? Sometimes I load pages using a 56k modem to see the difference.
  • Discussing performance budgets in the front-end standards

Recommended steps

  1. Discuss and determine performance budget guidelines/standards
  2. Add them to the front-end standards
  3. Implement gulp/grunt tasks as part of cf generator

How do we measure success?

  • New Relic has performance stats and we can see what our performance looks like in Production
  • Should a performance budget be part of the SAG review?
@ascott1
Copy link
Member Author

ascott1 commented Mar 4, 2016

Needs for MVP (discussed in meeting 3/4):

  • Best practices
  • Performance budget

@ascott1 ascott1 self-assigned this Mar 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant