Skip to content
https://clarivate.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

77

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.

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.

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.

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.

URLResource SizeEst Savings
Premium Data Sets div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Premium-Data-Sets.png47.9 KiB32.3 KiB
Workflow Solutions​ div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Workflow-Solutions%E2%80%8B.png34.9 KiB23.5 KiB
Intellectual Property div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Intellectual-Property.png24.1 KiB20.0 KiB
Insights & Analytics​ div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Insights-Analytics%E2%80%8B.png20.2 KiB16.5 KiB
Expert Services​ div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Expert-Services%E2%80%8B.png23.7 KiB16.0 KiB
Academia & Government div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Academia-and-Government.png16.2 KiB13.5 KiB
Life Sciences & Healthcare div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Life-Sciences-Healthcare.png9.6 KiB8.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:3067.152 label:Time to first byte subpart:timeToFirstByte] map[duration:416.516 label:Resource load delay subpart:resourceLoadDelay] map[duration:6.282 label:Resource load duration subpart:resourceLoadDuration] map[duration:232.446 label:Element render delay subpart:elementRenderDelay]]
lhId: page-7-DIV
nodeLabel: body.home > div#main-content-wrapper > section.hero > div.static-bg
path: 1,HTML,1,BODY,2,DIV,0,SECTION,1,DIV
selector: body.home > div#main-content-wrapper > section.hero > div.static-bg
snippet: <div class="static-bg" style="background-image: url(&quot;https://clarivate.com/wp-content/uploads/2024/03/hom…&quot;);">

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-7-DIV
nodeLabel: body.home > div#main-content-wrapper > section.hero > div.static-bg
path: 1,HTML,1,BODY,2,DIV,0,SECTION,1,DIV
selector: body.home > div#main-content-wrapper > section.hero > div.static-bg
snippet: <div class="static-bg" style="background-image: url(&quot;https://clarivate.com/wp-content/uploads/2024/03/hom…&quot;);">

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.

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
value: No additional origins are good candidates for preconnecting

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.9 s
URLTime Spent
clarivate.com/3.0 s

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: 80 ms 35.8 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.7 s
Other505 ms
Style & Layout377 ms
Script Parsing & Compilation234 ms
Rendering118 ms
Parse HTML & CSS72 ms
Garbage Collection49 ms

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 reasonFailure type
The page has an unload handler in the main frame.Actionable

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
Insights & Analytics​ div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Insights-Analytics%E2%80%8B.png
Premium Data Sets div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Premium-Data-Sets.png
Workflow Solutions​ div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Workflow-Solutions%E2%80%8B.png
Expert Services​ div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2024/03/Expert-Services%E2%80%8B.png
Rare Disease Innovation - Navigating Capital, Complexity, and Clinical Opportun… div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
/wp-content/uploads/2024/09/CL_photo_abstract_136-e168130...
The Top 100 Global Innovators div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2026/01/Top-100-2026-hero_1920x1080-380x530.jpg
Drugs to Watch div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2026/01/DTW-hero_1920x1080px-380x530.png
Highly Cited Researchers div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
/wp-content/uploads/2025/10/HCR-2025_Hero-section_1920x10...
Rare Disease Innovation - Navigating Capital, Complexity, and Clinical Opportun… div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
/wp-content/uploads/2024/09/CL_photo_abstract_136-e168130...
The Top 100 Global Innovators div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2026/01/Top-100-2026-hero_1920x1080-380x530.jpg
Drugs to Watch div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
clarivate.com/wp-content/uploads/2026/01/DTW-hero_1920x1080px-380x530.png
Highly Cited Researchers div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
/wp-content/uploads/2025/10/HCR-2025_Hero-section_1920x10...
Rare Disease Innovation - Navigating Capital, Complexity, and Clinical Opportun… div.h-100 > div.d-flex > div.card-image-wrapper > img.object-fit-cover
/wp-content/uploads/2024/09/CL_photo_abstract_136-e168130...
Clarivate on X ul.list-unstyled > li.list-inline-item > a > img
clarivate.com/wp-content/themes/clarivate/src/img/x-logo.svg
Clarivate training on YouTube ul.list-unstyled > li.list-inline-item > a > img
clarivate.com/wp-content/themes/clarivate/src/img/linkedin-logo.svg
Clarivate on Facebook ul.list-unstyled > li.list-inline-item > a > img
clarivate.com/wp-content/themes/clarivate/src/img/facebook-logo.svg
Clarivate on Instagram ul.list-unstyled > li.list-inline-item > a > img
clarivate.com/wp-content/themes/clarivate/src/img/instagram-logo.svg

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

●Max Potential First Input Delay 70 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoid long main-thread tasks 4 long tasks found
●Avoid non-composited animations 110 animated elements found
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 330 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
97

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Premium Data Sets div.card-body > div.d-flex > div > h5.card-title
Academia & Government div.card-body > div.d-flex > div > h5.card-title
Web of Science Platform div.card-body > div.d-flex > div > h5.card-title
Nandita Quaderi div.card-body > div.d-flex > div > h5.card-title
The Top 100 Global Innovators div.card-body > div.d-flex > div > h5.card-title
Insight or information? What trademark leaders really need from their IP manage… div.card-body > div.d-flex > div > h5.card-title

These are opportunities to improve keyboard navigation in your application.

Best practices

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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA `progressbar` elements have accessible names
●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
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[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
○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
○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
○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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting
Unload event listeners are deprecated and will be removed.
clarivate.com/ line 8, col 8711

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 451 ()

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS
●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 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
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
100

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.

○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 have descriptive text
●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