Tools & Wizards About Us
webarchive.jira.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

webarchive.jira.com

Log in with Atlassian account

Page Load Speed

3.1 sec in total

First Response

158 ms

Resources Loaded

2.8 sec

Page Rendered

90 ms

webarchive.jira.com screenshot

About Website

Click here to check amazing Webarchive Jira content for United States. Otherwise, check out these important facts you probably never knew about webarchive.jira.com

Log in to Jira, Confluence, and all other Atlassian Cloud products here. Not an Atlassian user? Sign up for free.

Visit webarchive.jira.com

Key Findings

We analyzed Webarchive.jira.com page load time and found that the first response time was 158 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

webarchive.jira.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.352

31/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

webarchive.jira.com

158 ms

webarchive.jira.com

727 ms

batch.css

168 ms

batch.css

502 ms

jira.webresources:groupbrowser.css

208 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 28% of them (24 requests) were addressed to the original Webarchive.jira.com, 66% (57 requests) were made to D1ixbz5qgnvms3.cloudfront.net and 3% (3 requests) were made to Dctkfvs9istwk.cloudfront.net. The less responsive or slowest element that took the longest time to load (727 ms) belongs to the original domain Webarchive.jira.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.7 kB (67%)

Content Size

414.4 kB

After Optimization

138.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Webarchive.jira.com main page is 414.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. 40% of websites need less resources to load. Javascripts take 350.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 48.0 kB

  • Original 60.5 kB
  • After minification 58.7 kB
  • After compression 12.5 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 48.0 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 166 B

  • Original 3.1 kB
  • After minification 2.9 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. Webarchive Jira images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 227.5 kB

  • Original 350.8 kB
  • After minification 350.8 kB
  • After compression 123.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 227.5 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (77%)

Requests Now

82

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webarchive Jira. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

webarchive.jira.com

webarchive.jira.com

158 ms

webarchive.jira.com

webarchive.jira.com

727 ms

batch.css

batch.css

168 ms

batch.css

batch.css

502 ms

jira.webresources:groupbrowser.css

jira.webresources:groupbrowser.css

208 ms

jira.webresources:group-pickers.css

jira.webresources:group-pickers.css

448 ms

batch.js

batch.js

716 ms

batch.js

batch.js

448 ms

batch.js

batch.js

535 ms

batch.js

batch.js

318 ms

batch.js

batch.js

448 ms

jira.webresources:group-label-lozenge.js

jira.webresources:group-label-lozenge.js

534 ms

jira.webresources:groupbrowser.js

jira.webresources:groupbrowser.js

534 ms

jira.webresources:group-pickers.js

jira.webresources:group-pickers.js

539 ms

jira.webresources:ie-imitation-placeholder.js

jira.webresources:ie-imitation-placeholder.js

581 ms

jira.webresources:jira-project-issuetype-fields.js

jira.webresources:jira-project-issuetype-fields.js

605 ms

jira.webresources:jira-fields.js

jira.webresources:jira-fields.js

626 ms

jira.webresources:calendar-en.js

jira.webresources:calendar-en.js

612 ms

jira.webresources:calendar-localisation-moment.js

jira.webresources:calendar-localisation-moment.js

617 ms

shortcuts.js

shortcuts.js

245 ms

main.js

main.js

79 ms

main.js

main.js

75 ms

main.js

main.js

74 ms

resources

resources

342 ms

jira-logo-scaled.png

jira-logo-scaled.png

90 ms

resources

resources

291 ms

appswitcher

appswitcher

239 ms

tools_20.png

tools_20.png

95 ms

64jira.png

64jira.png

206 ms

dashboard-diagnostics

dashboard-diagnostics

386 ms

ga.js

ga.js

53 ms

admin

admin

193 ms

announcement

announcement

198 ms

atlassian-icons.woff

atlassian-icons.woff

302 ms

ifr

ifr

236 ms

resources

resources

387 ms

__utm.gif

__utm.gif

13 ms

batch.js

batch.js

140 ms

batch.js

batch.js

94 ms

auth-refresh.js

auth-refresh.js

82 ms

com.atlassian.auiplugin:ajs-gadgets-base.css

com.atlassian.auiplugin:ajs-gadgets-base.css

162 ms

com.atlassian.gadgets.publisher:ajax.css

com.atlassian.gadgets.publisher:ajax.css

97 ms

com.atlassian.gadgets.publisher:ajs-gadgets-lite.css

com.atlassian.gadgets.publisher:ajs-gadgets-lite.css

109 ms

jira.webresources:icons.css

jira.webresources:icons.css

117 ms

com.atlassian.jira.gadgets:core-gadget-resources.css

com.atlassian.jira.gadgets:core-gadget-resources.css

378 ms

jira.webresources:list-styles.css

jira.webresources:list-styles.css

384 ms

jira.webresources:inline-layer.css

jira.webresources:inline-layer.css

246 ms

jira.webresources:dropdown.css

jira.webresources:dropdown.css

199 ms

jira.webresources:almond.js

jira.webresources:almond.js

204 ms

com.atlassian.plugins.jquery:jquery.js

com.atlassian.plugins.jquery:jquery.js

343 ms

com.atlassian.auiplugin:jquery-compatibility.js

com.atlassian.auiplugin:jquery-compatibility.js

284 ms

com.atlassian.auiplugin:aui-deprecation.js

com.atlassian.auiplugin:aui-deprecation.js

292 ms

com.atlassian.auiplugin:aui-core.js

com.atlassian.auiplugin:aui-core.js

343 ms

com.atlassian.auiplugin:ajs-gadgets-base.js

com.atlassian.auiplugin:ajs-gadgets-base.js

370 ms

com.atlassian.gadgets.publisher:templates.js

com.atlassian.gadgets.publisher:templates.js

422 ms

com.atlassian.gadgets.publisher:util.js

com.atlassian.gadgets.publisher:util.js

424 ms

com.atlassian.gadgets.publisher:ajax.js

com.atlassian.gadgets.publisher:ajax.js

456 ms

com.atlassian.gadgets.publisher:ajs-gadgets-lite.js

com.atlassian.gadgets.publisher:ajs-gadgets-lite.js

462 ms

jira.webresources:aui-core-amd-shim.js

jira.webresources:aui-core-amd-shim.js

460 ms

jira.webresources:legacy-namespacing.js

jira.webresources:legacy-namespacing.js

466 ms

com.atlassian.auiplugin:ajs-underscorejs.js

com.atlassian.auiplugin:ajs-underscorejs.js

504 ms

jira.webresources:ajs-underscorejs-amd-shim.js

jira.webresources:ajs-underscorejs-amd-shim.js

509 ms

jira.webresources:jira-metadata.js

jira.webresources:jira-metadata.js

542 ms

jira.webresources:aui-extensions.js

jira.webresources:aui-extensions.js

539 ms

jira.webresources:jira-events.js

jira.webresources:jira-events.js

547 ms

jira.webresources:browser-properties.js

jira.webresources:browser-properties.js

554 ms

jira.webresources:top-same-origin-window.js

jira.webresources:top-same-origin-window.js

586 ms

jira.webresources:util-lite.js

jira.webresources:util-lite.js

651 ms

com.atlassian.jira.gadgets:core-gadget-resources.js

com.atlassian.jira.gadgets:core-gadget-resources.js

635 ms

jira.webresources:content-retrievers.js

jira.webresources:content-retrievers.js

624 ms

jira.webresources:inline-layer.js

jira.webresources:inline-layer.js

632 ms

jira.webresources:list.js

jira.webresources:list.js

670 ms

jira.webresources:dropdown.js

jira.webresources:dropdown.js

671 ms

batch.css

batch.css

82 ms

batch.js

batch.js

165 ms

generate

generate

81 ms

loading.gif

loading.gif

93 ms

projectavatar

projectavatar

88 ms

projectavatar

projectavatar

87 ms

projectavatar

projectavatar

78 ms

projectavatar

projectavatar

70 ms

projectavatar

projectavatar

79 ms

projectavatar

projectavatar

80 ms

ico_reports.png

ico_reports.png

86 ms

menu_indicator_for_light_backgrounds.gif

menu_indicator_for_light_backgrounds.gif

80 ms

ico_filters.png

ico_filters.png

89 ms

Accessibility Review

webarchive.jira.com accessibility score

77

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

webarchive.jira.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

webarchive.jira.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webarchive.jira.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Webarchive.jira.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.

Social Sharing Optimization

webarchive.jira.com

Open Graph description is not detected on the main page of Webarchive Jira. 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: