3.5 sec in total
303 ms
3.1 sec
88 ms
Visit jira.aerian.com now to see the best up-to-date Jira Aerian content and also check out these interesting facts you probably never knew about jira.aerian.com
Visit jira.aerian.comWe analyzed Jira.aerian.com page load time and found that the first response time was 303 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
jira.aerian.com performance score
name
value
score
weighting
Value14.5 s
0/100
10%
Value16.5 s
0/100
25%
Value14.5 s
1/100
10%
Value1,200 ms
20/100
30%
Value0
100/100
15%
Value17.1 s
4/100
10%
303 ms
264 ms
204 ms
284 ms
302 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that all of those requests were addressed to Jira.aerian.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Jira.aerian.com.
Page size can be reduced by 44.3 kB (80%)
55.4 kB
11.1 kB
In fact, the total size of Jira.aerian.com main page is 55.4 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. 35% of websites need less resources to load. HTML takes 55.4 kB which makes up the majority of the site volume.
Potential reduce by 44.3 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 6.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 44.3 kB or 80% of the original size.
Number of requests can be reduced by 48 (84%)
57
9
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jira Aerian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
jira.aerian.com
303 ms
Dashboard.jspa
264 ms
batch.css
204 ms
batch.css
284 ms
batch.css
302 ms
batch.css
289 ms
batch.css
291 ms
com.atlassian.gadgets.dashboard:dashboard.css
295 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.css
305 ms
jira.webresources:global-static.css
592 ms
jira.webresources:old_header_resources.css
386 ms
com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources.css
384 ms
com.atlassian.plugins.atlassian-nav-links-plugin:rotp-projectshortcuts.css
391 ms
com.atlassian.jira.jira-quick-edit-plugin:quick-form.css
393 ms
batch.js
1009 ms
batch.js
802 ms
batch.js
478 ms
batch.js
492 ms
com.atlassian.gadgets.dashboard:dashboard.js
607 ms
com.atlassian.gadgets.embedded:gadget-core-resources.js
576 ms
com.atlassian.gadgets.embedded:gadget-container-resources.js
606 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.js
671 ms
jira.webresources:calendar.js
691 ms
jira.webresources:group-pickers.js
693 ms
jira.webresources:user-pickers.js
706 ms
jira.webresources:jira-fields.js
783 ms
jira.webresources:calendar-en.js
784 ms
com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources.js
792 ms
com.atlassian.plugins.atlassian-nav-links-plugin:rotp-projectshortcuts.js
802 ms
com.atlassian.jira.jira-quick-edit-plugin:quick-form.js
889 ms
com.atlassian.jira.jira-quick-edit-plugin:quick-create-issue.js
882 ms
shortcuts.js
900 ms
tips
101 ms
jira-logo-scaled.png
99 ms
dashboard-diagnostics
191 ms
ifr
115 ms
ifr
118 ms
auth-refresh.js
105 ms
com.atlassian.auiplugin:ajs-gadgets-base.css
112 ms
com.atlassian.gadgets.publisher:ajax.css
103 ms
com.atlassian.gadgets.publisher:ajs-gadgets-lite.css
171 ms
jira.webresources:util-lite.css
202 ms
com.atlassian.jira.gadgets:common-lite.css
205 ms
com.atlassian.jira.gadgets:common-lite.css
205 ms
com.atlassian.auiplugin:jquery-lib.js
383 ms
com.atlassian.auiplugin:jquery-compatibility.js
291 ms
com.atlassian.auiplugin:aui-core.js
293 ms
com.atlassian.auiplugin:ajs-gadgets-base.js
301 ms
com.atlassian.gadgets.publisher:templates.js
300 ms
com.atlassian.gadgets.publisher:util.js
301 ms
com.atlassian.gadgets.publisher:ajax.js
402 ms
com.atlassian.gadgets.publisher:ajs-gadgets-lite.js
499 ms
jira.webresources:util-lite.js
412 ms
com.atlassian.jira.gadgets:common-lite.js
408 ms
jira.webresources:captcha.css
400 ms
jira.webresources:captcha.js
473 ms
com.atlassian.jira.gadgets:g-login.js
487 ms
intro
100 ms
loading.gif
113 ms
64jira.png
97 ms
jira.aerian.com accessibility score
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
jira.aerian.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
jira.aerian.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jira.aerian.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Jira.aerian.com 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.aerian.com
Open Graph description is not detected on the main page of Jira Aerian. 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: