5.9 sec in total
929 ms
4.7 sec
272 ms
Welcome to jira.xwiki.org homepage info - get ready to check Jira Xwiki best content for India right away, or after learning these important things about jira.xwiki.org
Visit jira.xwiki.orgWe analyzed Jira.xwiki.org page load time and found that the first response time was 929 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
jira.xwiki.org performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value8.7 s
1/100
25%
Value8.4 s
18/100
10%
Value320 ms
76/100
30%
Value0.001
100/100
15%
Value8.7 s
36/100
10%
929 ms
92 ms
461 ms
365 ms
373 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 99% of them (126 requests) were addressed to the original Jira.xwiki.org, 1% (1 request) were made to Xwiki.org. The less responsive or slowest element that took the longest time to load (929 ms) belongs to the original domain Jira.xwiki.org.
Page size can be reduced by 89.8 kB (77%)
116.5 kB
26.7 kB
In fact, the total size of Jira.xwiki.org main page is 116.5 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. 70% of websites need less resources to load. HTML takes 108.3 kB which makes up the majority of the site volume.
Potential reduce by 89.4 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 15.8 kB, which is 15% 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 89.4 kB or 83% of the original size.
Potential reduce by 460 B
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. Jira Xwiki images are well optimized though.
Number of requests can be reduced by 87 (71%)
122
35
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jira Xwiki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
jira.xwiki.org
929 ms
MyJiraHome.jspa
92 ms
Dashboard.jspa
461 ms
batch.css
365 ms
batch.css
373 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.css
182 ms
batch.js
726 ms
batch.js
654 ms
com.atlassian.gadgets.embedded:gadget-core-resources.js
188 ms
com.atlassian.gadgets.embedded:gadget-container-resources.js
273 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.js
278 ms
jira.webresources:calendar-en.js
358 ms
com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources.js
388 ms
com.atlassian.jira.ext.calendar:browse-project-tip.js
448 ms
shortcuts.js
463 ms
tips
232 ms
logo.png
220 ms
appswitcher
201 ms
atlassian-icons.woff
195 ms
135 ms
icons_module.png
132 ms
dashboard-diagnostics
222 ms
ifr
193 ms
ifr
213 ms
ifr
173 ms
ifr
178 ms
ifr
175 ms
ifr
268 ms
ifr
281 ms
ifr
279 ms
ifr
281 ms
auth-refresh.js
189 ms
batch.css
267 ms
jira.webresources:list-styles.css
259 ms
jira.webresources:inline-layer.css
262 ms
jira.webresources:dropdown.css
265 ms
batch.js
520 ms
jira.webresources:content-retrievers.js
281 ms
jira.webresources:inline-layer.js
353 ms
jira.webresources:list.js
351 ms
jira.webresources:dropdown.js
356 ms
batch.css
368 ms
batch.js
745 ms
jira.webresources:captcha.css
269 ms
com.atlassian.auiplugin:aui-reset.css
299 ms
com.atlassian.auiplugin:aui-page-typography.css
300 ms
jira.webresources:captcha.js
405 ms
com.atlassian.jira.gadgets:g-login.js
406 ms
com.atlassian.auiplugin:aui-avatars.css
402 ms
com.atlassian.auiplugin:aui-page-layout.css
409 ms
com.atlassian.auiplugin:ajs-gadgets-base.css
437 ms
com.atlassian.auiplugin:aui-navigation.css
440 ms
com.atlassian.auiplugin:aui-experimental-iconfont.css
445 ms
com.atlassian.auiplugin:aui-header.css
446 ms
com.atlassian.auiplugin:aui-page-header.css
448 ms
com.atlassian.auiplugin:aui-dropdown2.css
523 ms
com.atlassian.auiplugin:ajs-html5shim.css
524 ms
com.atlassian.auiplugin:aui-toolbar2.css
532 ms
com.atlassian.auiplugin:ajs.css
533 ms
com.atlassian.gadgets.publisher:ajax.css
536 ms
com.atlassian.gadgets.publisher:ajs-gadgets.css
614 ms
jira.webresources:icons.css
617 ms
com.atlassian.jira.gadgets:core-gadget-resources.css
625 ms
com.atlassian.streams:datepicker.css
620 ms
com.atlassian.streams.actions:commentActionHandlers.css
620 ms
com.atlassian.streams:streamsWebResources.css
772 ms
com.atlassian.gadgets.publisher:ajs-gadgets-lite.css
752 ms
jira.webresources:autocomplete.css
757 ms
com.atlassian.jira.ext.calendar:issues-calendar-resource.css
704 ms
com.atlassian.auiplugin:jquery-lib.js
789 ms
com.atlassian.auiplugin:jquery-compatibility.js
699 ms
com.atlassian.auiplugin:aui-core.js
689 ms
com.atlassian.auiplugin:ajs-gadgets-base.js
688 ms
com.atlassian.auiplugin:ajs-raphael.js
719 ms
com.atlassian.auiplugin:ajs-contextpath.js
627 ms
com.atlassian.auiplugin:aui-header.js
636 ms
com.atlassian.auiplugin:aui-dropdown2.js
639 ms
com.atlassian.auiplugin:ajs.js
676 ms
com.atlassian.gadgets.publisher:templates.js
610 ms
com.atlassian.gadgets.publisher:util.js
612 ms
com.atlassian.gadgets.publisher:ajax.js
564 ms
com.atlassian.gadgets.publisher:ajs-gadgets.js
577 ms
jira.webresources:almond.js
570 ms
jira.webresources:util-lite.js
572 ms
com.atlassian.jira.gadgets:core-gadget-resources.js
579 ms
com.atlassian.streams:date-default.js
613 ms
com.atlassian.streams:date-js.js
618 ms
com.atlassian.streams:datepicker.js
629 ms
com.atlassian.streams:streams-parent-js.js
632 ms
com.atlassian.streams.actions:inlineActionsJs.js
632 ms
com.atlassian.streams.actions:commentActionHandlers.js
558 ms
com.atlassian.streams.jira.inlineactions:actionHandlers.js
615 ms
com.atlassian.streams:streamsWebResources.js
617 ms
com.atlassian.streams:streamsGadgetResources.js
612 ms
com.atlassian.gadgets.publisher:ajs-gadgets-lite.js
645 ms
jira.webresources:browser-properties.js
568 ms
com.atlassian.auiplugin:ajs-underscorejs.js
567 ms
com.atlassian.auiplugin:ajs-backbone.js
603 ms
com.atlassian.soy.soy-template-plugin:soy-deps.js
613 ms
jira.webresources:util.js
610 ms
jira.webresources:jquery-plugin-textoverflow.js
478 ms
jira.webresources:autocomplete.js
495 ms
com.atlassian.jira.ext.calendar:issues-calendar-resource.js
496 ms
generate
529 ms
generate
543 ms
generate
610 ms
generate
611 ms
loading.gif
598 ms
preferences
267 ms
streams
680 ms
gadget-loading.gif
310 ms
throbber.gif
314 ms
feed-icon.png
331 ms
full-view-icon.png
405 ms
list-view-icon.png
402 ms
htmlcalendar.html
356 ms
projectavatar
348 ms
projectavatar
342 ms
projectavatar
383 ms
projectavatar
426 ms
projectavatar
424 ms
projectavatar
463 ms
projectavatar
544 ms
projectavatar
535 ms
ico_reports.png
542 ms
menu_indicator_for_light_backgrounds.gif
574 ms
ico_filters.png
581 ms
jira.xwiki.org accessibility score
jira.xwiki.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
jira.xwiki.org SEO score
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.xwiki.org 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.xwiki.org 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.xwiki.org
Open Graph description is not detected on the main page of Jira Xwiki. 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: