Skip to content
https://openoffice.org

Lighthouse Mobile

· 0 checks — Mobile 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.

94

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.

RequestCache TTLTransfer Size
www.openoffice.org/images/AOO_logos/100MillAOO100px.png0.0 ms32.6 KiB
www.openoffice.org/css/styles.css0.0 ms18.9 KiB
www.openoffice.org/download/download.js0.0 ms12.7 KiB
www.openoffice.org/images/asf_logo_small.png0.0 ms6.2 KiB
www.openoffice.org/images/action-social.png0.0 ms4.9 KiB
www.openoffice.org/images/action-help.png0.0 ms4.7 KiB
www.openoffice.org/msg_prop_l10n.js0.0 ms4.6 KiB
www.openoffice.org/download/globalvars.js0.0 ms4.4 KiB
www.openoffice.org/images/action-info.png0.0 ms4.0 KiB
www.openoffice.org/images/action-participate.png0.0 ms3.8 KiB
www.openoffice.org/download/languages.js0.0 ms3.8 KiB
www.openoffice.org/css/ooo.css0.0 ms3.4 KiB
www.openoffice.org/images/action-download.png0.0 ms3.3 KiB
www.openoffice.org/css/exceptions.css0.0 ms3.3 KiB
www.openoffice.org/images/action-extend.png0.0 ms2.9 KiB
www.openoffice.org/css/home.css0.0 ms2.8 KiB
www.openoffice.org/images/logo-rss-16.png0.0 ms1.7 KiB
www.openoffice.org/images/logo-youtube-16.png0.0 ms1.6 KiB
www.openoffice.org/images/logo-facebook-16.png0.0 ms1.5 KiB
www.openoffice.org/images/logo-twitter-16.png0.0 ms1.4 KiB
www.openoffice.org/images/campaign-divider.png0.0 ms1.4 KiB

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.

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.

URLProtocol
www.openoffice.org/http/1.1
www.openoffice.org/css/ooo.csshttp/1.1
www.openoffice.org/download/globalvars.jshttp/1.1
www.openoffice.org/msg_prop_l10n.jshttp/1.1
www.openoffice.org/download/languages.jshttp/1.1
www.openoffice.org/download/download.jshttp/1.1
www.openoffice.org/css/home.csshttp/1.1
www.openoffice.org/css/styles.csshttp/1.1
www.openoffice.org/css/exceptions.csshttp/1.1
www.openoffice.org/images/AOO_logos/100MillAOO100px.pnghttp/1.1
www.openoffice.org/images/logo-rss-16.pnghttp/1.1
www.openoffice.org/images/logo-facebook-16.pnghttp/1.1
www.openoffice.org/images/logo-twitter-16.pnghttp/1.1
www.openoffice.org/images/logo-youtube-16.pnghttp/1.1
www.openoffice.org/images/asf_logo_small.pnghttp/1.1
www.openoffice.org/images/action-info.pnghttp/1.1
www.openoffice.org/images/action-download.pnghttp/1.1
www.openoffice.org/images/action-help.pnghttp/1.1
www.openoffice.org/images/action-extend.pnghttp/1.1
www.openoffice.org/images/action-participate.pnghttp/1.1
www.openoffice.org/images/action-social.pnghttp/1.1
www.openoffice.org/images/campaign-divider.pnghttp/1.1
www.openoffice.org/favicon.icohttp/1.1

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.

URLTransfer SizeDuration
www.openoffice.org/css/styles.css18.9 KiB903 ms
www.openoffice.org/download/download.js12.7 KiB453 ms
www.openoffice.org/msg_prop_l10n.js4.6 KiB603 ms
www.openoffice.org/download/languages.js3.8 KiB153 ms
www.openoffice.org/download/globalvars.js4.4 KiB603 ms
www.openoffice.org/css/exceptions.css3.3 KiB453 ms
www.openoffice.org/css/home.css2.8 KiB453 ms
www.openoffice.org/css/ooo.css3.4 KiB153 ms
www.apachecon.com/event-images/snippet.js0 B780 ms

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
Apache OpenOffice div#bannera > div#bannerleft > a > img#ooo-logo
www.openoffice.org/images/AOO_logos/100MillAOO100px.png31.5 KiB25.9 KiB

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

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.

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: 0.0 ms 17.3 KiB
URLTransfer SizeEst Savings
www.openoffice.org/css/styles.css17.8 KiB17.3 KiB

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 5.5 KiB
URLTransfer SizeEst Savings
www.openoffice.org/download/download.js11.5 KiB5.5 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
Apache OpenOffice div#bannera > div#bannerleft > a > img#ooo-logo
www.openoffice.org/images/AOO_logos/100MillAOO100px.png
Blog div.action-social-extra > p > span > img
www.openoffice.org/images/logo-rss-16.png
Facebook div.action-social-extra > p > span > img
www.openoffice.org/images/logo-facebook-16.png
Twitter div.action-social-extra > p > span > img
www.openoffice.org/images/logo-twitter-16.png
YouTube div.action-social-extra > p > span > img
www.openoffice.org/images/logo-youtube-16.png

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

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: 757 ms
URLTime Spent
openoffice.org/757 ms
www.openoffice.org/0.0 ms
●Time to Interactive 2.5 s
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Max Potential First Input Delay 20 ms
●Minify CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 167 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.4 s
●Avoid long main-thread tasks 1 long task found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 0 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 100 ms
●Avoid large layout shifts 4 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
76

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
Language Asturianu (ast) Català (ca) Čeština (cs) Dansk (da) Deutsch (de) Engl… body > div#bannera > div#languagesdiv
The Free and Open Productivity Suite body > div#bannera > div#bannercenter
Product div#topnava > ul > li > a
Download div#topnava > ul > li > a
Support div#topnava > ul > li > a
Blog div#topnava > ul > li > a
Extensions & Templates div#topnava > ul > li > a
Get Involved div#topnava > ul > li > a
Focus Areas div#topnava > ul > li > a
Native Languages div#topnava > ul > li > a
home body > div#topbara > div#breadcrumbsa > a
All Posts div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.16 div#news > div.first > p > a
Development Update - April 2024 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.15 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.14 div#news > div.first > p > a
333,333,333+ Downloads of Apache OpenOffice div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.13 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.12 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.11 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.10 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.9 div#news > div.first > p > a
New release for Apple's macOS 11 (Big Sur) - Also with fixes for Linux and Wind… div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.8 div#news > div.first > p > a
300 Million Downloads of Apache OpenOffice div#news > div.first > p > a
The Apache Software Foundation Celebrates 20 Years of OpenOffice® div#news > div.first > p > a
Apache OpenOffice needs your help div#news > div.first > p > a
1.6 million downloads of Apache OpenOffice 4.1.7 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.7 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.6 div#news > div.first > p > a
Over 3.2 million downloads of Apache OpenOffice 4.1.5 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.5 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.4 div#news > div.first > p > a
Over 200 million downloads of Apache OpenOffice div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.3 div#news > div.first > p > a
Announcing Apache OpenOffice 4.1.2 div#news > div.first > p > a
Coming soon... Apache OpenOffice 4.1.2 div#news > div.first > p > a
Authoring e-Books in Apache OpenOffice div#news > div.first > p > a
Collaboration is in our DNA div#news > div.first > p > a
Copyright & License div#footera > div#copyrighta > p > a
Privacy div#footera > div#copyrighta > p > a
Contact Us div#footera > div#copyrighta > p > a
Donate div#footera > div#copyrighta > p > a
Thanks div#footera > div#copyrighta > p > a

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Asturianu (ast) Català (ca) Čeština (cs) Dansk (da) Deutsch (de) English [US] (… body > div#bannera > div#languagesdiv > select#selectlanguage

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 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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●Document has a `<title>` element
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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 a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○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.
88

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Apache OpenOffice div#bannera > div#bannerleft > a > img#ooo-logo
www.openoffice.org/images/AOO_logos/100MillAOO100px.png348 x 100348 x 100522 x 150
The ASF div#poweredbya > p > a > img
www.openoffice.org/images/asf_logo_small.png188 x 76188 x 76282 x 114
Facebook div.action-social-extra > p > span > img
www.openoffice.org/images/logo-facebook-16.png16 x 1616 x 1624 x 24
Blog div.action-social-extra > p > span > img
www.openoffice.org/images/logo-rss-16.png16 x 1616 x 1624 x 24
Twitter div.action-social-extra > p > span > img
www.openoffice.org/images/logo-twitter-16.png16 x 1616 x 1624 x 24
YouTube div.action-social-extra > p > span > img
www.openoffice.org/images/logo-youtube-16.png16 x 1616 x 1624 x 24

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.openoffice.org/ line 1036, col 0
Loading the image 'https://www.w3.org/Icons/valid-xhtml10-blue.png' violates the following Content Security Policy directive: "default-src 'self' data: blob: 'unsafe-inline' 'unsafe-eval' https://www.apachecon.com/ https://www.communityovercode.org/ https://*.apache.org/ https://apache.org/ https://*.scarf.sh/". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●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
●Page has the HTML doctype
●Properly defines charset
●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
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