https://develop-corporate-site.quiet-sunset-55b2.workers.dev

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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.

Why this matters

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

Why this matters

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.

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: div#root > header.relative > div.pointer-events-none > img.ddr-hero-image

path: 1,HTML,1,BODY,0,DIV,1,HEADER,1,DIV,0,IMG

selector: div#root > header.relative > div.pointer-events-none > img.ddr-hero-image

snippet: <img src="/assets/hero-CfUJRTCv.avif" alt="" class="ddr-hero-image absolute inset-0 w-full h-full object-cover object-center">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

value: No additional origins are good candidates for preconnecting

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/css2?family=Plus+Jakarta+Sans:wght@400;500;600;700;800&f...	1.5 KiB	267 ms
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/index-oGcq4DrJ.css	17.1 KiB	164 ms
/css2?family=Fraunces:opsz,wght@9..144,400;9..144,500;9.....	642 B	61 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
AI & Machine Intelligence `div.flex > div.flex-1 > div.relative > img.w-full`	develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/tech1-BDswpTUj.avif	1.4 MiB	1.4 MiB
Foundational AI Research `div.flex > article.w-full > div.relative > img.absolute`	develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/about1-BqEMGjpT.avif	213.6 KiB	190.6 KiB

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 10.2 KiB

URL	Transfer Size	Est Savings
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/index-oGcq4DrJ.css	16.6 KiB	10.2 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 55.9 KiB

URL	Transfer Size	Est Savings
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/index-BAvvfShy.js	130.8 KiB	55.9 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/tech1-BDswpTUj.avif	1.4 MiB
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/about3-DR1brHAw.avif	259.0 KiB
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/about2-B6JOYGIv.avif	222.5 KiB
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/about1-BqEMGjpT.avif	214.2 KiB
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/about4-CGir62MO.avif	176.5 KiB
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/index-BAvvfShy.js	131.4 KiB
develop-corporate-site.quiet-sunset-55b2.workers.dev/assets/hero-CfUJRTCv.avif	95.5 KiB
develop-corporate-site.quiet-sunset-55b2.workers.dev/Icon.svg	53.1 KiB
fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2	47.3 KiB
/assets/Logo O2-BsqWkVek.svg	33.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
DeepDrops Research `nav.mx-auto > div.grid > a.flex > img.h-8`	/assets/Logo O2-BsqWkVek.svg
Indian Institute of Technology Kharagpur `div.flex > div.grid > div.flex > img.h-12`
Indian Institute of Technology Patna `div.flex > div.grid > div.flex > img.h-12`
Indian Institute of Technology Kanpur `div.flex > div.grid > div.flex > img.h-12`
All India Institute of Medical Sciences, New Delhi `div.flex > div.grid > div.flex > img.h-12`
Tripura Medical College & Dr. B.R. Ambedkar Memorial Teaching Hospital `div.flex > div.grid > div.flex > img.h-12`
Agartala Government Medical College `div.flex > div.grid > div.flex > img.h-12`
Government of Tripura `div.flex > div.grid > div.flex > img.h-12`

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 40 ms

●Minify CSS

●Minify JavaScript

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.6 s

●Avoid non-composited animations 3 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 40 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 290 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Explore Health Brain → `nav.mx-auto > div.grid > div.flex > button.group`
Explore Our Research → `header.relative > div.relative > div.flex > a.group`
Partner With Us → `header.relative > div.relative > div.flex > a.group`
Who We Are `div.relative > div.flex > div.inline-flex > span.text-[13px]`
Build. `div.flex > h2.text-[clamp(28px,4.2vw,44px)] > span.relative > span.absolute`
Discover DeepDrops → `div.relative > div.grid > div > a.group`
AI Research `div.flex > article.w-full > div.flex > span.inline-flex`
DD `article.w-full > div.flex > div.flex > span.grid`
Learn more `div.w-full > a.group > div.relative > span.relative`
Learn more `div.w-full > a.group > div.relative > span.relative`
Learn more `div.w-full > a.group > div.relative > span.relative`
Learn more `div.w-full > a.group > div.relative > span.relative`
Email address `div.relative > form.flex > div.flex > input.px-4`
Subscribe `footer.relative > div.relative > form.flex > button.inline-flex`

These are opportunities to improve the legibility of your content.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 `div.relative > div.flex > div.flex > button.h-2`
Go to slide 2 `div.relative > div.flex > div.flex > button.h-2`
Go to slide 3 `div.relative > div.flex > div.flex > button.h-2`
Go to slide 4 `div.relative > div.flex > div.flex > button.h-2`
Go to slide 5 `div.relative > div.flex > div.flex > button.h-2`
Go to slide 6 `div.relative > div.flex > div.flex > button.h-2`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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>`

●`[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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●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

●Heading elements appear in a sequentially-descending order

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[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

○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

○ARIA IDs are unique

○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

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

○No element has a `[tabindex]` value greater than 0

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

100

Best Practices

●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

●No browser errors logged to the console

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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.

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`x-robots-tag: noindex`

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.

Why this matters

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`
3	`<head>`	`Syntax not understood`
4	`<meta charset="UTF-8" />`	`Syntax not understood`
5	`<link rel="icon" type="image/svg+xml" href="/Icon.svg" />`	`Syntax not understood`
6	`<meta name="viewport" content="width=device-width, initial-scale=1.0" />`	`Syntax not understood`
8	`<title>DeepDrops</title>`	`Syntax not understood`
9	`<meta`	`Syntax not understood`
10	`name="description"`	`Syntax not understood`
11	`content="DeepDrops Health Brain is an AI health intelligence platform that understands your health deeply, learns continuously, and delivers personalized, clinically-validated insights for hospitals, researchers, and individuals."`	`Syntax not understood`
12	`/>`	`Syntax not understood`
13	`<meta name="robots" content="index, follow" />`	`Syntax not understood`
14	`<link rel="canonical" href="https://deepdrops.health/" />`	`Unknown directive`
16	`<!-- Open Graph -->`	`Syntax not understood`
17	`<meta property="og:type" content="website" />`	`Unknown directive`
18	`<meta property="og:site_name" content="DeepDrops Health" />`	`Unknown directive`
19	`<meta`	`Syntax not understood`
20	`property="og:title"`	`Unknown directive`
21	`content="DeepDrops Health Brain — AI-Powered Personalized Health Intelligence"`	`Syntax not understood`
22	`/>`	`Syntax not understood`
23	`<meta`	`Syntax not understood`
24	`property="og:description"`	`Unknown directive`
25	`content="AI health intelligence that understands your health deeply, learns continuously, and delivers personalized insights for better outcomes."`	`Syntax not understood`
26	`/>`	`Syntax not understood`
27	`<meta property="og:url" content="https://deepdrops.health/" />`	`Unknown directive`
28	`<meta property="og:image" content="https://deepdrops.health/og-image.png" />`	`Unknown directive`
29	`<meta property="og:image:width" content="1200" />`	`Unknown directive`
30	`<meta property="og:image:height" content="630" />`	`Unknown directive`
32	`<!-- Twitter -->`	`Syntax not understood`
33	`<meta name="twitter:card" content="summary_large_image" />`	`Unknown directive`
34	`<meta`	`Syntax not understood`
35	`name="twitter:title"`	`Unknown directive`
36	`content="DeepDrops Health Brain — AI-Powered Personalized Health Intelligence"`	`Syntax not understood`
37	`/>`	`Syntax not understood`
38	`<meta`	`Syntax not understood`
39	`name="twitter:description"`	`Unknown directive`
40	`content="AI health intelligence that understands your health deeply, learns continuously, and delivers personalized insights for better outcomes."`	`Syntax not understood`
41	`/>`	`Syntax not understood`
42	`<meta name="twitter:image" content="https://deepdrops.health/og-image.png" />`	`Unknown directive`
44	`<meta name="theme-color" content="#0d0f0a" />`	`Syntax not understood`
46	`<link rel="preconnect" href="https://fonts.googleapis.com" />`	`Unknown directive`
47	`<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />`	`Unknown directive`
48	`<link`	`Syntax not understood`
49	`href="https://fonts.googleapis.com/css2?family=Plus+Jakarta+Sans:wght@400;500;600;700;800&family=Inter:wght@400;500;600;700&family=Caveat:wght@500;600;700&display=swap"`	`Unknown directive`
50	`rel="stylesheet"`	`Syntax not understood`
51	`/>`	`Syntax not understood`
52	`<script type="module" crossorigin src="/assets/index-BAvvfShy.js"></script>`	`Syntax not understood`
53	`<link rel="stylesheet" crossorigin href="/assets/index-oGcq4DrJ.css">`	`Syntax not understood`
54	`</head>`	`Syntax not understood`
55	`<body>`	`Syntax not understood`
56	`<div id="root"></div>`	`Syntax not understood`
57	`</body>`	`Syntax not understood`
58	`</html>`	`Syntax not understood`

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
/research/ai-machine-intelligence	Learn more

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

○Structured data is valid

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`