Skip to content
Audit Complete

Results for https://www.asana.com

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:14 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 72 / 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

Content-Security-Policy header is missing

Security › Security Headers
2

No Content-Security-Policy header found

Security › Content Security Policy
3

Page weighs 11.4 MB (5.7 MB transferred)

Performance › Page Weight Budget
4

5 image-only link(s) without alt text

Accessibility › Link & Button Quality
5

No <main> landmark found

Accessibility › Landmark Structure
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.asana.com)](https://beavercheck.com/results/4fffafb4-430d-7e0d-4248-b9ff6f0d9122)
<a href="https://beavercheck.com/results/4fffafb4-430d-7e0d-4248-b9ff6f0d9122"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.asana.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.asana.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.

32
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
83
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
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.

3.24 s

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

25.12 s

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

3.25 s

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

0.001

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

8.57 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.

25.27 s

Detailed Report

Audit breakdown by category with detailed findings.

32

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

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:387.042 source:map[column:183781 line:1 type:source-location url:https://asana.com/_next/static/chunks/framework-e5fb0dd7fe072789.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 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:62.207 source:map[type:text value:[unattributed]]] map[reflowTime:21.991 source:map[column:162791 line:0 type:source-location url:https://asana.com/_next/static/chunks/pages/_app-236bbd23a55394b9.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:5.231 source:map[column:7165 line:0 type:source-location url:https://asana.com/_next/static/chunks/88743-edc16fc1a8179f5a.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:78.103 source:map[column:164038 line:0 type:source-location url:https://asana.com/_next/static/chunks/pages/_app-236bbd23a55394b9.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:153.254 source:map[column:164540 line:0 type:source-location url:https://asana.com/_next/static/chunks/pages/_app-236bbd23a55394b9.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:122.717 source:map[column:164586 line:0 type:source-location url:https://asana.com/_next/static/chunks/pages/_app-236bbd23a55394b9.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:0.593 source:map[column:47485 line:0 type:source-location url:https://asana.com/_next/static/chunks/75311-0282f6f55d7fe731.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:0.704 source:map[column:3487 line:0 type:source-location url:https://asana.com/_next/static/chunks/10012.c5300d4af375cd99.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:4.449 source:map[column:51438 line:0 type:source-location url:https://asana.com/_next/static/chunks/19357-5b0117ee4b7da39c.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 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
Asana product UI of AI Teammate Use Cases div.w-css-reset > div > div.w-css-reset > img.w-css-reset
/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.webp?image_c...20.0 KiB17.2 KiB
Creative Production div.css-18s6ar4 > div.css-zg55ta > span > img
/transform/5da0ba11-381c-4ce8-a264-0124cedbb07b/Illustrat...14.7 KiB14.4 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:470.5680009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:2721.7279990234374 label:Resource load delay subpart:resourceLoadDelay] map[duration:162.307 label:Resource load duration subpart:resourceLoadDuration] map[duration:32.733 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: Asana product UI of AI Teammate Use Cases
path: 1,HTML,1,BODY,6,DIV,0,DIV,2,DIV,0,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,WISTIA-PLAYER,a,#document-fragment,1,DIV,0,DIV,1,DIV,1,DIV,1,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,IMG
selector: div.w-css-reset > div > div.w-css-reset > img.w-css-reset
snippet: <img class="w-css-reset" srcset="https://embed-ssl.wistia.com/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.w…" src="https://embed-ssl.wistia.com/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.w…" alt="Asana product UI of AI Teammate Use Cases" style="background-color: rgb(0, 0, 0); height: 100%; object-fit: contain;">

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

lhId: page-0-IMG
nodeLabel: Asana product UI of AI Teammate Use Cases
path: 1,HTML,1,BODY,6,DIV,0,DIV,2,DIV,0,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,WISTIA-PLAYER,a,#document-fragment,1,DIV,0,DIV,1,DIV,1,DIV,1,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,IMG
selector: div.w-css-reset > div > div.w-css-reset > img.w-css-reset
snippet: <img class="w-css-reset" srcset="https://embed-ssl.wistia.com/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.w…" src="https://embed-ssl.wistia.com/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.w…" alt="Asana product UI of AI Teammate Use Cases" style="background-color: rgb(0, 0, 0); height: 100%; object-fit: contain;">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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.

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 859 ms
URLTime Spent
www.asana.com/859 ms
asana.com/0.0 ms

Diagnostics

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: 600 ms 72.0 KiB

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
Style & Layout17.3 s
Script Evaluation12.7 s
Other9.1 s
Rendering1.6 s
Script Parsing & Compilation612 ms
Garbage Collection433 ms
Parse HTML & CSS163 ms

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

Estimated savings: 0.0 ms 12.4 KiB
URLTransfer SizeEst Savings
asana.com/assets/dist/hashed/css/reskin-6a3c245d65.css61.3 KiB12.4 KiB

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

Estimated savings: 0.0 ms 8.4 KiB
URLTransfer SizeEst Savings
asana.com/assets/dist/hashed/js/global-7258b96615.js16.7 KiB8.4 KiB

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

URL
Amplify your impact with AI image div.css-dbksp > div.css-lhkx71 > picture.css-l2evne > img
/transform/9c192ab3-d6e7-483b-abed-b2e08ba2e6c0/homepage_...
More clarity and accountability div.css-1nmi2ge > div.css-lhkx71 > picture.css-l2evne > img
/transform/d7a969e8-6f18-4c89-b0b9-ab7ec13f7f17/WEB-homep...

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

Layout shift culprits
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 9 user timings
Avoid long main-thread tasks 20 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 50 ms
Server Backend Latencies 210 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 290 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
83

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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Failing Elements
Terms div.siteFooter__secondary__col > div.terms-and-privacy > div.css-yuiwnc > div#/terms
Privacy div.siteFooter__secondary__col > div.terms-and-privacy > div.css-yuiwnc > div#/terms/privacy-statement
Download the Asana iOS app div.siteFooter__secondary__col-wrapper > div.siteFooter__secondary__col > div.css-yuiwnc > div#https://itunes.apple.com/us/app/asana-mobile/id489969512?mt=8
Download the Asana Android app div.siteFooter__secondary__col-wrapper > div.siteFooter__secondary__col > div.css-yuiwnc > div#https://play.google.com/store/apps/details?id=com.asana.app

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Failing Elements
Project intake Capture, prioritize, and assign requests automatically so your … div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Product launches Coordinate teams, tasks, and timelines to keep every launch o… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Organizational planning Address business needs quickly by analyzing progress, … div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Resource planning Visualize how teams are staffed and what resources are avail… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Goal management Connect everyone's work to the organizational goals they suppo… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Employee onboarding Standardize onboarding to help new employees make an impac… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Microsoft Teams div.css-1ik4zij > div.css-1eebgoq > div.css-1adq0r4 > div.appMarquee-row
Asana is our air traffic control. We have the visibility to scale production an… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Having one centralized ecosystem that brings all doers and stakeholders togethe… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Failing Elements
85% of Fortune 100 companies choose Asana¹ div.css-1i6a9mr > div.css-4ofcuc > div.css-1t6egar > h4.css-mai43k
Campaign management div.css-1tj5lnt-link-2 > div.css-c10hy > div > h5#info-card-title-campaign-management
Stay secure and compliant with Asana Gov div.css-zt3vru > div.css-allxq9-p1-p2-p1 > div.css-0 > h5
Simon Levinson div.css-vii74e > div.css-j0ozid > div.css-1kuaip6 > h6
Try the Asana demo div.css-8ulzpr > a.css-1pf1mn9 > div.css-n01hrm > h4.css-rqx2h3

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
1 div.slick-slider > ul.slick-dots > li.slick-active > button
2 div.slick-slider > ul.slick-dots > li > button
3 div.slick-slider > ul.slick-dots > li > button
4 div.slick-slider > ul.slick-dots > li > button

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html.device-android html.device-android

These items highlight common accessibility best practices.

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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[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 use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
No element has a `[tabindex]` value greater than 0
Deprecated ARIA roles were not used
ARIA IDs are unique
`<video>` elements contain a `<track>` element with `[kind="captions"]`
All heading elements contain content.
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
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
`<frame>` or `<iframe>` elements have a title
`<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
Form elements have associated labels
Links are distinguishable without relying on color.
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
Tables have different content in the summary attribute and `<caption>`.
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
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.
92

Best Practices

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
Cannot read properties of undefined (reading '__k')
Failed to load resource: the server responded with a status of 401 ()
Loading the script 'https://browser.sentry-cdn.com/9.6.1/bundle.min.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'unsafe-inline' https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ https://ajax.aspnetcdn.com https://bat.bing.com https://sjs.bizographics.com https://ct.capterra.com https://googleads.g.doubleclick.net https://connect.facebook.net https://tracking.g2crowd.com https://www.google-analytics.com https://apis.google.com https://www.googleadservices.com https://*.googleapis.com https://tpc.googlesyndication.com https://www.googletagmanager.com https://ssl.gstatic.com https://cdn.jotfor.ms https://form.jotform.us https://snap.licdn.com https://px.ads.linkedin.com https://www.linkedin.com https://luna1.co https://js.recurly.com https://fast.wistia.com https://fast.wistia.net https://www.youtube.com https://s.ytimg.com https://*.marketo.com https://*.marketo.net https://cdnjs.cloudflare.com https://api.ipify.org https://cdn.pdst.fm https://*.vimeocdn.com https://resources.asana.com https://w58858w0sjxx.statuspage.io https://cdn.cookielaw.org https://geolocation.onetrust.com https://*.logs.datadoghq.com https://www.datadoghq-browser-agent.com https://tagmanager.google.com/debug https://t.contentsquare.net contentsquare.com app.contentsquare.com https://cdn.jsdelivr.net/npm/@sheerid/jslib@1/ https://v2.listenloop.com https://boards.greenhouse.io/embed/job_board/js https://job-boards.greenhouse.io https://www.redditstatic.com/ads/pixel.js https://yjtag.jp/tag.js https://s.yjtag.jp/tag.js https://s.yimg.jp/ https://yjtag.yahoo.co.jp/tag https://analytics.tiktok.com/i18n/pixel/ https://s.pinimg.com/ct/ https://b92.yahoo.co.jp/rt/ https://t-antenna.asana.com/ https://scripts.postie.com/wbgboxjj/lp.1.js https://b91.yahoo.co.jp/pagead/ https://b98.yahoo.co.jp/ https://accounts.google.com/gsi/client https://js.adstk.io/convpixel.js https://a.quora.com/qevents.js https://d34r8q7sht0t9k.cloudfront.net/tag.js https://collector-39548.us.tvsquared.com/tv2track.js https://*.qualified.com https://static.xingcdn.com/xingtrk/index.js https://ct.pinterest.com/static/ct/token_create.js https://*.6sc.co https://*.6sense.com https://js.zi-scripts.com/ https://*.mountain.com/ https://c0.adalyser.com/adalyser.js https://dyv6f9ner1ir9.cloudfront.net/assets/js/nloader.js https://pagead2.googlesyndication.com https://c.amazon-adsystem.com/aat/amzn.js https://*.optimizely.com https://optimizely.s3.amazonaws.com https://tr.capterra.com https://pixel.byspotify.com/ping.min.js". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.
TypeError: Cannot read properties of undefined (reading '__k') at c.__ (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:552169) at V (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:9285) at e.value (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:640697) at e.<anonymous> (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:639475) at e.y (https://asana.com/_next/static/chunks/28fafed5.1d9eba965cb4ac03.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637:1:169128) at e.v (https://asana.com/_next/static/chunks/28fafed5.1d9eba965cb4ac03.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637:1:168944) at e.trigger (https://asana.com/_next/static/chunks/28fafed5.1d9eba965cb4ac03.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637:1:173211) at n.trigger (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:398357) at n (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:469626) at https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:470910
Uncaught (in promise) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy
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
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
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.

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

45
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
80
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
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.

981 ms

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

5.26 s

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

561 ms

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

0.006

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

3.21 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.

5.29 s

Detailed Report

Audit breakdown by category with detailed findings.

45

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

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:483.903 source:map[column:183781 line:1 type:source-location url:https://asana.com/_next/static/chunks/framework-e5fb0dd7fe072789.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 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:178.982 source:map[type:text value:[unattributed]]] map[reflowTime:6.622 source:map[column:7165 line:0 type:source-location url:https://asana.com/_next/static/chunks/88743-edc16fc1a8179f5a.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:113.677 source:map[column:164038 line:0 type:source-location url:https://asana.com/_next/static/chunks/pages/_app-236bbd23a55394b9.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:197.169 source:map[column:164540 line:0 type:source-location url:https://asana.com/_next/static/chunks/pages/_app-236bbd23a55394b9.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:129.526 source:map[column:164586 line:0 type:source-location url:https://asana.com/_next/static/chunks/pages/_app-236bbd23a55394b9.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:0.891 source:map[column:47485 line:0 type:source-location url:https://asana.com/_next/static/chunks/75311-0282f6f55d7fe731.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:20.251 source:map[column:162791 line:0 type:source-location url:https://asana.com/_next/static/chunks/pages/_app-236bbd23a55394b9.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:0.87 source:map[column:3487 line:0 type:source-location url:https://asana.com/_next/static/chunks/10012.c5300d4af375cd99.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 urlProvider:network]] map[reflowTime:14.897 source:map[column:51438 line:0 type:source-location url:https://asana.com/_next/static/chunks/19357-5b0117ee4b7da39c.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637 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
Amplify your impact with AI image div.css-dbksp > div.css-lhkx71 > picture.css-l2evne > img
/transform/9c192ab3-d6e7-483b-abed-b2e08ba2e6c0/homepage_...42.9 KiB33.9 KiB
Asana product UI of AI Teammate Use Cases div.w-css-reset > div > div.w-css-reset > img.w-css-reset
/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.webp?image_c...50.4 KiB31.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:500.8170009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:3050.9769990234377 label:Resource load delay subpart:resourceLoadDelay] map[duration:139.778 label:Resource load duration subpart:resourceLoadDuration] map[duration:41.66 label:Element render delay subpart:elementRenderDelay]]
lhId: page-1-IMG
nodeLabel: Asana product UI of AI Teammate Use Cases
path: 1,HTML,1,BODY,6,DIV,0,DIV,2,DIV,0,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,WISTIA-PLAYER,a,#document-fragment,1,DIV,0,DIV,1,DIV,1,DIV,1,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,IMG
selector: div.w-css-reset > div > div.w-css-reset > img.w-css-reset
snippet: <img class="w-css-reset" srcset="https://embed-ssl.wistia.com/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.w…" src="https://embed-ssl.wistia.com/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.w…" alt="Asana product UI of AI Teammate Use Cases" style="background-color: rgb(0, 0, 0); height: 100%; object-fit: contain;">

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

lhId: page-1-IMG
nodeLabel: Asana product UI of AI Teammate Use Cases
path: 1,HTML,1,BODY,6,DIV,0,DIV,2,DIV,0,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,WISTIA-PLAYER,a,#document-fragment,1,DIV,0,DIV,1,DIV,1,DIV,1,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,IMG
selector: div.w-css-reset > div > div.w-css-reset > img.w-css-reset
snippet: <img class="w-css-reset" srcset="https://embed-ssl.wistia.com/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.w…" src="https://embed-ssl.wistia.com/deliveries/5db8175a0d68c14dcbed7b9fcc50dbac.w…" alt="Asana product UI of AI Teammate Use Cases" style="background-color: rgb(0, 0, 0); height: 100%; object-fit: contain;">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 311 ms
URLTime Spent
www.asana.com/311 ms
asana.com/0.0 ms

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.

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

Diagnostics

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.1 s
Other1.4 s
Style & Layout806 ms
Script Parsing & Compilation182 ms
Garbage Collection86 ms
Parse HTML & CSS72 ms
Rendering70 ms

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

Estimated savings: 0.0 ms 12.4 KiB
URLTransfer SizeEst Savings
asana.com/assets/dist/hashed/css/reskin-6a3c245d65.css61.3 KiB12.4 KiB

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

Estimated savings: 0.0 ms 8.4 KiB
URLTransfer SizeEst Savings
asana.com/assets/dist/hashed/js/global-7258b96615.js16.7 KiB8.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 71.9 KiB

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

Layout shift culprits
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 9 user timings
Avoid long main-thread tasks 5 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 40 ms
Server Backend Latencies 270 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 300 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
80

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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Failing Elements
Choose your preferred language div._nav_language-selector__4JrcF > div.css-yuiwnc > button._nav_language-selector__select__oOIIR > div#language-selector
Terms div.siteFooter__secondary__col > div.terms-and-privacy > div.css-yuiwnc > div#/terms
Privacy div.siteFooter__secondary__col > div.terms-and-privacy > div.css-yuiwnc > div#/terms/privacy-statement
Download the Asana iOS app div.siteFooter__secondary__col-wrapper > div.siteFooter__secondary__col > div.css-yuiwnc > div#https://itunes.apple.com/us/app/asana-mobile/id489969512?mt=8
Download the Asana Android app div.siteFooter__secondary__col-wrapper > div.siteFooter__secondary__col > div.css-yuiwnc > div#https://play.google.com/store/apps/details?id=com.asana.app

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Failing Elements
Resource planning Visualize how teams are staffed and what resources are avail… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Goal management Connect everyone's work to the organizational goals they suppo… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Employee onboarding Standardize onboarding to help new employees make an impac… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Microsoft Teams div.css-1ik4zij > div.css-1eebgoq > div.css-1adq0r4 > div.appMarquee-row

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Failing Elements
85% of Fortune 100 companies choose Asana¹ div.css-1i6a9mr > div.css-4ofcuc > div.css-1t6egar > h4.css-mai43k
Campaign management div.css-1tj5lnt-link-2 > div.css-c10hy > div > h5#info-card-title-campaign-management
Stay secure and compliant with Asana Gov div.css-zt3vru > div.css-allxq9-p1-p2-p1 > div.css-0 > h5
Simon Levinson div.css-vii74e > div.css-j0ozid > div.css-1kuaip6 > h6
Try the Asana demo div.css-8ulzpr > a.css-1pf1mn9 > div.css-n01hrm > h4.css-rqx2h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
div.css-15st4et > div.css-l00654 > div.css-1tjylrs > a div.css-15st4et > div.css-l00654 > div.css-1tjylrs > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Failing Elements
Contact sales View demo Download app header._nav_header__7tbaV > div._nav_desktop-drawer__qquVR > div._nav_dropdown-footer__4avDy > ul._nav_dropdown-footer__buttons__F4Vxf
Marketing Operations IT Leadership div.css-1eebgoq > div.css-fiaey7 > div.css-16e6i3h > ul.css-5x05ay

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html html

These items highlight common accessibility best practices.

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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Deprecated ARIA roles were not used
ARIA IDs are unique
`<video>` elements contain a `<track>` element with `[kind="captions"]`
All heading elements contain content.
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
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
`<frame>` or `<iframe>` elements have a title
`<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
Form elements have associated labels
Links are distinguishable without relying on color.
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
Tables have different content in the summary attribute and `<caption>`.
Image elements do not have `[alt]` attributes that are redundant text.
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.
92

Best Practices

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
Cannot read properties of undefined (reading '__k')
Failed to load resource: the server responded with a status of 401 ()
Loading the script 'https://browser.sentry-cdn.com/9.6.1/bundle.min.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'unsafe-inline' https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ https://ajax.aspnetcdn.com https://bat.bing.com https://sjs.bizographics.com https://ct.capterra.com https://googleads.g.doubleclick.net https://connect.facebook.net https://tracking.g2crowd.com https://www.google-analytics.com https://apis.google.com https://www.googleadservices.com https://*.googleapis.com https://tpc.googlesyndication.com https://www.googletagmanager.com https://ssl.gstatic.com https://cdn.jotfor.ms https://form.jotform.us https://snap.licdn.com https://px.ads.linkedin.com https://www.linkedin.com https://luna1.co https://js.recurly.com https://fast.wistia.com https://fast.wistia.net https://www.youtube.com https://s.ytimg.com https://*.marketo.com https://*.marketo.net https://cdnjs.cloudflare.com https://api.ipify.org https://cdn.pdst.fm https://*.vimeocdn.com https://resources.asana.com https://w58858w0sjxx.statuspage.io https://cdn.cookielaw.org https://geolocation.onetrust.com https://*.logs.datadoghq.com https://www.datadoghq-browser-agent.com https://tagmanager.google.com/debug https://t.contentsquare.net contentsquare.com app.contentsquare.com https://cdn.jsdelivr.net/npm/@sheerid/jslib@1/ https://v2.listenloop.com https://boards.greenhouse.io/embed/job_board/js https://job-boards.greenhouse.io https://www.redditstatic.com/ads/pixel.js https://yjtag.jp/tag.js https://s.yjtag.jp/tag.js https://s.yimg.jp/ https://yjtag.yahoo.co.jp/tag https://analytics.tiktok.com/i18n/pixel/ https://s.pinimg.com/ct/ https://b92.yahoo.co.jp/rt/ https://t-antenna.asana.com/ https://scripts.postie.com/wbgboxjj/lp.1.js https://b91.yahoo.co.jp/pagead/ https://b98.yahoo.co.jp/ https://accounts.google.com/gsi/client https://js.adstk.io/convpixel.js https://a.quora.com/qevents.js https://d34r8q7sht0t9k.cloudfront.net/tag.js https://collector-39548.us.tvsquared.com/tv2track.js https://*.qualified.com https://static.xingcdn.com/xingtrk/index.js https://ct.pinterest.com/static/ct/token_create.js https://*.6sc.co https://*.6sense.com https://js.zi-scripts.com/ https://*.mountain.com/ https://c0.adalyser.com/adalyser.js https://dyv6f9ner1ir9.cloudfront.net/assets/js/nloader.js https://pagead2.googlesyndication.com https://c.amazon-adsystem.com/aat/amzn.js https://*.optimizely.com https://optimizely.s3.amazonaws.com https://tr.capterra.com https://pixel.byspotify.com/ping.min.js". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.
TypeError: Cannot read properties of undefined (reading '__k') at c.__ (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:552169) at V (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:9285) at e.value (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:640697) at e.<anonymous> (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:639475) at e.y (https://asana.com/_next/static/chunks/28fafed5.1d9eba965cb4ac03.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637:1:169128) at e.v (https://asana.com/_next/static/chunks/28fafed5.1d9eba965cb4ac03.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637:1:168944) at e.trigger (https://asana.com/_next/static/chunks/28fafed5.1d9eba965cb4ac03.js?dpl=8354dcc07986847a71dc14f1ee1c2c2a2bda738c46de2d29401737ba56b44b73363964353262633735333530303230303038626238636637:1:173211) at n.trigger (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:398357) at n (https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:469626) at https://fast.wistia.com/assets/external/publicApi.js@0.1.7:1:470910
Uncaught (in promise) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy
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
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
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.

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