Skip to content
https://tmsarl.netlify.app

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.

87

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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:180.509 label:Time to first byte subpart:timeToFirstByte] map[duration:104.216 label:Resource load delay subpart:resourceLoadDelay] map[duration:161.174 label:Resource load duration subpart:resourceLoadDuration] map[duration:3089.109 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: Équipements médicaux TMS SARL
path: 1,HTML,1,BODY,5,MAIN,1,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,IMG
selector: div.hero-split > div.hero-visual > div.hero-image-wrapper > img
snippet: <img src="images/hero-medical-equipment.webp" alt="Équipements médicaux TMS SARL" loading="lazy" width="600" height="400" onerror="this.src='data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22…">

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: Équipements médicaux TMS SARL
path: 1,HTML,1,BODY,5,MAIN,1,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,IMG
selector: div.hero-split > div.hero-visual > div.hero-image-wrapper > img
snippet: <img src="images/hero-medical-equipment.webp" alt="Équipements médicaux TMS SARL" loading="lazy" width="600" height="400" onerror="this.src='data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22…">

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
tmsarl.netlify.app/.netlify/scripts/hud?variant=public60.0 s10.0 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.

URLResource SizeEst Savings
Kit laboratoire complet div.container > div.grid > div.product-card > img.card-image
tmsarl.netlify.app/images/produits/Labo.webp74.6 KiB49.3 KiB
Équipement de laboratoire div.container > div.grid > div.product-card > img.card-image
tmsarl.netlify.app/images/produits/labo.webp74.6 KiB49.3 KiB
Équipement salle d'opération div.container > div.grid > div.product-card > img.card-image
tmsarl.netlify.app/images/produits/salle-de-chirugie.webp49.7 KiB33.8 KiB
Scanner IRM 3T div.container > div.grid > div.product-card > img.card-image
tmsarl.netlify.app/images/produits/IRM-scan.webp58.0 KiB32.7 KiB
Dr. Jean Kouam div.container > div.grid > div.col-span-3 > img.team-member-image
tmsarl.netlify.app/images/equipe/docteur2.jfif24.4 KiB23.0 KiB
Électrocardiogramme digital div.container > div.grid > div.product-card > img.card-image
tmsarl.netlify.app/images/produits/ECG.webp26.6 KiB18.1 KiB
Matériel médical divers div.container > div.grid > div.product-card > img.card-image
tmsarl.netlify.app/images/produits/materiel.webp33.7 KiB17.5 KiB
Équipement d'imagerie médicale div.container > div.grid > div.product-card > img.card-image
tmsarl.netlify.app/images/produits/Irm-img.webp25.0 KiB17.0 KiB
Microscope de laboratoire div.container > div.grid > div.product-card > img.card-image
tmsarl.netlify.app/images/produits/Microscope.webp24.2 KiB16.4 KiB
Dr. Alice Mbala div.container > div.grid > div.col-span-3 > img.team-member-image
tmsarl.netlify.app/images/equipe/docteur1.jfif14.1 KiB12.1 KiB
Matériel médical div.container > div.grid > div.product-card > img.card-image
tmsarl.netlify.app/images/produits/istockphoto-1283314480-612x612.webp15.2 KiB11.0 KiB
Histoire de TMS SARL div.container > div.grid > div.col-span-6 > img.card-image
tmsarl.netlify.app/images/produits/about.webp20.5 KiB9.0 KiB
Dr. Marie Tchameni div.container > div.grid > div.col-span-3 > img.team-member-image
tmsarl.netlify.app/images/equipe/docteur3.jfif9.8 KiB7.7 KiB
Dr. Paul Nguembu div.container > div.grid > div.col-span-3 > img.team-member-image
tmsarl.netlify.app/images/equipe/docteur4.jfif8.9 KiB6.8 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: 60 ms 14.1 KiB
URLTransfer SizeEst Savings
cdnjs.cloudflare.com/ajax/libs/remixicon/4.6.0/remixicon.min.css14.3 KiB14.1 KiB

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

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 3.1 KiB
URLTransfer SizeEst Savings
tmsarl.netlify.app/js/i18n.js15.4 KiB3.1 KiB

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

●Time to Interactive 2.4 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Modern HTTP
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Max Potential First Input Delay 30 ms
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 849 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.4 s
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 1,660 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 130 ms
●Avoid large layout shifts 6 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
96

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
MICROSCOPIE div.grid > div.product-card > div.card-body > span.card-tag
CARDIOLOGIE div.grid > div.product-card > div.card-body > span.card-tag
IMAGERIE div.grid > div.product-card > div.card-body > span.card-tag
LABORATOIRE div.grid > div.product-card > div.card-body > span.card-tag
CHIRURGIE div.grid > div.product-card > div.card-body > span.card-tag
ÉQUIPEMENT div.grid > div.product-card > div.card-body > span.card-tag
IMAGERIE div.grid > div.product-card > div.card-body > span.card-tag
LABORATOIRE div.grid > div.product-card > div.card-body > span.card-tag
ÉQUIPEMENT div.grid > div.product-card > div.card-body > span.card-tag
À PROPOS DE TMS SARL div.container > div.grid > div.col-span-6 > span.label-sm
TMS SARL div.col-span-4 > div.footer-brand > a.navbar-logo > span.script

These are opportunities to improve the legibility of your content.

○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
●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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<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.
○Identical links have the same purpose.
○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
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○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