Lighthouse Mobile

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

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.

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.

URL	Transfer Size	Duration
odoocdn.com/web/assets/1/a617b1c/web.assets_frontend.min.css	286.4 KiB	3.7 s
/web/assets/1/1b5807e/social_push_notifications.assets_pu...	843 B	821 ms
fonts.googleapis.com/css?family=Inter:300,400,500,600&display=swap	862 B	819 ms
fonts.googleapis.com/css?family=Caveat:700&display=swap	965 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.

	URL	Resource Size	Est Savings
div.container > div.row > div.o_grid_item > img.w-100 `div.container > div.row > div.o_grid_item > img.w-100`	odoocdn.com/openerp_website/static/src/img/apps/home/mobile_productivity.webp	99.0 KiB	90.5 KiB
section.bg-200 > div.container > div.s_wd_persona > img.s_wd_persona_icon `section.bg-200 > div.container > div.s_wd_persona > img.s_wd_persona_icon`	odoocdn.com/openerp_website/static/src/img/snippets/s_wd_persona/bill.png	29.5 KiB	28.9 KiB
Spain `div.row > div.col-xl-9 > div.x_wd_notification_box > img.rounded-pill`	odoocdn.com/base/static/img/country_flags/es.png	7.4 KiB	7.4 KiB

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

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.

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: 811 ms

URL	Time Spent
odoo.com/	811 ms
www.odoo.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 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: 1.4 s 382.3 KiB

URL	Transfer Size	Est Savings
odoocdn.com/web/assets/1/a617b1c/web.assets_frontend.min.css	285.8 KiB	271.7 KiB
www.odoo.com/im_livechat/assets_embed.css	112.1 KiB	110.6 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: 3.9 s 817.5 KiB

URL	Transfer Size	Est Savings
odoocdn.com/web/assets/1/2ca246b/web.assets_frontend_lazy.min.js	1.4 MiB	817.5 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.

URL	Total CPU Time	Script Evaluation	Script Parse
odoocdn.com/web/assets/1/2ca246b/web.assets_frontend_lazy.min.js	1.8 s	1.1 s	574 ms
Unattributable	705 ms	17 ms	0.0 ms
www.odoo.com/	347 ms	35 ms	3.5 ms
odoocdn.com/web/assets/1/a617b1c/web.assets_frontend.min.css	160 ms	0.0 ms	0.0 ms

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.

Category	Time Spent
Script Evaluation	1.2 s
Other	751 ms
Script Parsing & Compilation	582 ms
Style & Layout	338 ms
Parse HTML & CSS	180 ms
Rendering	62 ms
Garbage Collection	18 ms

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 29.5 KiB

URL	Transfer Size	Est Savings
odoocdn.com/web/assets/1/a617b1c/web.assets_frontend.min.css	286.4 KiB	20.6 KiB
www.odoo.com/im_livechat/assets_embed.css	112.5 KiB	9.0 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
div.container > div.row > div.o_grid_item > img.w-100 `div.container > div.row > div.o_grid_item > img.w-100`	odoocdn.com/openerp_website/static/src/img/apps/home/mobile_productivity.webp
Spain `div.row > div.col-xl-9 > div.x_wd_notification_box > img.rounded-pill`	odoocdn.com/base/static/img/country_flags/es.png
div.row > div.col-lg-6 > a > img.align-top `div.row > div.col-lg-6 > a > img.align-top`	odoocdn.com/openerp_website/static/src/img/arrows/secondary_arrow_sm_03.svg
div.co-lg-6 > div.s_panel_video > a.btn_video_play > img.me-2 `div.co-lg-6 > div.s_panel_video > a.btn_video_play > img.me-2`	odoocdn.com/openerp_website/static/src/img/graphics/youtube.svg
Odoo Accounting icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/accountant/static/description/icon.svg
Odoo Knowledge icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/knowledge/static/description/icon.svg
Odoo Sign icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/sign/static/description/icon.svg
Odoo CRM icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/crm/static/description/icon.svg
Odoo Studio icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/web_studio/static/description/icon.svg
Odoo Subscriptions icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/sale_subscription/static/description/icon.svg
Odoo Unknown icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/ai_app/static/description/icon.svg
Odoo Point of Sale icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/point_of_sale/static/description/icon.svg
Odoo Discuss icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/mail/static/description/icon.svg
Odoo Documents icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/documents/static/description/icon.svg
Odoo Project icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/project/static/description/icon.svg
Odoo Timesheet icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/hr_timesheet/static/description/icon.svg
Odoo Field Service icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/industry_fsm/static/description/icon.svg
Odoo Planning icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/planning/static/description/icon.svg
Odoo Helpdesk icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/helpdesk/static/description/icon.svg
Odoo eCommerce icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/website_sale/static/description/icon.svg
Odoo Website icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/website/static/description/icon.svg
Odoo Email Marketing icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/mass_mailing/static/description/icon.svg
Odoo Purchase icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/purchase/static/description/icon.svg
Odoo Inventory icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/stock/static/description/icon.svg
Odoo Manufacturing icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/mrp/static/description/icon.svg
Odoo Sales icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/sale/static/description/icon.svg
Odoo Employees icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/hr/static/description/icon.svg
Odoo Spreadsheet dashboard icon `div.row > a.x_wd_app_entry > figure > img.img-thumbnail`	download.odoocdn.com/icons/spreadsheet_dashboard/static/description/icon.svg
div.container > div.row > div.co-lg-6 > img.rotate-40 `div.container > div.row > div.co-lg-6 > img.rotate-40`	odoocdn.com/openerp_website/static/src/img/graphics/arrow_doodle_3.svg
Odoo Sh AI `div.row > div.col-lg-7 > div.s_wd_features_item > img.img-thumbnail`
Unique value `div.row > div.col-lg-5 > div.s_wd_features_item > img.w-100`
div.container > div.row > div.col-lg-4 > img.img-thumbnail `div.container > div.row > div.col-lg-4 > img.img-thumbnail`
div#wrap > section.s_wd_call_to_action > div.container > img.d-block `div#wrap > section.s_wd_call_to_action > div.container > img.d-block`

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

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,259 KiB

●Avoid long main-thread tasks 9 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 50 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 60 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

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
Open source `div.row > div.col-lg-7 > div.s_wd_features_item > h4.s_wd_features_title`
Join 15 million users `div.container > div.position-absolute > div.bg-white > h6.display-2`

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.row > div.col-12 > div.o_footer_social_media > a.me-3 `div.row > div.col-12 > div.o_footer_social_media > a.me-3`
div.row > div.col-12 > div.o_footer_social_media > a.me-3 `div.row > div.col-12 > div.o_footer_social_media > a.me-3`
div.row > div.col-12 > div.o_footer_social_media > a.me-3 `div.row > div.col-12 > div.o_footer_social_media > a.me-3`
div.row > div.col-12 > div.o_footer_social_media > a.me-3 `div.row > div.col-12 > div.o_footer_social_media > a.me-3`
div.row > div.col-12 > div.o_footer_social_media > a.me-3 `div.row > div.col-12 > div.o_footer_social_media > a.me-3`
div.row > div.col-12 > div.o_footer_social_media > a.me-3 `div.row > div.col-12 > div.o_footer_social_media > a.me-3`
div.row > div.col-12 > div.o_footer_social_media > a.me-3 `div.row > div.col-12 > div.o_footer_social_media > a.me-3`

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.

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

●ARIA attributes are used as specified for the element's role

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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

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

○Identical links have the same purpose.

○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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
… `div.col-lg-10 > div.mb-n5 > div.row > a.btn`
`div.row > div.col-lg-10 > div.row > a.btn`

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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid