godaddy / godaddy/timings

Quick Starting guide and Documentation is missing

Open
#56 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
45
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Dear GoDaddy team
As you can imagine there is not much capacity in Story Points for innovation per scrum sprint.
We need to go from zero to hero within a couple of days on every investigation/innovation jira ticket.
The documentation you have provided is a thorough one but it is useful only for advanced users.
Could you provide a couple of scenarios that are common and useful as ready and then we can delve-in to more details ?
For example a quick-start guide of how to assert the timing of all the API calls of a certain page is a good use-case. And please add info of why you are using the parameters you are using etc.
Another good example is measuring the case study where you measure the navigation time of the entire page and you just assert against a single number.
You might be able to think of more useful case-studies to include.

Unfortunately we don't have time to learn all the specifics the performance api but we want to use it and improve our performance. Could you help by providing quick start guide either on README.md or in a blog post ?

Many thanks

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.