Skip to content
https://libreoffice.org

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.

92

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.

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: Writer screenshot
path: 1,HTML,1,BODY,4,SECTION,0,DIV,1,DIV,0,IMG
selector: section#hero > div.hero-container > div.hero-screenshot-bg > img.hero-screenshot
snippet: <img class="hero-screenshot" src="/media/screenshot_writer_hero.png" alt="Writer screenshot">

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

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.

RequestCache TTLTransfer Size
piwik.documentfoundation.org/piwik.js0.0 ms25.5 KiB
www.libreoffice.org/media/screenshot_draw.png604800.0 s240.1 KiB
www.libreoffice.org/fonts/Lato-BoldItalic.woff2604800.0 s189.6 KiB
www.libreoffice.org/fonts/Lato-Bold.woff2604800.0 s181.4 KiB
www.libreoffice.org/fonts/Lato-Regular.woff2604800.0 s179.3 KiB
www.libreoffice.org/fonts/Lato-Black.woff2604800.0 s173.4 KiB
www.libreoffice.org/media/screenshot_writer.png604800.0 s113.8 KiB
www.libreoffice.org/media/screenshot_writer_hero.png604800.0 s97.4 KiB
www.libreoffice.org/media/screenshot_impress.png604800.0 s80.5 KiB
www.libreoffice.org/media/screenshot_base.png604800.0 s70.5 KiB
www.libreoffice.org/media/screenshot_calc.png604800.0 s58.3 KiB
www.libreoffice.org/js/leaflet.js604800.0 s51.2 KiB
www.libreoffice.org/media/screenshot_math.png604800.0 s39.8 KiB
www.libreoffice.org/media/illustration2.png604800.0 s12.3 KiB
www.libreoffice.org/js/flexsearch.js604800.0 s12.2 KiB
www.libreoffice.org/media/illustration3.png604800.0 s9.8 KiB
www.libreoffice.org/media/illustration1.png604800.0 s9.8 KiB
www.libreoffice.org/css/default.css604800.0 s9.4 KiB
b.tile.openstreetmap.org/2/1/0.png526677.0 s7.6 KiB
a.tile.openstreetmap.org/2/2/1.png518847.0 s6.4 KiB
c.tile.openstreetmap.org/2/1/1.png523351.0 s6.4 KiB
b.tile.openstreetmap.org/2/3/1.png525259.0 s5.2 KiB
www.libreoffice.org/js/community_map.js604800.0 s6.1 KiB
c.tile.openstreetmap.org/2/2/0.png521253.0 s4.7 KiB
www.libreoffice.org/media/libreoffice-tdf-logo.svg604800.0 s4.8 KiB
www.libreoffice.org/css/leaflet.css604800.0 s4.7 KiB
c.tile.openstreetmap.org/2/3/2.png525959.0 s3.8 KiB
a.tile.openstreetmap.org/2/3/0.png527291.0 s3.4 KiB
a.tile.openstreetmap.org/2/1/2.png518804.0 s3.0 KiB
www.libreoffice.org/js/libreoffice.js604800.0 s3.1 KiB
www.libreoffice.org/css/normalize.css604800.0 s2.5 KiB
www.libreoffice.org/js/download.js604800.0 s2.5 KiB
www.libreoffice.org/js/fastsearch.js604800.0 s2.4 KiB
b.tile.openstreetmap.org/2/2/2.png519407.0 s1.8 KiB
www.libreoffice.org/media/marker-icon.png604800.0 s2.1 KiB
www.libreoffice.org/media/subtle-prism.svg604800.0 s1.7 KiB
www.libreoffice.org/js/platform_detector.js604800.0 s1.6 KiB
www.libreoffice.org/media/searchicon.png604800.0 s1.4 KiB
www.libreoffice.org/media/libo-math.svg604800.0 s1.3 KiB
www.libreoffice.org/media/libo-impress.svg604800.0 s1.3 KiB
www.libreoffice.org/media/libo-writer.svg604800.0 s1.3 KiB
www.libreoffice.org/media/libo-draw.svg604800.0 s1.2 KiB
www.libreoffice.org/media/marker-shadow.png604800.0 s1.2 KiB
www.libreoffice.org/media/libo-calc.svg604800.0 s1.2 KiB
www.libreoffice.org/media/libo-base.svg604800.0 s1.2 KiB
www.libreoffice.org/js/matomo.js604800.0 s994 B

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
Draw screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_draw.png239.3 KiB230.6 KiB
Writer screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_writer.png113.0 KiB76.9 KiB
Impress screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_impress.png79.8 KiB74.4 KiB
Base screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_base.png69.8 KiB65.1 KiB
Calc screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_calc.png57.6 KiB53.8 KiB
Math screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_math.png39.1 KiB36.5 KiB

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.

URLTransfer Size
www.libreoffice.org/css/leaflet.css4.7 KiB
www.libreoffice.org/css/default.css9.4 KiB
www.libreoffice.org/css/normalize.css2.5 KiB

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: 712 ms
URLTime Spent
libreoffice.org/712 ms
www.libreoffice.org/0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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 3.0 KiB
URLTransfer SizeEst Savings
www.libreoffice.org/css/default.css9.4 KiB3.0 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 30.7 KiB
URLTransfer SizeEst Savings
www.libreoffice.org/js/leaflet.js50.6 KiB30.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
Writer screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_writer.png
Calc screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_calc.png
Draw screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_draw.png
Base screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_base.png
Math screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_math.png
Impress screenshot div.screenshots_container > div.sshot > div.sshot_img_container > img
www.libreoffice.org/media/screenshot_impress.png
Writer screenshot section#hero > div.hero-container > div.hero-screenshot-bg > img.hero-screenshot
www.libreoffice.org/media/screenshot_writer_hero.png
Illustration for no cost argument body.html-ltr > section#why_choose > aside.no-cost-arg > img
www.libreoffice.org/media/illustration1.png
Illustration for language argument body.html-ltr > section#why_choose > aside.language-arg > img
www.libreoffice.org/media/illustration2.png
Illustration for community argument body.html-ltr > section#why_choose > aside.community-arg > img
www.libreoffice.org/media/illustration3.png
LibreOffice nav.nav-main > h2 > a > img.logo
www.libreoffice.org/media/libreoffice-tdf-logo.svg
LibreOffice div.fullWidth-center > h2 > a > img.logo
www.libreoffice.org/media/libreoffice-tdf-logo.svg
Writer icon div.screenshots_container > div.sshot > div.shot-caption > img
www.libreoffice.org/media/libo-writer.svg
Calc icon div.screenshots_container > div.sshot > div.shot-caption > img
www.libreoffice.org/media/libo-calc.svg
Impress icon div.screenshots_container > div.sshot > div.shot-caption > img
www.libreoffice.org/media/libo-impress.svg
Draw icon div.screenshots_container > div.sshot > div.shot-caption > img
www.libreoffice.org/media/libo-draw.svg
Base icon div.screenshots_container > div.sshot > div.shot-caption > img
www.libreoffice.org/media/libo-base.svg
Math icon div.screenshots_container > div.sshot > div.shot-caption > img
www.libreoffice.org/media/libo-math.svg
Facebook div.ft-donate-lang-social > div.sm-container > a.sm-icon > img
Mastodon div.ft-donate-lang-social > div.sm-container > a.sm-icon > img
Reddit div.ft-donate-lang-social > div.sm-container > a.sm-icon > img
Youtube div.ft-donate-lang-social > div.sm-container > a.sm-icon > img
Twitter @tdforg div.ft-donate-lang-social > div.sm-container > a.sm-icon > img

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

●Time to Interactive 1.9 s
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,728 KiB
●JavaScript execution time 0.2 s
●Minimizes main-thread work 0.6 s
●Avoid long main-thread tasks 1 long task found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 160 ms
●Server Backend Latencies 330 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 170 ms
●Avoid large layout shifts 4 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
88

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
DONATE nav.nav-main > ul > li > a.button
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Read the guide book. div.shot-caption > div.sshot-description > p > a
Ilmari Lauhakangas section#join_our_community > div.opportunities > p > a
DESIGN div.opportunities > ul > li > a
LOCALISATION div.opportunities > ul > li > a
MARKETING div.opportunities > ul > li > a
DOCUMENTATION div.opportunities > ul > li > a
DEVELOPMENT div.opportunities > ul > li > a
INFRASTRUCTURE div.opportunities > ul > li > a
QUALITY ASSURANCE div.opportunities > ul > li > a
Join TDF section#join_our_community > div.opportunities > p > a
ZDNET section#what_people_are_saying > ul.fullWidth-center > li > a
TechRadar section#what_people_are_saying > ul.fullWidth-center > li > a
DONATE div.fullWidth-center > div.ft-donate-lang-social > p > a.button

These are opportunities to improve the legibility of your content.

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
Download About Us Get Help Community Blog DONATE body.html-ltr > div#nav-wrapper > nav.nav-main > ul

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

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
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon
Marker div#community_map > div.leaflet-pane > div.leaflet-pane > img.leaflet-marker-icon

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

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
●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.
●`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
●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.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○ARIA `progressbar` 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
○Buttons have an accessible name
○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.
○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.
○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.
96

Best Practices

General

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
www.libreoffice.org/js/libreoffice.js line 133, col 36
TypeError: Cannot read properties of undefined (reading 'startsWith') at https://www.libreoffice.org/js/libreoffice.js:134:37
●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 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
●Page has valid source maps
○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback