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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.106877] map[node:map[boundingRect:map[bottom:883 height:735 left:439 right:911 top:148 width:472] lhId:page-1-DIV nodeLabel:Sign in Help Username Remember my username Continue Forgot username or Sign … path:1,HTML,1,BODY,0,DIV,3,DIV,0,DIV,0,DIV,1,DIV selector:div#utd-main > div#loginView > div.login-container > div.floating-labels-form snippet:<div data-v-8597d9e7="" class="floating-labels-form"> type:node] score:0.106877 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.uptodate.com/app/assets/NotoSans-Regular-CUnezwo1.woff2]] map[cause:Web font extra:map[type:url value:https://www.uptodate.com/app/assets/wk-icons-8dBf3Vus.woff2]]] type:subitems]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.uptodate.com/app/assets/NotoSans-SemiBold-eeohmkRK.woff2	185 ms
www.uptodate.com/app/assets/NotoSans-Bold-CjI8rmzb.woff2	95 ms
www.uptodate.com/app/assets/NotoSans-Light-DzqmUfbq.woff2	95 ms
www.uptodate.com/app/assets/NotoSans-Regular-CUnezwo1.woff2	65 ms
www.uptodate.com/app/assets/FiraSans-Regular-BTnMGPMZ.woff	65 ms
www.uptodate.com/app/assets/FiraSans-Light-CcuDwDV2.woff	65 ms
www.uptodate.com/app/assets/wk-icons-8dBf3Vus.woff2	40 ms
www.uptodate.com/app/assets/wk-icons-open-I9AnqcVf.woff	40 ms

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

value: no origins were preconnected

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.uptodate.com/app/assets/utd-all-C4EXBBMH.css	218.8 KiB	559 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
cdn.wolterskluwer.io/wk-logos/1.0.x/wk-brand-white.svg	0.0 ms	2.5 KiB

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
www.uptodate.com/login	http/1.1
www.uptodate.com/app/dist/DOM-Cws02s0j.min.js	http/1.1
www.uptodate.com/app/dist/epic-ClRhenuO.min.js	http/1.1
www.uptodate.com/app/assets/utd-all-C4EXBBMH.css	http/1.1
www.uptodate.com/app/dist/index-CEWs5uCT.min.js	http/1.1
www.uptodate.com/app/dist/vendor-DMdb3ILA.min.js	http/1.1
www.uptodate.com/app/dist/utd-all-BtFJPR2f.min.js	http/1.1
www.uptodate.com/app/utd-menu/utd-icon.png	http/1.1
www.uptodate.com/app/dist/pace-B_2Z1FtK.min.js	http/1.1
www.uptodate.com/app/utd-menu/utd-icon-redesign.png	http/1.1
www.uptodate.com/services/app/init/json?id=YXBwQ29udGFpbmVy	http/1.1
www.uptodate.com/app/assets/NotoSans-Regular-CUnezwo1.woff2	http/1.1
www.uptodate.com/app/utd-menu/wk-wheel-icon.svg	http/1.1
www.uptodate.com/app/utd-menu/utd-logo.svg	http/1.1
www.uptodate.com/app/assets/WK-Logo-7lXiX5v8.svg	http/1.1
www.uptodate.com/app/assets/NotoSans-Bold-CjI8rmzb.woff2	http/1.1
www.uptodate.com/app/assets/wk-icons-8dBf3Vus.woff2	http/1.1
www.uptodate.com/app/assets/NotoSans-SemiBold-eeohmkRK.woff2	http/1.1
www.uptodate.com/services/app/localization/file?lang=fr	http/1.1
/services/app/event/login/json?source=login-subscribe-vie...	http/1.1
www.uptodate.com/services/app/config/footer/json	http/1.1
www.uptodate.com/contents/assets/css/UTD_gx_gen.css	http/1.1
www.uptodate.com/app/assets/microsoft-logo-blue-BeURMre4.svg	http/1.1
www.uptodate.com/app/assets/open-athens-logo-purple-Dep7k9zT.svg	http/1.1
www.uptodate.com/app/assets/NotoSans-Light-DzqmUfbq.woff2	http/1.1
www.uptodate.com/app/assets/wk-icons-open-I9AnqcVf.woff	http/1.1
www.uptodate.com/app/assets/FiraSans-Regular-BTnMGPMZ.woff	http/1.1
www.uptodate.com/app/assets/FiraSans-Light-CcuDwDV2.woff	http/1.1

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.1 s

URL	Time Spent
uptodate.com/	729 ms
www.uptodate.com/	295 ms
www.uptodate.com/index	75 ms
www.uptodate.com/login	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Sign in Help Username Remember my username Continue Forgot username or Sign … `div#utd-main > div#loginView > div.login-container > div.floating-labels-form`	0.107

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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: 140 ms 210.9 KiB

URL	Transfer Size	Est Savings
www.uptodate.com/app/assets/utd-all-C4EXBBMH.css	216.8 KiB	210.9 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: 1.3 s 1.5 MiB

URL	Transfer Size	Est Savings
www.uptodate.com/app/dist/utd-all-BtFJPR2f.min.js	1.3 MiB	967.2 KiB
www.uptodate.com/app/dist/vendor-DMdb3ILA.min.js	677.2 KiB	381.9 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	176.7 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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
www.uptodate.com/app/dist/utd-all-BtFJPR2f.min.js	1.3 MiB
www.uptodate.com/app/dist/vendor-DMdb3ILA.min.js	679.3 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.uptodate.com/app/assets/utd-all-C4EXBBMH.css	218.8 KiB
www.uptodate.com/app/assets/FiraSans-Regular-BTnMGPMZ.woff	180.9 KiB
www.uptodate.com/app/assets/FiraSans-Light-CcuDwDV2.woff	180.6 KiB
www.uptodate.com/app/assets/NotoSans-SemiBold-eeohmkRK.woff2	167.9 KiB
www.uptodate.com/app/assets/NotoSans-Regular-CUnezwo1.woff2	165.3 KiB
www.uptodate.com/app/assets/NotoSans-Light-DzqmUfbq.woff2	164.8 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
footer.wk-footer > div.wk-footer-container > a.wk-logo > img `footer.wk-footer > div.wk-footer-container > a.wk-logo > img`	cdn.wolterskluwer.io/wk-logos/1.0.x/wk-brand-white.svg
UpToDate `div.wk-header-container > div > a.wk-logo > img.utd-logo`	www.uptodate.com/app/utd-menu/utd-logo.svg

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

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Optimize viewport for mobile

●Max Potential First Input Delay 40 ms

●Minify CSS

●Minify JavaScript

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.6 s

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 40 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Français `header.wk-header > div.wk-header-container > ul.wk-nav > li`

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Français `ul.wk-nav > li > div.wk-dropdown > a#prospect-language-selector`

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.

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
Company `div.wk-footer-nav > div.wk-footer-nav-list > section > h3.wk-footer-heading`
About Us `section > ul > li > a`
Editorial Policy `section > ul > li > a`
Testimonials `section > ul > li > a`
Wolters Kluwer `section > ul > li > a.wk-icon`
Careers `section > ul > li > a.wk-icon`
Support `div.wk-footer-nav > div.wk-footer-nav-list > section > h3.wk-footer-heading`
Contact Us `section > ul > li > a`
Help & Training `section > ul > li > a`
Citing Our Content `section > ul > li > a`
News & Events `div.wk-footer-container > div.wk-footer-nav > div.wk-footer-nav-list > h3.wk-footer-heading`
Nouveautés `div.wk-footer-nav-list > ul > li > a`
Webinars `div.wk-footer-nav-list > ul > li > a`
Resources `div.wk-footer-container > div.wk-footer-nav > div.wk-footer-nav-list > h3.wk-footer-heading`
UpToDate Sign-in `div.wk-footer-nav-list > ul > li > a`
Mobile Apps `div.wk-footer-nav-list > ul > li > a`
Follow Us `div.wk-footer-container > div.wk-footer-nav > div.wk-footer-nav-list > h3.wk-footer-heading`
Sign Up `div.wk-navbar > ul.wk-nav > li.wk-green > a`
Privacy Policy `div.wk-footer-copyright-container > ul.wk-footer-meta-info > li > a`
Trademarks `div.wk-footer-copyright-container > ul.wk-footer-meta-info > li > a`
Conditions d'utilisation `div.wk-footer-copyright-container > ul.wk-footer-meta-info > li > a`
Manage Cookie Preferences `div.wk-footer-copyright-container > ul.wk-footer-meta-info > li > a#ot-sdk-btn`
© 2026 UpToDate, Inc. and/or its affiliates. All Rights Reserved. `div.wk-footer-copyright > div.wk-footer-copyright-container > ul.wk-footer-meta-info > div.copyright`
, Inc. and/or its affiliates. All Rights Reserved. `div.wk-footer-copyright-container > ul.wk-footer-meta-info > div.copyright > span.copyrightFull`
Licensed to `div.wk-footer-copyright-container > ul.wk-footer-meta-info > li.nowrap > span`
: UpToDate Marketing Professional `div.wk-footer-copyright-container > ul.wk-footer-meta-info > li.nowrap > span`
Étiquette de support `div.wk-footer-copyright-container > ul.wk-footer-meta-info > li > span`
: [1005 - 141.227.188.123 - 37F3E9DF56 - PR14 - UPT - NP - 20260422-00:22:57UTC… `div.wk-footer-copyright-container > ul.wk-footer-meta-info > li > span`
- XL `ul.wk-footer-meta-info > li > span > span.SupportTagXLarge`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
footer.wk-footer > div.wk-footer-container > a.wk-logo > img `footer.wk-footer > div.wk-footer-container > a.wk-logo > img`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wk-footer-nav-list > ul.wk-social-icons-container > li > a.wk-icon `div.wk-footer-nav-list > ul.wk-social-icons-container > li > a.wk-icon`
div.wk-footer-nav-list > ul.wk-social-icons-container > li > a.wk-icon `div.wk-footer-nav-list > ul.wk-social-icons-container > li > a.wk-icon`
div.wk-footer-nav-list > ul.wk-social-icons-container > li > a.wk-icon `div.wk-footer-nav-list > ul.wk-social-icons-container > li > a.wk-icon`
div.wk-footer-nav-list > ul.wk-social-icons-container > li > a.wk-icon `div.wk-footer-nav-list > ul.wk-social-icons-container > li > a.wk-icon`
footer#utdFooter > footer.wk-footer > div.wk-footer-container > a.wk-logo `footer#utdFooter > footer.wk-footer > div.wk-footer-container > a.wk-logo`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sign up today to receive the latest news and updates from UpToDate. Sign Up `div.wk-footer-nav > div.wk-footer-nav-list > div.wk-navbar > ul.wk-nav`
Privacy Policy Trademarks Conditions d'utilisation Manage Cookie Preferences © … `footer.wk-footer > div.wk-footer-copyright > div.wk-footer-copyright-container > ul.wk-footer-meta-info`

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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.wkProspect `html.wkProspect`

These items highlight common accessibility best practices.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close `div.visuallyHidden > div.username-tooltip-box > div.tooltip-action > button.utd-button`

These are opportunities to improve keyboard navigation in your application.

○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

●Form elements have associated labels

●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

●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

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

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

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

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
footer.wk-footer > div.wk-footer-container > a.wk-logo > img `footer.wk-footer > div.wk-footer-container > a.wk-logo > img`

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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`