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.

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
pagead2.googlesyndication.com/pagead/js/lidar.js?fcd=true	3600.0 s	83.4 KiB
/pagead/managed/js/adsense/m202607010101/show_ads_impl_fy...	1209600.0 s	165.1 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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.069 source:map[column:31 line:1657 type:source-location url:https://www.mybts.fr/ urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:47.609 source:map[type:text value:[unattributed]]] map[reflowTime:0.069 source:map[column:404 line:1606 type:source-location url:https://www.mybts.fr/ urlProvider:network]]]

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

nodeLabel: My BTS Menu principal Aller au contenu principal Aller au contenu secondaire Ac…

path: 5,HTML,2,BODY,6,DIV,0,HEADER

selector: body.home > div#page > header#branding

snippet: <header id="branding" role="banner">

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

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
www.mybts.fr/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	30.0 KiB	182 ms
www.mybts.fr/wp-content/tablepress-combined.min.css?ver=64	2.3 KiB
/wp-content/plugins/forget-about-shortcode-buttons/public...	1.7 KiB
/wp-content/plugins/easy-digital-downloads/assets/build/c...	4.7 KiB
www.mybts.fr/wp-content/uploads/rmp-menu/css/rmp-menu.css?ver=05.17.59	2.5 KiB
www.mybts.fr/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.1 KiB
www.mybts.fr/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70	593 B
www.mybts.fr/wp-content/plugins/crazy-pills/css/styles.css?ver=0.4.3	2.1 KiB
www.mybts.fr/wp-includes/css/dashicons.min.css	35.2 KiB	182 ms
/wp-content/plugins/easy-digital-downloads/includes/block...	533 B
/wp-content/plugins/forget-about-shortcode-buttons/public...	12.9 KiB
www.mybts.fr/wp-content/themes/twentyeleven43/style.css	13.5 KiB
www.mybts.fr/wp-content/themes/twentyeleven43/blocks.css?ver=20230122	2.1 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.entry-summary > div.excerpt-thumb > a > img.alignleft `div.entry-summary > div.excerpt-thumb > a > img.alignleft`	www.mybts.fr/wp-content/uploads/calculateur-prix-vente.png	22.5 KiB	20.2 KiB
Découvrir tous les calculateurs BTS MCO gratuits `div#secondary > aside#media_image-14 > a > img.image`	www.mybts.fr/wp-content/uploads/tous-les-calculateurs.webp	15.2 KiB	10.9 KiB
div.entry-summary > div.excerpt-thumb > a > img.alignleft `div.entry-summary > div.excerpt-thumb > a > img.alignleft`	www.mybts.fr/wp-content/uploads/qcm-facturation-bts-mco-corrigees.webp	6.6 KiB	4.4 KiB

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: 80 ms 59.0 KiB

URL	Transfer Size	Est Savings
www.mybts.fr/wp-includes/css/dashicons.min.css	34.9 KiB	34.9 KiB
/wp-content/plugins/forget-about-shortcode-buttons/public...	12.6 KiB	12.6 KiB
www.mybts.fr/wp-content/themes/twentyeleven43/style.css	13.2 KiB	11.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: 80 ms 338.3 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/adsense/m202607010101/show_ads_impl_fy...	165.1 KiB	120.3 KiB
www.googletagmanager.com/gtag/js?id=G-VNCZT0PMG9	159.6 KiB	67.3 KiB
pagead2.googlesyndication.com/pagead/js/lidar.js?fcd=true	83.3 KiB	65.6 KiB
/i/ca-pub-2232486685154121?href=https%3A%2F%2Fwww.mybts.f...	69.0 KiB	35.6 KiB
/pagead/js/adsbygoogle.js?client=ca-pub-2232486685154121	54.5 KiB	29.1 KiB
www.mybts.fr/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	29.7 KiB	20.3 KiB

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 reason	Failure type
The page has an unload handler in the main frame.	Actionable

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

URL	Transfer Size	Est Savings
www.mybts.fr/wp-content/themes/twentyeleven43/style.css	13.5 KiB	3.5 KiB
/* ===================================================== / / ================== VERSION DESKTOP =…	3.8 KiB	2.1 KiB

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 787 ms

URL	Time Spent
www.mybts.fr/	887 ms

●Time to Interactive 2.4 s

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Avoids enormous network payloads Total size was 937 KiB

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.7 s

●Avoid long main-thread tasks 4 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 140 ms

●Server Backend Latencies 20 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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
Navigation des articles `div#primary > div#content > nav#nav-below > h3.assistive-text`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
33 `div#content > nav#nav-below > div.wp-pagenavi > a.last`

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	pagead2.googlesyndication.com/pagead/js/lidar.js?fcd=true line 10, col 9148

●Uses HTTPS

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`