Tools & Wizards About Us
mediaparts.jira.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

mediaparts.jira.com

Log in with Atlassian account

Page Load Speed

2.1 sec in total

First Response

157 ms

Resources Loaded

1.9 sec

Page Rendered

86 ms

mediaparts.jira.com screenshot

About Website

Welcome to mediaparts.jira.com homepage info - get ready to check Mediaparts Jira best content for United States right away, or after learning these important things about mediaparts.jira.com

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

Visit mediaparts.jira.com

Key Findings

We analyzed Mediaparts.jira.com page load time and found that the first response time was 157 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

mediaparts.jira.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.9 s

47/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.5 s

48/100

10%

Network Requests Diagram

mediaparts.jira.com

157 ms

login.jsp

79 ms

login

626 ms

batch-main.min.css

384 ms

batch-main.min.js

465 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 78% of them (7 requests) were addressed to the original Mediaparts.jira.com, 22% (2 requests) were made to Atlassian.com. The less responsive or slowest element that took the longest time to load (626 ms) belongs to the original domain Mediaparts.jira.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.6 kB (73%)

Content Size

7.7 kB

After Optimization

2.1 kB

  • HTML

In fact, the total size of Mediaparts.jira.com main page is 7.7 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. Only 5% of websites need less resources to load. HTML takes 7.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 5.6 kB

  • Original 7.7 kB
  • After minification 5.6 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 2.2 kB, which is 28% 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 5.6 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • AJAX
  • JavaScript
  • CSS

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mediaparts Jira. According to our analytics all requests are already optimized.

Network Requests Diagram

mediaparts.jira.com

mediaparts.jira.com

157 ms

login.jsp

login.jsp

79 ms

login

login

626 ms

batch-main.min.css

batch-main.min.css

384 ms

batch-main.min.js

batch-main.min.js

465 ms

login.min.js

login.min.js

238 ms

atlassian-icons.woff

atlassian-icons.woff

156 ms

frame

frame

37 ms

frame

frame

17 ms

Accessibility Review

mediaparts.jira.com accessibility score

98

Accessibility Issues

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

mediaparts.jira.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

mediaparts.jira.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mediaparts.jira.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 Mediaparts.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

mediaparts.jira.com

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