Skip to content
Audit Complete

Results for https://www.atlassian.com

Visit site
Brazil Brazil · Sao Paulo Completed: Apr 4, 2026 17:27 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C71

Site Health

Score: 71 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

'unsafe-eval' found in script source

Security › Content Security Policy
2

'unsafe-inline' found in script source

Security › Content Security Policy
3

Cookie 'ajs_anonymous_id' is missing the Secure flag

Security › Cookie Security
4

Page weighs 41.0 MB (30.7 MB transferred)

Performance › Page Weight Budget
5

1 control(s) without accessible label

Accessibility › Form Accessibility
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.atlassian.com)](https://beavercheck.com/results/c2f2c0f7-2259-487e-bcc2-b365fe5502a1)
<a href="https://beavercheck.com/results/c2f2c0f7-2259-487e-bcc2-b365fe5502a1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.atlassian.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.atlassian.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

25
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
94
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
88
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

14.03 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

22.43 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

4.32 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.016

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

14.03 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

30.90 s

Detailed Report

Audit breakdown by category with detailed findings.

25

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:89.751 source:map[column:20 line:15 type:source-location url:_lighthouse-eval.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:137.178 source:map[column:332382 line:2 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:0.869 source:map[column:112486 line:624 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:31.065 source:map[column:233102 line:762 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:1.04 source:map[column:216343 line:48 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:2.683 source:map[column:429117 line:2 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:87.068 source:map[column:428629 line:2 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:0.447 source:map[type:text value:[unattributed]]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
div._1reo15vq > div._1tke1osq > button._1e0c1ule > img._p12f1osq div._1reo15vq > div._1tke1osq > button._1e0c1ule > img._p12f1osq
dam-cdn.atl.orangelogic.com/CDNLink/AT12EXEC.png1.0 MiB722.7 KiB
div._1e0cglyw > div._f45rh2mm > picture > img.img-screenshot div._1e0cglyw > div._f45rh2mm > picture > img.img-screenshot
/AssetLink/7g6j15a0o21u8b45773ws38rg15ioc73/jira-board-so...121.4 KiB118.4 KiB
div._kqswh2mm > div._vwz4idpf > div._kqswh2mm > video._165tbekw div._kqswh2mm > div._vwz4idpf > div._kqswh2mm > video._165tbekw
dam-cdn.atl.orangelogic.com/CDNLink/AT12MPH2.jpg29.8 KiB28.1 KiB
Teamwork Collection products visualization div._1e0c11p5 > div._1e0c1txw > figure._19pkidpf > img._1bsb1osq
dam-cdn.atl.orangelogic.com/AssetLink/5140xb7orvf7timubceisv3470t0305a.webp30.3 KiB24.0 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:119.02799999904633 label:Time to first byte subpart:timeToFirstByte] map[duration:34.32300000095368 label:Resource load delay subpart:resourceLoadDelay] map[duration:1084.117 label:Resource load duration subpart:resourceLoadDuration] map[duration:1593.165 label:Element render delay subpart:elementRenderDelay]]
lhId: page-4-VIDEO
nodeLabel: Team 26 conference video
path: 0,HTML,1,BODY,0,DIV,0,DIV,1,DIV,0,MAIN,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,VIDEO
selector: div._kqswh2mm > div._1bsb1osq > div._kqswh2mm > video._165tbekw
snippet: <video playsinline="" preload="auto" poster="https://dam-cdn.atl.orangelogic.com/AssetLink/42wp4t8o843x2uj0cc217d1ycn2r…" loop="" aria-label="Team 26 conference video" aria-hidden="false" class="_165tbekw _1vkha7f3 _tnruirba" style="max-width: 100%; --_1frmj6s: auto; --_1cta8t7: auto; --_k89wwe: auto;">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-4-VIDEO
nodeLabel: Team 26 conference video
path: 0,HTML,1,BODY,0,DIV,0,DIV,1,DIV,0,MAIN,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,VIDEO
selector: div._kqswh2mm > div._1bsb1osq > div._kqswh2mm > video._165tbekw
snippet: <video playsinline="" preload="auto" poster="https://dam-cdn.atl.orangelogic.com/AssetLink/42wp4t8o843x2uj0cc217d1ycn2r…" loop="" aria-label="Team 26 conference video" aria-hidden="false" class="_165tbekw _1vkha7f3 _tnruirba" style="max-width: 100%; --_1frmj6s: auto; --_1cta8t7: auto; --_k89wwe: auto;">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Script Evaluation10.2 s
Other3.5 s
Style & Layout1.4 s
Script Parsing & Compilation401 ms
Garbage Collection373 ms
Parse HTML & CSS366 ms
Rendering262 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Estimated savings: 0.0 ms 6.4 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 0.0 ms 47.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Team 26 Logo div._kqswh2mm > div._1e0c1txw > div._1e0c1txw > img
dam-cdn.atl.orangelogic.com/AssetLink/a8yv1fqb07trq8864u04w2i47cgwd1n0.svg
div._1reo15vq > div._1tke1osq > button._1e0c1ule > img._p12f1osq div._1reo15vq > div._1tke1osq > button._1e0c1ule > img._p12f1osq

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
User Timing marks and measures 20 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 6 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 130 ms
Server Backend Latencies 140 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 100 ms
Avoid large layout shifts 10 layout shifts found
INP breakdown
94

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Watch the full video div._19pkidpf > div.link-wrapper > a#Watchthefullvideo-:r0: > span

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Failing Elements
Skip to content div._1e0cglyw > nav._11q7cd5j > div._18zrpxbi > a._kqswstnw

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Read their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Read their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
See their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Read their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Atlassian Cookies and Tracking Notice div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
88

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div._4cvresu3 > div._kqswh2mm > figure._19pkidpf > img._1bsb1osq div._4cvresu3 > div._kqswh2mm > figure._19pkidpf > img._1bsb1osq
/AssetLink/7g6j15a0o21u8b45773ws38rg15ioc73/jira-board-so...1536 x 800 (1.92)1984 x 1042 (1.90)

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 429 ()
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Serves images with appropriate resolution
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destinationLink Text
www.atlassian.com/collections/teamworkLearn more
www.atlassian.com/legal/cookiesMore information

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

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

33
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
94
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
88
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.28 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.01 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

822 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.048

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.77 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

7.03 s

Detailed Report

Audit breakdown by category with detailed findings.

33

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:103.748 source:map[column:20 line:15 type:source-location url:_lighthouse-eval.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:167.068 source:map[type:text value:[unattributed]]] map[reflowTime:33.715 source:map[column:809075 line:680 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:0.671 source:map[column:216343 line:48 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:0.187 source:map[column:214873 line:48 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:3.386 source:map[column:429117 line:2 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:100.362 source:map[column:428629 line:2 type:source-location url:https://wac-web.prod-east.frontend.public.atl-paas.net/assets/404.e73ccca2.js urlProvider:network]] map[reflowTime:1.272 source:map[column:181 line:458 type:source-location url:https://www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js urlProvider:network]] map[reflowTime:0.81 source:map[column:303 line:104 type:source-location url:https://www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
div._1reo15vq > div._1tke1osq > button._1e0c1ule > img._p12f1osq div._1reo15vq > div._1tke1osq > button._1e0c1ule > img._p12f1osq
dam-cdn.atl.orangelogic.com/CDNLink/AT12EXEC.png1.0 MiB722.7 KiB
div._4cvresu3 > div._kqswh2mm > figure._19pkidpf > img._1bsb1osq div._4cvresu3 > div._kqswh2mm > figure._19pkidpf > img._1bsb1osq
/AssetLink/7g6j15a0o21u8b45773ws38rg15ioc73/jira-board-so...121.4 KiB111.3 KiB
div._kqswh2mm > div._vwz4idpf > div._kqswh2mm > video._165tbekw div._kqswh2mm > div._vwz4idpf > div._kqswh2mm > video._165tbekw
dam-cdn.atl.orangelogic.com/AssetLink/g24hk1v4sy0080a3ooy73w8y305nfgdl.jpg98.1 KiB84.3 KiB
Teamwork Collection products visualization div._1e0c11p5 > div._1e0c1txw > figure._19pkidpf > img._1bsb1osq
dam-cdn.atl.orangelogic.com/AssetLink/5140xb7orvf7timubceisv3470t0305a.webp30.3 KiB16.2 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:69.368 label:Time to first byte subpart:timeToFirstByte] map[duration:30.995 label:Resource load delay subpart:resourceLoadDelay] map[duration:1037.101 label:Resource load duration subpart:resourceLoadDuration] map[duration:1725.573 label:Element render delay subpart:elementRenderDelay]]
lhId: page-4-VIDEO
nodeLabel: Team 26 conference video
path: 0,HTML,1,BODY,0,DIV,0,DIV,1,DIV,0,MAIN,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,VIDEO
selector: div._kqswh2mm > div._1bsb1osq > div._kqswh2mm > video._165tbekw
snippet: <video playsinline="" preload="auto" poster="https://dam-cdn.atl.orangelogic.com/AssetLink/42wp4t8o843x2uj0cc217d1ycn2r…" loop="" aria-label="Team 26 conference video" aria-hidden="false" class="_165tbekw _1vkha7f3 _tnruirba" style="max-width: 100%; --_1frmj6s: auto; --_1cta8t7: auto; --_k89wwe: auto;">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-4-VIDEO
nodeLabel: Team 26 conference video
path: 0,HTML,1,BODY,0,DIV,0,DIV,1,DIV,0,MAIN,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,VIDEO
selector: div._kqswh2mm > div._1bsb1osq > div._kqswh2mm > video._165tbekw
snippet: <video playsinline="" preload="auto" poster="https://dam-cdn.atl.orangelogic.com/AssetLink/42wp4t8o843x2uj0cc217d1ycn2r…" loop="" aria-label="Team 26 conference video" aria-hidden="false" class="_165tbekw _1vkha7f3 _tnruirba" style="max-width: 100%; --_1frmj6s: auto; --_1cta8t7: auto; --_k89wwe: auto;">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

CategoryTime Spent
Script Evaluation3.4 s
Other997 ms
Style & Layout393 ms
Garbage Collection124 ms
Script Parsing & Compilation123 ms
Parse HTML & CSS93 ms
Rendering67 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Estimated savings: 0.0 ms 6.5 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 0.0 ms 2.0 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 0.0 ms 48.1 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
div._1reo15vq > div._1e0c1txw > div._4t3i1osq > img div._1reo15vq > div._1e0c1txw > div._4t3i1osq > img
dam-cdn.atl.orangelogic.com/AssetLink/b25ni6jq86en824330eb181373404py3.svg
div._1reo15vq > div._1e0c1txw > div._4t3i1osq > img div._1reo15vq > div._1e0c1txw > div._4t3i1osq > img
dam-cdn.atl.orangelogic.com/AssetLink/72737qhytbe162wp8518852f85krd8jn.svg
Team 26 Logo div._kqswh2mm > div._1e0c1txw > div._1e0c1txw > img
dam-cdn.atl.orangelogic.com/AssetLink/a8yv1fqb07trq8864u04w2i47cgwd1n0.svg
div._1reo15vq > div._1tke1osq > button._1e0c1ule > img._p12f1osq div._1reo15vq > div._1tke1osq > button._1e0c1ule > img._p12f1osq
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img
div._kqswh2mm > div._bna7ng7t > picture > img div._kqswh2mm > div._bna7ng7t > picture > img

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 20 user timings
Avoid long main-thread tasks 19 long tasks found
Avoid non-composited animations 3 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 130 ms
Server Backend Latencies 140 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 50 ms
Avoid large layout shifts 15 layout shifts found
INP breakdown
94

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Watch the full video div._19pkidpf > div.link-wrapper > a#Watchthefullvideo-:r0: > span

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Failing Elements
Skip to content div._1e0cglyw > nav._1e0c1txw > div._1e0c1txw > a._kqswstnw

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Read their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Read their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
See their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Read their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Atlassian Cookies and Tracking Notice div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
88

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div._1e0cglyw > div._f45rh2mm > picture > img.img-screenshot div._1e0cglyw > div._f45rh2mm > picture > img.img-screenshot
/AssetLink/7g6j15a0o21u8b45773ws38rg15ioc73/jira-board-so...1920 x 1080 (1.78)1984 x 1042 (1.90)
div._4cvresu3 > div._kqswh2mm > figure._19pkidpf > img._1bsb1osq div._4cvresu3 > div._kqswh2mm > figure._19pkidpf > img._1bsb1osq
/AssetLink/7g6j15a0o21u8b45773ws38rg15ioc73/jira-board-so...577 x 298 (1.94)1984 x 1042 (1.90)

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 429 ()
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Serves images with appropriate resolution
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destinationLink Text
www.atlassian.com/collections/teamworkLearn more
www.atlassian.com/legal/cookiesMore information

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

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback