Skip to content
https://site123.me

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.

55

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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
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
/versions/2/system_mini/css/minimizeSITE123website.css?v=...29.4 KiB905 ms

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.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
pixel.byspotify.com/ping.min.js3600.0 s10.3 KiB
/collect/?pid=32899&fmt=gif&e_ipv6=AQKcrmSpKuF5nAAAAZ2yBX...0.0 ms778 B
/rp.gif?ts=1776808194807&id=t2_2h4l5gmu&event=PageVisit&m...0.0 ms666 B
/_/ad/c8f86d2183d6400d8288bbf9f7d9e950/pixel?tag=ViewCont...0.0 ms347 B
www.facebook.com/tr?id=1074611005929279&ev=PageView&noscript=10.0 ms19 B

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.

URLEst Savings
/files/fontawesome-pro-6.7.1-web/webfonts/fa-light-300.woff210 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
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
files.cdn-files-a.com/admin/websitesPluginsManager/800_69ddf9410c784.png33.6 KiB26.7 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: 3.0 s
URLTime Spent
site123.me/850 ms
www.site123.me/630 ms
www.site123.me/458 ms
www.site123.com/1.0 s
fr.site123.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

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

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: 350 ms 83.2 KiB
URLTransfer SizeEst Savings
/files/fontawesome-pro-6.7.1-web/css/fontawesome.min.css?...56.8 KiB56.4 KiB
/versions/2/system_mini/css/minimizeSITE123website.css?v=...28.8 KiB26.8 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: 300 ms 179.7 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-JGWK0XY7J6&cx=c&gtm=4e64h1171.9 KiB67.0 KiB
/versions/2/system_mini/js/minimizeSITE123website.js?v=y8...97.6 KiB61.5 KiB
www.googletagmanager.com/gtag/js?id=AW-741508231141.9 KiB51.3 KiB

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.

CategoryTime Spent
Script Evaluation1.0 s
Other395 ms
Style & Layout361 ms
Script Parsing & Compilation154 ms
Parse HTML & CSS81 ms
Rendering51 ms
Garbage Collection9.4 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with WebSocket cannot enter back/forward cache.Pending browser support

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
SITE123 logo div.row > div.col-xs-12 > a > img.site123_logo
/admin/InterfaceStatisFiles/allOther/all/site123/logos/Lo...
logo body.language_fr > div.mobileMenuFromSide > div.mobileMenuHeader > img.site123_logo
/admin/InterfaceStatisFiles/allOther/all/site123/logos/Lo...
SITE123 logo div.col-xs-12 > div.logoPlace > a > img.site123_logo
/admin/InterfaceStatisFiles/allOther/all/site123/logos/Lo...
Ce qui fait de nous le meilleur créateur de site Web div.row > div.col-xs-12 > div.rightSide > img.homepage_image_p
Créez votre site Web d'entreprise en 3 étapes faciles div.row > div.col-xs-12 > div.rightSide > img.homepage_image_p
Créez votre boutique en ligne en un rien de temps div.row > div.col-xs-12 > div.rightSide > img.homepage_image_p
Support par Chat div.row > div.col-xs-12 > div.rightSide > img.img-rounded

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,201 KiB
●User Timing marks and measures 14 user timings
●JavaScript execution time 1.0 s
●Avoid long main-thread tasks 8 long tasks found
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 160 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 0 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
60

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
Se connecter div.mobileMenuFromSide > div.mobile-menu-main-btns > a.btn > span
COMMENCER ICI div.mobileMenuFromSide > div.mobile-menu-main-btns > a.btn > span
COMMENCER ICI div.row > div.col-xs-12 > div.start-content > a.btn

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
Des milliers de clients satisfaits section.container-fluid > div.container > div.sectionHeader > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy

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.container > div.row > div.col-xs-12 > a div.container > div.row > div.col-xs-12 > a
div.container > div.row > div.col-xs-12 > a div.container > div.row > div.col-xs-12 > a
div.container > div.row > div.col-xs-12 > a div.container > div.row > div.col-xs-12 > a
div.container > div.row > div.col-xs-12 > a div.container > div.row > div.col-xs-12 > a
div.container > div.row > div.col-xs-12 > a div.container > div.row > div.col-xs-12 > a
div.container > div.row > div.col-xs-12 > a div.container > div.row > div.col-xs-12 > a
div.container > div.row > div.col-xs-12 > a div.container > div.row > div.col-xs-12 > a
div.container > div.row > div.col-xs-12 > a div.container > div.row > div.col-xs-12 > a
div.container > div.row > div.col-xs-12 > a div.container > div.row > div.col-xs-12 > a
div.socialIcons > ul > li > a div.socialIcons > ul > li > a
div.socialIcons > ul > li > a div.socialIcons > ul > li > a
div.socialIcons > ul > li > a div.socialIcons > ul > li > a
div.socialIcons > ul > li > a div.socialIcons > ul > li > a

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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>`
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
○`[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 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 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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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.
81

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.site123.me/Allowed
●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
85

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
nav > ul.site123_nav > li > a.languageModalElement nav > ul.site123_nav > li > a.languageModalElement
Français nav > ul.site123_nav > li > a.languageModalElement
Français div.row > div.col-xs-12 > div > a.languageModalElement

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

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy
div.row > div.col-xs-12 > a > img.lazy div.row > div.col-xs-12 > a > img.lazy

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 have descriptive text
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback