Last post we touched on TLS and Firewall best practices to get the best performance from Atlassian Cloud applications. This post we’ll touch on client hardware and network speeds that help get the best performance from Atlassian Cloud applications.
Modern teams rely on Atlassian to collaborate and deliver value at scale. While Atlassian Cloud is engineered for speed and reliability, our research shows that client-side hardware and network configuration play a critical role in the end-user experience. This post outlines Atlassian’s recommendations for client hardware and network requirements, the measurable impact of these factors, and actionable steps to ensure your teams get the best possible performance.
Why client hardware and network matters
Every interaction with Jira and Confluence—whether loading a dashboard, editing a page, or searching for issues—depends on the capabilities of the customer’s device and the speed of their internet connection. Even with a perfectly optimized cloud backend, insufficient client resources or slow connectivity can introduce delays that compound across teams and workflows.
Key impact:
Across large organizations, these delays can translate into significant productivity loss.
Recommended client configuration
Based on extensive performance testing and customer feedback, Atlassian recommends the following client-side specifications for optimal performance:
|
Factor
|
Atlassian's Recommendation
|
|
CPU Cores
|
8 or more*
|
|
Internet Speed
|
10 Mbps download speed or higher
|
|
Browser
|
Latest version of a modern web browser (Chrome, Edge, Safari, Firefox, Dia, etc.)
|
|
Network Enhancements
|
Allowlisting Atlassian domains, HTTP/2 enabled
|
Details
-
CPU Cores*: Devices with fewer than 8 cores may experience slower page loads and reduced responsiveness, especially when multitasking or running multiple browser tabs.
- * - CPU models & speed differ greatly between each other. Newer CPU models with the best speeds may give incredibly performance with only 1 or 2 cores on the client hardware. While older CPU models with slower speeds may still give sub-optimal performance even with 8 or more cores. CPU models and speeds are not exposed to web applications by modern browsers because of security & privacy concerns, while number of cores is exposed. The best guidance we can give is the number of cores based but please know that CPU models and speeds is the bigger factor here with performance.
-
Internet Speed: A download speed of at least 10 Mbps is recommended. Lower speeds can cause noticeable delays, particularly when loading large pages or attachments.
-
Browser: Use the latest version of modern browser for the best compatibility and performance (Chrome, Edge, Firefox, Dia, etc.).
-
Network Configuration: For organizations with strict network policies, enabling allowlisting and HTTP/2 can further improve performance. - Link to post to learn more
How client configuration impacts performance
When client hardware or network speed falls below these recommendations, users may experience:
-
Slower initial page loads
-
Laggy interactivity (e.g., editing, searching, commenting)
-
Delays in rendering large or complex pages
Our performance and support teams have analyzed thousands of customer environments and confirmed that client-side limitations are a key contributor to these slowdowns.
Additional best practices
-
Allowlisting and HTTP/2: For organizations using proxies, firewalls, or secure web gateways, ensure Atlassian domains are allowlisted and HTTP/2 is enabled. This prevents protocol downgrades and ensures efficient resource loading. - Link to post to learn more
-
Monitor and validate: Regularly test user experience across different devices and network conditions. Use browser developer tools or HAR files to diagnose performance bottlenecks.
Summary
By ensuring your teams meet or exceed these minimum client hardware and network requirements, you can maximize the value of Atlassian applications and deliver a fast, responsive experience for every user.
