Lighthouse Desktop
· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.Detailed Report
Audit breakdown by category with detailed findings.
Performance
Insights
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| portal.kumorai.io/styles.185da9dbc3624d954685.css | 168.7 KiB | 615 ms |
| portal.kumorai.io/assets/sql-formatter/sql-formatter.min.js | 14.7 KiB | |
| fonts.googleapis.com/icon?family=Material+Icons | 817 B | 262 ms |
| fonts.googleapis.com/css2?family=Poppins:wght@300;400;600&display=swap | 635 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| portal.kumorai.io/styles.185da9dbc3624d954685.css | 168.6 KiB | 163.4 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| portal.kumorai.io/main.b2e477fcccefdded4d1f.js | 1.1 MiB | 742.0 KiB |
| portal.kumorai.io/61.9350838b2192087324ce.js | 518.3 KiB | 517.6 KiB |
| portal.kumorai.io/scripts.1997f9227ae5e5638520.js | 601.4 KiB | 369.3 KiB |
| portal.kumorai.io/78.f2a42a3cec7ea243eda3.js | 302.9 KiB | 161.0 KiB |
| portal.kumorai.io/7.43f8a0cde085b9746148.js | 154.0 KiB | 127.5 KiB |
| portal.kumorai.io/3.50ba4308c9bfed7c86de.js | 119.4 KiB | 84.7 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
Kumorai div.kc-login > div.kc-brand > div.kc-brand-content > img.kc-brand-logo | portal.kumorai.io/assets/kumorailogo/Kumorai-Logo-Icon.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
or sign in with email div.ng-tns-c403-1 > div.mb-2 > div.kc-divider > span.ng-tns-c403-1 |
These are opportunities to improve the legibility of your content.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Best Practices
General
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
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
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Crawling and Indexing
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Performance issues directly impact user engagement and conversion rates.
| Line # | Content | Error |
|---|---|---|
| 1 | <!doctype html> | Syntax not understood |
| 2 | <html lang="en"> | Syntax not understood |
| 4 | <head> | Syntax not understood |
| 5 | <meta charset="utf-8"> | Syntax not understood |
| 6 | <title> | Syntax not understood |
| 7 | Kumorai - Multi-Cloud Automation, Orchestration, Compliance & Governance | Syntax not understood |
| 8 | </title> | Syntax not understood |
| 9 | <base href="/"> | Syntax not understood |
| 11 | <meta content="width=device-width, initial-scale=1" name="viewport"> | Syntax not understood |
| 12 | <link href="favicon.ico" rel="icon" type="image/x-icon"> | Syntax not understood |
| 13 | <link rel="apple-touch-icon" sizes="180x180" href="apple-touch-icon.png"> | Syntax not understood |
| 14 | <link rel="icon" type="image/png" sizes="32x32" href="favicon-32x32.png"> | Syntax not understood |
| 15 | <link rel="icon" type="image/png" sizes="16x16" href="favicon-16x16.png"> | Syntax not understood |
| 16 | <!-- <link rel="manifest" href="site.webmanifest"> --> | Syntax not understood |
| 17 | <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet"> | Unknown directive |
| 18 | <style> | Syntax not understood |
| 19 | @import url('https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;600&display=swap'); | Unknown directive |
| 20 | </style> | Syntax not understood |
| 21 | <script src="assets/sql-formatter/sql-formatter.min.js"></script> | Syntax not understood |
| 22 | <link rel="stylesheet" href="styles.185da9dbc3624d954685.css"></head> | Syntax not understood |
| 24 | <body dir="ltr"> | Syntax not understood |
| 25 | <style> | Syntax not understood |
| 27 | display: block; | Unknown directive |
| 28 | position: absolute; | Unknown directive |
| 29 | top: 0; | Unknown directive |
| 30 | left: 0; | Unknown directive |
| 31 | width: 100%; | Unknown directive |
| 32 | height: 100%; | Unknown directive |
| 33 | background: #13293d; | Unknown directive |
| 34 | z-index: 99999; | Unknown directive |
| 35 | pointer-events: none; | Unknown directive |
| 36 | } | Syntax not understood |
| 39 | position: fixed; | Unknown directive |
| 40 | top: 50%; | Unknown directive |
| 41 | left: 50%; | Unknown directive |
| 42 | transform: translate(-50%, -50%); | Unknown directive |
| 43 | -webkit-transform: translate(-50%, -50%); | Unknown directive |
| 44 | } | Syntax not understood |
| 46 | @-webkit-keyframes ball-scale-multiple { | Syntax not understood |
| 47 | 0% { | Syntax not understood |
| 48 | -webkit-transform: scale(0); | Unknown directive |
| 49 | transform: scale(0); | Unknown directive |
| 50 | opacity: 0; | Unknown directive |
| 51 | } | Syntax not understood |
| 53 | 5% { | Syntax not understood |
| 54 | opacity: 1; | Unknown directive |
| 55 | } | Syntax not understood |
| 57 | 100% { | Syntax not understood |
| 58 | -webkit-transform: scale(1); | Unknown directive |
| 59 | transform: scale(1); | Unknown directive |
| 60 | opacity: 0; | Unknown directive |
| 61 | } | Syntax not understood |
| 62 | } | Syntax not understood |
| 64 | @keyframes ball-scale-multiple { | Syntax not understood |
| 65 | 0% { | Syntax not understood |
| 66 | -webkit-transform: scale(0); | Unknown directive |
| 67 | transform: scale(0); | Unknown directive |
| 68 | opacity: 0; | Unknown directive |
| 69 | } | Syntax not understood |
| 71 | 5% { | Syntax not understood |
| 72 | opacity: 1; | Unknown directive |
| 73 | } | Syntax not understood |
| 75 | 100% { | Syntax not understood |
| 76 | -webkit-transform: scale(1); | Unknown directive |
| 77 | transform: scale(1); | Unknown directive |
| 78 | opacity: 0; | Unknown directive |
| 79 | } | Syntax not understood |
| 80 | } | Syntax not understood |
| 82 | .ball-scale-multiple { | Syntax not understood |
| 83 | position: relative; | Unknown directive |
| 84 | -webkit-transform: translateY(-30px); | Unknown directive |
| 85 | transform: translateY(-30px); | Unknown directive |
| 86 | } | Syntax not understood |
| 88 | .ball-scale-multiple>div:nth-child(2) { | Unknown directive |
| 89 | -webkit-animation-delay: -0.4s; | Unknown directive |
| 90 | animation-delay: -0.4s; | Unknown directive |
| 91 | } | Syntax not understood |
| 93 | .ball-scale-multiple>div:nth-child(3) { | Unknown directive |
| 94 | -webkit-animation-delay: -0.2s; | Unknown directive |
| 95 | animation-delay: -0.2s; | Unknown directive |
| 96 | } | Syntax not understood |
| 98 | .ball-scale-multiple>div { | Syntax not understood |
| 99 | background-color: #fff; | Unknown directive |
| 100 | border-radius: 100%; | Unknown directive |
| 101 | -webkit-animation-fill-mode: both; | Unknown directive |
| 102 | animation-fill-mode: both; | Unknown directive |
| 103 | position: absolute; | Unknown directive |
| 104 | left: -30px; | Unknown directive |
| 105 | top: 0; | Unknown directive |
| 106 | opacity: 0; | Unknown directive |
| 107 | margin: 0; | Unknown directive |
| 108 | width: 60px; | Unknown directive |
| 109 | height: 60px; | Unknown directive |
| 110 | -webkit-animation: ball-scale-multiple 1s 0s linear infinite; | Unknown directive |
| 111 | animation: ball-scale-multiple 1s 0s linear infinite; | Unknown directive |
| 112 | } | Syntax not understood |
| 113 | </style> | Syntax not understood |
| 115 | <div id="vex-splash-screen"> | Syntax not understood |
| 116 | <div class="wrapper"> | Syntax not understood |
| 117 | <div class="ball-scale-multiple"> | Syntax not understood |
| 118 | <div></div> | Syntax not understood |
| 119 | <div></div> | Syntax not understood |
| 120 | <div></div> | Syntax not understood |
| 121 | </div> | Syntax not understood |
| 122 | </div> | Syntax not understood |
| 123 | </div> | Syntax not understood |
| 125 | <vex-root></vex-root> | Syntax not understood |
| 126 | <app-redirect></app-redirect> | Syntax not understood |
| 127 | <script src="runtime.3bed62c1df71dc36c41a.js" defer></script><script src="polyfills.be9a603a93183832c964.js" defer></script><script src="scripts.1997f9227ae5e5638520.js" defer></script><script src="main.b2e477fcccefdded4d1f.js" defer></script></body> | Syntax not understood |
| 129 | </html> | Syntax not understood |
To appear in search results, crawlers need access to your app.