2.6 sec in total
248 ms
2.3 sec
102 ms
Click here to check amazing Jira Squiz content for Australia. Otherwise, check out these important facts you probably never knew about jira.squiz.net
Log in to Jira, Confluence, and all other Atlassian Cloud products here. Not an Atlassian user? Sign up for free.
Visit jira.squiz.netWe analyzed Jira.squiz.net page load time and found that the first response time was 248 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
jira.squiz.net performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value9.0 s
1/100
25%
Value8.9 s
15/100
10%
Value490 ms
59/100
30%
Value0.003
100/100
15%
Value9.5 s
30/100
10%
248 ms
295 ms
272 ms
355 ms
219 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that all of those requests were addressed to Jira.squiz.net and no external sources were called. The less responsive or slowest element that took the longest time to load (729 ms) belongs to the original domain Jira.squiz.net.
Page size can be reduced by 40.8 kB (72%)
56.9 kB
16.2 kB
In fact, the total size of Jira.squiz.net main page is 56.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 49.2 kB which makes up the majority of the site volume.
Potential reduce by 38.7 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 5.3 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 38.7 kB or 79% of the original size.
Potential reduce by 2.1 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Jira Squiz needs image optimization as it can save up to 2.1 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Number of requests can be reduced by 21 (75%)
28
7
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jira Squiz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
jira.squiz.net
248 ms
Dashboard.jspa
295 ms
batch.css
272 ms
batch.css
355 ms
batch.css
219 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.css
223 ms
com.atlassian.labs.hipchat.hipchat-for-jira-plugin:resources.css
227 ms
batch.js
676 ms
batch.js
729 ms
batch.js
441 ms
com.atlassian.gadgets.embedded:gadget-core-resources.js
302 ms
com.atlassian.gadgets.embedded:gadget-container-resources.js
337 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.js
378 ms
jira.webresources:calendar-en.js
405 ms
com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources.js
420 ms
com.atlassian.labs.hipchat.hipchat-for-jira-plugin:resources.js
455 ms
shortcuts.js
480 ms
tips
133 ms
icon-jira-logo.png
100 ms
69 ms
icons_module.png
77 ms
dashboard-diagnostics
180 ms
atlassian-icons.woff
75 ms
ifr
85 ms
auth-refresh.js
70 ms
batch.css
159 ms
jira.webresources:captcha.css
76 ms
com.atlassian.auiplugin:aui-reset.css
78 ms
com.atlassian.auiplugin:aui-page-typography.css
139 ms
batch.js
380 ms
jira.webresources:captcha.js
154 ms
com.atlassian.jira.gadgets:g-login.js
155 ms
jira.squiz.net accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Form elements do not have associated labels
jira.squiz.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
jira.squiz.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jira.squiz.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jira.squiz.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
jira.squiz.net
Open Graph description is not detected on the main page of Jira Squiz. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: