Analyze your user setup
Beta release limitations
The new Site optimizer performance tools are in beta. In future releases, expect to see changes including new features and adjustments to metric definitions.
The new Site optimizer includes insights into how your site’s load times are affected by the tools and characteristics of your end users as they access Jira. Specifically, insights cover five areas:
Network speed
CPU core count
Network protocol (HTTP/1.1 vs. HTTP/2)
Operating system
Browser
Each of the five areas may impact the performance that end users experience on your Jira site. The User setup screen contains data from your own end users that can help you understand which areas, if any, are influencing the performance of your specific site.
Understanding your User setup data
Compare user load times across different cohorts
Use this chart to understand the effect that different characteristics have on your site’s load times.
For example, select Network speed in the “Group by” filter in the top right. If load times are significantly worse for users with slow network speeds, then increasing network speed may improve load times. Analyzing multiple segments reveals a cutoff point for each characteristic, above which performance improves. This data reflects only your site, ensuring the insights apply directly to you.
On some characteristics, there may be no significant difference. For example, you may see negligible differences between users on Chrome versus Firefox. In these cases, there's no cause for further investigation.
Analyze your user distribution
Once you’ve concluded that a certain characteristic impacts end user performance, you’ll want to know how many of your users display that characteristic. The user distribution charts display the percentage of your users displaying each characteristic in a given time period.
Continuing the example of slow network speeds, your site will suffer more if many users experience slow speeds. For instance, if 40% of users have speeds between 0 and 5 Mbps, you should urgently investigate the root cause, such as VPN or network security issues. If only 3% of users have these speeds, consider investigating network speed only for those who request support.
How do we collect this data?
Load time data is collected using Atlassian’s internal telemetry. User setup data is collected for each load event using standard HTTP headers.