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.

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
/p/js_composer/assets/lib/vendor/dist/@fortawesome/fontaw...	400 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

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
nextcloud.com/c/themes/nextcloud-theme/dist/js/nc_cookies.js?ver=1	7.5 KiB
/c/themes/nextcloud-theme/dist/js/jquery.sticky-sidebar.m...	3.7 KiB
nextcloud.com/wp-includes/js/jquery/jquery.js?ver=3.7.1	82.1 KiB	50 ms
nextcloud.com/c/themes/nextcloud-theme/dist/css/theme.min.css?ver=1776694352	87.7 KiB	100 ms
nextcloud.com/p/js_composer/assets/css/js_composer.min.css?ver=8.7.2	44.9 KiB
nextcloud.com/p/js_composer/assets/css/js_composer_tta.min.css?ver=8.7.2	13.8 KiB
/p/js_composer/assets/lib/vendor/dist/@fortawesome/fontaw...	21.1 KiB
nextcloud.com/c/themes/nextcloud-theme/dist/css/bootstrap.min.css?ver=1762523483	22.5 KiB
nextcloud.com/wp-includes/css/dist/block-library/style.css?ver=6.9.1	16.3 KiB	50 ms
/p/js_composer/assets/lib/vendor/dist/@fortawesome/fontaw...	4.1 KiB	50 ms
/c/themes/nextcloud-theme/dist/js/jquery.magnific-popup.m...	7.2 KiB	50 ms
nextcloud.com/wp-includes/js/jquery/jquery-migrate.js?ver=3.4.1	9.9 KiB
nextcloud.com/c/themes/nextcloud-theme/style.css?ver=1748585939	248 B
nextcloud.com/c/themes/nextcloud-theme/dist/css/slick.css?ver=1702023611	657 B
/c/sitepress-multilingual-cms/templates/language-switcher...	226 B

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
nextcloud.com/c/uploads/2026/04/Talk_Desktop.mp4	0.0 ms	5.5 MiB
nextcloud.com/c/uploads/2026/01/Assistant_01-1.mp4	0.0 ms	3.8 MiB
nextcloud.com/c/uploads/2026/01/Assistant_02.mp4	0.0 ms	3.7 MiB
nextcloud.com/c/uploads/2026/04/Talk_Mobile.mp4	0.0 ms	3.0 MiB
nextcloud.com/c/uploads/2026/04/Files_Desktop.mp4	0.0 ms	2.8 MiB
nextcloud.com/c/uploads/2026/04/Office_01.mp4	0.0 ms	2.8 MiB
nextcloud.com/c/uploads/2026/04/Files_Mobile.mp4	0.0 ms	2.5 MiB
nextcloud.com/c/uploads/2026/04/Groupware_01.mp4	0.0 ms	1.4 MiB
nextcloud.com/c/uploads/2025/12/Office_02.mp4	0.0 ms	1.3 MiB
nextcloud.com/c/uploads/2025/12/Groupware_03.mp4	0.0 ms	1.1 MiB
nextcloud.com/c/uploads/2025/12/office_03.mp4	0.0 ms	917.3 KiB
cdn.matomo.cloud/nextcloud.matomo.cloud/container_wlmEL4w2.js	691200.0 s	50.5 KiB

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
div.wpb_wrapper > a > div.nc_videos_repeater > video#nc_video `div.wpb_wrapper > a > div.nc_videos_repeater > video#nc_video`	nextcloud.com/c/uploads/2026/04/Files_Desktop_poster.jpg	87.8 KiB	82.1 KiB
div.wpb_wrapper > a > div.nc_videos_repeater > video#nc_video `div.wpb_wrapper > a > div.nc_videos_repeater > video#nc_video`	nextcloud.com/c/uploads/2026/04/Files_Mobile_poster.jpg	56.3 KiB	55.2 KiB
div.wpb_wrapper > div.vc_btn3-container > a.vc_general > ::after `div.wpb_wrapper > div.vc_btn3-container > a.vc_general > ::after`	nextcloud.com/c/themes/nextcloud-theme/dist/img/26Winter-Promo-graphic-web.png	18.5 KiB	5.0 KiB

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

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 49.1 KiB

URL	Transfer Size	Est Savings
nextcloud.com/wp-includes/js/jquery/jquery.js?ver=3.7.1	82.1 KiB	42.0 KiB
nextcloud.com/wp-includes/js/jquery/jquery-migrate.js?ver=3.4.1	9.9 KiB	4.0 KiB
nextcloud.com/c/themes/nextcloud-theme/dist/js/nc_cookies.js?ver=1	7.4 KiB	3.1 KiB

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: 150 ms 198.7 KiB

URL	Transfer Size	Est Savings
nextcloud.com/c/themes/nextcloud-theme/dist/css/theme.min.css?ver=1776694352	87.6 KiB	82.4 KiB
nextcloud.com/p/js_composer/assets/css/js_composer.min.css?ver=8.7.2	44.9 KiB	44.1 KiB
nextcloud.com/c/themes/nextcloud-theme/dist/css/bootstrap.min.css?ver=1762523483	22.5 KiB	22.0 KiB
/p/js_composer/assets/lib/vendor/dist/@fortawesome/fontaw...	21.0 KiB	20.7 KiB
nextcloud.com/wp-includes/css/dist/block-library/style.css?ver=6.9.1	16.2 KiB	16.1 KiB
nextcloud.com/p/js_composer/assets/css/js_composer_tta.min.css?ver=8.7.2	13.8 KiB	13.5 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 73.0 KiB

URL	Transfer Size	Est Savings
nextcloud.com/wp-includes/js/jquery/jquery.js?ver=3.7.1	82.1 KiB	50.5 KiB
cdn.matomo.cloud/nextcloud.matomo.cloud/container_wlmEL4w2.js	50.0 KiB	22.5 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 14.0 KiB

URL	Transfer Size	Est Savings
nextcloud.com/c/themes/nextcloud-theme/dist/css/theme.min.css?ver=1776694352	87.7 KiB	14.0 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
nextcloud.com/c/uploads/2026/04/Talk_Desktop.mp4	5.5 MiB
nextcloud.com/c/uploads/2026/01/Assistant_01-1.mp4	3.8 MiB
nextcloud.com/c/uploads/2026/01/Assistant_02.mp4	3.7 MiB
nextcloud.com/c/uploads/2026/04/Talk_Mobile.mp4	3.0 MiB
nextcloud.com/c/uploads/2026/04/Files_Desktop.mp4	2.8 MiB
nextcloud.com/c/uploads/2026/04/Office_01.mp4	2.8 MiB
nextcloud.com/c/uploads/2026/04/Files_Mobile.mp4	2.5 MiB
nextcloud.com/c/uploads/2026/04/Groupware_01.mp4	1.4 MiB
nextcloud.com/c/uploads/2025/12/Office_02.mp4	1.3 MiB
nextcloud.com/c/uploads/2025/12/Groupware_03.mp4	1.1 MiB

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
ul#menu-primary-menu > li.nav-btn > a#nav-instant-trial > img.navcon `ul#menu-primary-menu > li.nav-btn > a#nav-instant-trial > img.navcon`	nextcloud.com/c/uploads/2026/01/instant-trial-icon.svg

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

●Time to Interactive 1.5 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●JavaScript execution time 0.0 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 1 long task found

●Avoid non-composited animations 4 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 80 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 60 ms

●Avoid large layout shifts 7 layout shifts found

○INP breakdown

○User Timing marks and measures

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ENGLISH `nav#menu-primary-menu-container > ul#menu-primary-menu > li.menu-item > a`
Nextcloud Files `div.vc_tta-panels > div#nextcloud_files_tab > div.vc_tta-panel-heading > h4#custom-heading-nextcloud_files_tab`
Nextcloud Talk `div.vc_tta-panels > div#nextcloud_talk_tab > div.vc_tta-panel-heading > h4#custom-heading-nextcloud_talk_tab`
Nextcloud Groupware `div.vc_tta-panels > div#nextcloud_groupware_tab > div.vc_tta-panel-heading > h4#custom-heading-nextcloud_groupware_tab`
Nextcloud Office `div.vc_tta-panels > div#nextcloud_office_tab > div.vc_tta-panel-heading > h4#custom-heading-nextcloud_office_tab`
Nextcloud Assistant `div.vc_tta-panels > div#nextcloud_assistant_tab > div.vc_tta-panel-heading > h4#custom-heading-nextcloud_assistant_tab`
Nextcloud Flow `div.vc_tta-panels > div#flow > div.vc_tta-panel-heading > h4#custom-heading-flow`

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
Learn more `div#nextcloud_files_tab > div#nextcloud_files_tab-body > div.vc_btn3-container > a.vc_general`
SOLUTIONS `div.wpb_wrapper > div.wpb_text_column > div.wpb_wrapper > p`
See more `a > div.iconbox_container > div.title_and_description > span.see_more`
See more `a > div.iconbox_container > div.title_and_description > span.see_more`
See more `a > div.iconbox_container > div.title_and_description > span.see_more`
HIPAA, GDPR AND MORE `div.wpb_wrapper > div.wpb_text_column > div.wpb_wrapper > p`
Privacy Policy `div.cookie_banner_inner > div.description > div.text > a`

These are opportunities to improve the legibility of your content.

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
Public sector `a > div.iconbox_container > div.title_and_description > h4.title`
Productivity `div.wpb_wrapper > div.wpb_text_column > div.wpb_wrapper > h4`
Compliance Kit `a > div.iconbox_container > div.title_and_description > h4.title`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.wpb_wrapper > div.wpb_single_image > figure.wpb_wrapper > a.vc_single_image-wrapper `div.wpb_wrapper > div.wpb_single_image > figure.wpb_wrapper > a.vc_single_image-wrapper`
div.wpb_wrapper > div.wpb_single_image > figure.wpb_wrapper > a.vc_single_image-wrapper `div.wpb_wrapper > div.wpb_single_image > figure.wpb_wrapper > a.vc_single_image-wrapper`

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.

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.no-js `html.no-js`

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

●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 are distinguishable without relying on color.

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

●`[lang]` attributes have a valid value

●Skip links are focusable.

●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

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

○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

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○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

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

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

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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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.

Link destination	Link Text
nextcloud.com/blog/nextcloud-hub26-winter/	Read more
nextcloud.com/files/	Learn more
nextcloud.com/customers/#interviews	Learn more

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`