Skip to content
https://roche.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.

71

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.

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.

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
decorative image div.teaser__media-container > figure.image > div.image__container > img.image__img
/f/176343/2592x1944/0ef73b4ea6/roche-full-year-ar2025.jpg...46.6 KiB32.6 KiB
decorative image div.teaser__media-container > figure.image > div.image__container > img.image__img
/f/176343/2592x1944/0ef73b4ea6/roche-full-year-ar2025.jpg...32.7 KiB23.4 KiB
Two masked women are seated at a desk, collaborating on tasks and discussing th… div.story-teaser__media-container > figure.image > div.image__container > img.image__img
/f/176343/1920x1080/cc17ee3aff/wfh-sri-lanka_high-res-ima...34.8 KiB22.3 KiB
Two masked women are seated at a desk, collaborating on tasks and discussing th… div.story-teaser__media-container > figure.image > div.image__container > img.image__img
/f/176343/1920x1080/cc17ee3aff/wfh-sri-lanka_high-res-ima...40.4 KiB22.1 KiB
Smiling person with long dark hair, wearing a rainbow lanyard, indoors. Bright … div.hero-teaser__media-container > figure.image > div.image__container > img.image__img
/f/176343/2000x1334/ccfefc80a2/pred-collaboration-space-4...22.9 KiB13.5 KiB
Smiling person with long dark hair, wearing a rainbow lanyard, indoors. Bright … div.hero-teaser__media-container > figure.image > div.image__container > img.image__img
/f/176343/2000x1334/ccfefc80a2/pred-collaboration-space-4...42.5 KiB9.8 KiB
Decorative illustration div.story-teaser__media-container > figure.image > div.image__container > img.image__img
/f/176343/1920x1080/504154d2ce/1164695-ash-backgrounder-a...17.2 KiB4.7 KiB
Decorative Illustration div.story-teaser__media-container > figure.image > div.image__container > img.image__img
/f/176343/740x416/617c25b70f/article-teaser.jpg/m/320x240...17.0 KiB4.5 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:800.594 label:Time to first byte subpart:timeToFirstByte] map[duration:1920.581 label:Resource load delay subpart:resourceLoadDelay] map[duration:21.76 label:Resource load duration subpart:resourceLoadDuration] map[duration:134.084 label:Element render delay subpart:elementRenderDelay]]
lhId: page-5-IMG
nodeLabel: Roche apprentices examining results of bacteria growth on agar culture medium, …
path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,3,MAIN,0,DIV,0,DIV,1,DIV,0,DIV,2,DIV,0,FIGURE,0,DIV,0,IMG
selector: div.side-by-side > figure.image > div.image__container > img.image__img
snippet: <img class="image__img image__img--ratio-hd" src="https://assets.roche.com/f/176343/1280x854/c0aeecd0b0/roche_34267.png/m/59…" srcset="https://assets.roche.com/f/176343/1280x854/c0aeecd0b0/roche_34267.png/m/59…" sizes="599px" alt="Roche apprentices examining results of bacteria growth on agar culture med…" loading="lazy">

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-5-IMG
nodeLabel: Roche apprentices examining results of bacteria growth on agar culture medium, …
path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,3,MAIN,0,DIV,0,DIV,1,DIV,0,DIV,2,DIV,0,FIGURE,0,DIV,0,IMG
selector: div.side-by-side > figure.image > div.image__container > img.image__img
snippet: <img class="image__img image__img--ratio-hd" src="https://assets.roche.com/f/176343/1280x854/c0aeecd0b0/roche_34267.png/m/59…" srcset="https://assets.roche.com/f/176343/1280x854/c0aeecd0b0/roche_34267.png/m/59…" sizes="599px" alt="Roche apprentices examining results of bacteria growth on agar culture med…" loading="lazy">

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

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.

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: 563 ms
URLTime Spent
roche.com/563 ms
www.roche.com/0.0 ms

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

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 61.1 KiB
URLTransfer SizeEst Savings
.icon-container{display:flex;justify-content:flex-start} …47.6 KiB41.0 KiB
23.0 KiB20.1 KiB

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

●Max Potential First Input Delay 100 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,868 KiB
●User Timing marks and measures 1 user timing
●JavaScript execution time 0.7 s
●Minimizes main-thread work 1.2 s
●Avoid long main-thread tasks 4 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 110 ms
●Server Backend Latencies 350 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 440 ms
●Avoid large layout shifts 15 layout shifts found
○INP breakdown
100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
How we improved outcomes for patients around the world With our combined stren… div.grid__columns > div.grid__column > div.teaser > a.teaser__link-wrapper
Roche publishes its Full Year results for 2025 Roche reports 7% (CER) sales fo… div.grid__columns > div.grid__column > div.teaser > a.teaser__link-wrapper
Rare within rare: Women with haemophilia April 14, 2022 div.swiper > div#swiper-wrapper-c31a8636cb10279a4 > div.swiper-slide > a.story-teaser
Haemophilia treatment for all: A partnership for better access May 06, 2022 div.swiper > div#swiper-wrapper-c31a8636cb10279a4 > div.swiper-slide > a.story-teaser
Haemophilia A in infants December 07, 2022 div.swiper > div#swiper-wrapper-c31a8636cb10279a4 > div.swiper-slide > a.story-teaser
About Roche We unite leading science and technology across diagnostics, medici… div#swiper-wrapper-14c8fe8cb4304ee7 > div.swiper-slide > div.teaser > a.teaser__link-wrapper
Solutions We are committed to tackling the most complex healthcare challenges … div#swiper-wrapper-14c8fe8cb4304ee7 > div.swiper-slide > div.teaser > a.teaser__link-wrapper
Innovation In everything we do, we are guided by the needs of patients and the… div#swiper-wrapper-14c8fe8cb4304ee7 > div.swiper-slide > div.teaser > a.teaser__link-wrapper
○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
●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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 are distinguishable without relying on color.
●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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields 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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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

General

●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
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○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.

Why this matters

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.

○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