3.3 sec in total
159 ms
3 sec
218 ms
Visit jira.lifesize.com now to see the best up-to-date JIRA Life Size content for Colombia and also check out these interesting facts you probably never knew about jira.lifesize.com
Visit jira.lifesize.comWe analyzed Jira.lifesize.com page load time and found that the first response time was 159 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.lifesize.com performance score
159 ms
261 ms
262 ms
144 ms
224 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that all of those requests were addressed to Jira.lifesize.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Jira.lifesize.com.
Page size can be reduced by 45.1 kB (80%)
56.4 kB
11.2 kB
In fact, the total size of Jira.lifesize.com main page is 56.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. 25% of websites need less resources to load. HTML takes 56.4 kB which makes up the majority of the site volume.
Potential reduce by 45.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.1 kB or 80% of the original size.
Number of requests can be reduced by 49 (82%)
60
11
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JIRA Life Size. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
jira.lifesize.com
159 ms
Dashboard.jspa
261 ms
batch.css
262 ms
batch.css
144 ms
batch.css
224 ms
batch.css
142 ms
batch.css
140 ms
com.atlassian.gadgets.dashboard:dashboard.css
249 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.css
269 ms
jira.webresources:global-static.css
481 ms
jira.webresources:old_header_resources.css
274 ms
com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources.css
353 ms
com.atlassian.plugins.atlassian-nav-links-plugin:rotp-projectshortcuts.css
377 ms
com.atlassian.jira.jira-quick-edit-plugin:quick-form.css
387 ms
batch.js
842 ms
batch.js
404 ms
batch.js
783 ms
batch.js
552 ms
batch.js
517 ms
com.atlassian.gadgets.dashboard:dashboard.js
719 ms
com.atlassian.gadgets.embedded:gadget-core-resources.js
610 ms
com.atlassian.gadgets.embedded:gadget-container-resources.js
655 ms
com.atlassian.gadgets.dashboard:gadget-dashboard-resources.js
674 ms
jira.webresources:calendar.js
823 ms
jira.webresources:group-pickers.js
788 ms
jira.webresources:user-pickers.js
803 ms
jira.webresources:jira-fields.js
1048 ms
jira.webresources:calendar-en.js
1091 ms
com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources.js
1096 ms
com.atlassian.plugins.atlassian-nav-links-plugin:rotp-projectshortcuts.js
1096 ms
com.atlassian.jira.jira-quick-edit-plugin:quick-form.js
1179 ms
com.atlassian.jira.jira-quick-edit-plugin:quick-create-issue.js
1180 ms
shortcuts.js
1183 ms
tips
299 ms
jira-logo-scaled.png
138 ms
tools_20.png
136 ms
menu_indicator_for_light_backgrounds.gif
136 ms
dashboard-diagnostics
199 ms
ifr
190 ms
ifr
191 ms
auth-refresh.js
185 ms
com.atlassian.auiplugin:ajs-gadgets-base.css
179 ms
com.atlassian.gadgets.publisher:ajax.css
147 ms
com.atlassian.gadgets.publisher:ajs-gadgets-lite.css
174 ms
jira.webresources:util-lite.css
175 ms
com.atlassian.jira.gadgets:common-lite.css
146 ms
com.atlassian.jira.gadgets:common-lite.css
320 ms
com.atlassian.auiplugin:jquery-lib.js
404 ms
com.atlassian.auiplugin:jquery-compatibility.js
278 ms
com.atlassian.auiplugin:aui-core.js
308 ms
com.atlassian.auiplugin:ajs-gadgets-base.js
306 ms
com.atlassian.gadgets.publisher:templates.js
309 ms
com.atlassian.gadgets.publisher:util.js
421 ms
com.atlassian.gadgets.publisher:ajax.js
434 ms
com.atlassian.gadgets.publisher:ajs-gadgets-lite.js
519 ms
jira.webresources:util-lite.js
520 ms
com.atlassian.jira.gadgets:common-lite.js
486 ms
jira.webresources:captcha.css
542 ms
jira.webresources:captcha.js
547 ms
com.atlassian.jira.gadgets:g-login.js
564 ms
intro
98 ms
loading.gif
139 ms
new-image-animated.gif
130 ms
jira.lifesize.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jira.lifesize.com 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.lifesize.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.lifesize.com
Open Graph description is not detected on the main page of JIRA Life Size. 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: