PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Feb 28, 2025, 8:00:43 AM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.5 s
Page LoadsGood (≤ 2.5 s)91%Needs Improvement (2.5 s - 4 s)6%Poor (> 4 s)3%75th Percentile - 1.5 sCore Web Vital
Interaction to Next Paint (INP)
253 ms
Page LoadsGood (≤ 200 ms)67%Needs Improvement (200 ms - 500 ms)23%Poor (> 500 ms)11%75th Percentile - 253 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)96%Needs Improvement (0.1 - 0.25)2%Poor (> 0.25)2%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.2 s
Page LoadsGood (≤ 1.8 s)89%Needs Improvement (1.8 s - 3 s)8%Poor (> 3 s)4%75th Percentile - 1.2 s 
Time to First Byte (TTFB)
0.7 s
Page LoadsGood (≤ 0.8 s)78%Needs Improvement (0.8 s - 1.8 s)17%Poor (> 1.8 s)5%75th Percentile - 0.7 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.3 s
Page LoadsGood (≤ 2.5 s)92%Needs Improvement (2.5 s - 4 s)6%Poor (> 4 s)3%75th Percentile - 1.3 sCore Web Vital
Interaction to Next Paint (INP)
261 ms
Page LoadsGood (≤ 200 ms)67%Needs Improvement (200 ms - 500 ms)20%Poor (> 500 ms)13%75th Percentile - 261 msCore Web Vital
Cumulative Layout Shift (CLS)
0.02
Page LoadsGood (≤ 0.1)95%Needs Improvement (0.1 - 0.25)2%Poor (> 0.25)3%75th Percentile - 0.02Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1 s
Page LoadsGood (≤ 1.8 s)89%Needs Improvement (1.8 s - 3 s)7%Poor (> 3 s)4%75th Percentile - 1 s 
Time to First Byte (TTFB)
0.7 s
Page LoadsGood (≤ 0.8 s)79%Needs Improvement (0.8 s - 1.8 s)14%Poor (> 1.8 s)7%75th Percentile - 0.7 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
86 FCP+9LCP+12TBT+30CLS+25SI+10 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
1.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
4.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
2.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 28, 2025, 8:00 AM UTC
  • Emulated Moto G Power with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 437 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.126 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Largest Contentful Paint element 4,050 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
Phase
% of LCP
Timing
TTFB
15%
600 ms
Load Delay
43%
1,750 ms
Load Time
10%
390 ms
Render Delay
32%
1,310 ms
Reduce unused CSS Potential savings of 70 KiB
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.LCPFCP
URL
Transfer Size
Potential Savings
lapeyre.fr
1st party
73.2 KiB
69.9 KiB
39.2 KiB
36.0 KiB
34.0 KiB
33.9 KiB
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
URL
lapeyre.fr
1st party
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
Unattributable
fabriqué en France par Lapeyre loading=
<img src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="fabriqué en France par Lapeyre loading=" lazy"="" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/catalogue/picto/02…" class="lazyfrz">
Existe Aussi sur mesure loading=
<img src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Existe Aussi sur mesure loading=" lazy"="" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/catalogue/picto/02…" class="lazyfrz">
Serve static assets with an efficient cache policy 41 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
lapeyre.fr
1st party
659 KiB
1h
19 KiB
30d
82 KiB
30d
42 KiB
30d
40 KiB
30d
40 KiB
30d
38 KiB
30d
35 KiB
30d
34 KiB
30d
33 KiB
30d
33 KiB
30d
33 KiB
30d
23 KiB
30d
23 KiB
30d
23 KiB
30d
22 KiB
30d
21 KiB
30d
12 KiB
30d
10 KiB
30d
10 KiB
30d
9 KiB
30d
8 KiB
30d
8 KiB
30d
8 KiB
30d
7 KiB
30d
7 KiB
30d
5 KiB
30d
4 KiB
30d
4 KiB
30d
4 KiB
30d
3 KiB
30d
3 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
1 KiB
30d
1 KiB
30d
1 KiB
30d
1 KiB
30d
1 KiB
30d
1 KiB
Properly size images Potential savings of 28 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
lapeyre.fr
1st party
42.7 KiB
27.5 KiB
txt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/Visuels/cra/service-co…" alt="txt" loading="lazy" width="1116" height="806" class="frz-img" onload="frzRemoveDimensionsTag(this)">
22.4 KiB
14.5 KiB
txt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/Visuels/cra/marque-up.…" alt="txt" loading="lazy" width="1116" height="684" class="frz-img" onload="frzRemoveDimensionsTag(this)">
20.3 KiB
13.1 KiB
Avoid an excessive DOM size 3,695 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
3,695
Maximum DOM Depth
div.modal-cta > a.btn2 > svg.svg > use
<use href="/wcsstore/LapeyreSAS/images/sprite.svg#chevron-right">
15
Maximum Child Elements
PRODUITS Promotions Menuiserie porte & fenêtre Cuisine & Electroménager Salle d…
<nav class="nav">
71
Initial server response time was short Root document took 490 ms
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.LCPFCP
URL
Time Spent
lapeyre.fr
1st party
490 ms
490 ms
Avoids enormous network payloads Total size was 748 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
lapeyre.fr
1st party
431.6 KiB
82.1 KiB
53.8 KiB
42.4 KiB
40.2 KiB
40.0 KiB
38.2 KiB
34.8 KiB
33.6 KiB
33.4 KiB
33.0 KiB
Avoid chaining critical requests 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 829.565 ms
Initial Navigation
- 17.798 ms, 5.54 KiB
JavaScript execution time 0.1 s
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.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
lapeyre.fr
1st party
572 ms
52 ms
2 ms
572 ms
52 ms
2 ms
Unattributable
100 ms
2 ms
0 ms
Unattributable
100 ms
2 ms
0 ms
Minimizes main-thread work 0.7 s
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 workTBT
Category
Time Spent
Style & Layout
310 ms
Other
143 ms
Parse HTML & CSS
129 ms
Script Evaluation
70 ms
Rendering
60 ms
Script Parsing & Compilation
4 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (25)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Warnings: A `<link rel=preconnect>` was found for "https://statics.lapeyre.fr" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
Avoid large layout shifts
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid long main-thread tasks
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
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.
Names and labels
Image elements do not have [alt] attributes
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.
Failing Elements
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
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.
Failing Elements
head > meta
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
These items highlight common accessibility best practices.
ARIA
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Failing Elements
Menu
<a class="h-burger js-nav-inter" aria-label="Menu" onclick="document.body.classList.add('navopen');">
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
EN SAVOIR PLUS
<a href="/c/marque" class="btn2 btn2-secondary">
TOUS NOS SERVICES
<a href="/c/les-services" class="btn2 btn2-tertiary">
JE ME LANCE
<a href="/c/projet" class="btn2 btn2-tertiary">
Nouveauté
<span class="thumbnail-postit">
These are opportunities to improve the legibility of your content.
Tables and lists
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Failing Elements
Promotions Menuiserie porte & fenêtre Cuisine & Electroménager Salle de bains &…
<ul class="nav-list">
Promotions
<a href="/toutes-les-promotions" class="nav-list-link gooddeal">
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (20)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
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.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Heading elements appear in a sequentially-descending order
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.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (31)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with `'strict-dynamic'` if necessary.
default-src
High
`'unsafe-inline'` allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
default-src
High
Avoid using plain URL schemes (http:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High
Avoid using plain URL schemes (https:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High
Passed audits (15)
Show Hide
Uses HTTPS
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.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
Legible text
100.00%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No browser errors logged to the console
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
No issues in the Issues panel in Chrome Devtools
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.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
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
Links are not crawlable
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
Uncrawlable Link
Menu
<a class="h-burger js-nav-inter" aria-label="Menu" onclick="document.body.classList.add('navopen');">
Continuer mes achats
<a onclick="javascript:$('#closeMinishop').click();" class="btn2 btn2-outline-dark">
Produits
<a class="h-nav-link js-nav-inter" onclick="document.body.classList.add('navopen');">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close" onclick="document.body.classList.remove('navopen');">
Menuiserie porte & fenêtre
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU3193775">
Cuisine & Electroménager
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU0001">
Salle de bains & WC
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU0002">
Escalier, Rampe & Main-courante
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU6740123">
Rangement, Dressing & Aménagement
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU3620685">
Jardin & Extérieur
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU0008">
Revêtement sol & mur
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU0007">
Équipement & Outil
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU3099822">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Fenêtre
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193777">
Porte-Fenêtre
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193779">
Verrière
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3620703">
Baie vitrée
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193783">
Velux & Lucarne
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193785">
Volet
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193787">
Porte d'entrée
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193789">
Porte d'intérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193791">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Modèle de cuisine
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU1555698">
Meuble de cuisine & Equipement
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3140528">
Plan de travail de cuisine
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687962">
Carrelage de cuisine & Crédence
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU4644304">
Evier & Robinetterie de cuisine
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687965">
Electroménager & lots
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687997">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Meuble de salle de bains & Rangement
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688001">
Douche
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688016">
Baignoire
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688337">
WC
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688348">
Vasque & Lavabo
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3249510">
Robinetterie de salle de bains & Colonne de douche
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688353">
Sèche-serviette
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3249512">
Carrelage de salle de bains
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688351">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Escalier
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3620709">
Rampe, poteau & Main courante
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU6784819">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Porte de placard
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3620687">
Dressing
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3620696">
Meuble de rangement
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU4850701">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Portail & Motorisation
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687925">
Clôture & Balustrade
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687932">
Porte de garage
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688197">
Store banne & Ombrage
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU4849498">
Terrasse & Escalier extérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688012">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Carrelage intérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687949">
Parquet & Sol d'intérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688033">
Terrasse & Extérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687954">
Lambris & Parement mural
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687956">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Plomberie
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3099824">
Motorisation & Electricité
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3099826">
Sécurité & Surveillance
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3099828">
Produit de pose & d'entretien
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3099830">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
> Paramétrer les cookies
<a class="ot-sdk-show-settings">
To appear in search results, crawlers need access to your app.
Content Best Practices
Image elements do not have [alt] attributes
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.
Failing Elements
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (8)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1 s
Page LoadsGood (≤ 2.5 s)95%Needs Improvement (2.5 s - 4 s)3%Poor (> 4 s)2%75th Percentile - 1 sCore Web Vital
Interaction to Next Paint (INP)
114 ms
Page LoadsGood (≤ 200 ms)85%Needs Improvement (200 ms - 500 ms)8%Poor (> 500 ms)6%75th Percentile - 114 msCore Web Vital
Cumulative Layout Shift (CLS)
0.01
Page LoadsGood (≤ 0.1)96%Needs Improvement (0.1 - 0.25)3%Poor (> 0.25)1%75th Percentile - 0.01Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
0.7 s
Page LoadsGood (≤ 1.8 s)94%Needs Improvement (1.8 s - 3 s)3%Poor (> 3 s)3%75th Percentile - 0.7 s 
Time to First Byte (TTFB)
0.4 s
Page LoadsGood (≤ 0.8 s)91%Needs Improvement (0.8 s - 1.8 s)6%Poor (> 1.8 s)3%75th Percentile - 0.4 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.2 s
Page LoadsGood (≤ 2.5 s)92%Needs Improvement (2.5 s - 4 s)5%Poor (> 4 s)3%75th Percentile - 1.2 sCore Web Vital
Interaction to Next Paint (INP)
102 ms
Page LoadsGood (≤ 200 ms)83%Needs Improvement (200 ms - 500 ms)10%Poor (> 500 ms)7%75th Percentile - 102 msCore Web Vital
Cumulative Layout Shift (CLS)
0.02
Page LoadsGood (≤ 0.1)92%Needs Improvement (0.1 - 0.25)4%Poor (> 0.25)4%75th Percentile - 0.02Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
0.8 s
Page LoadsGood (≤ 1.8 s)91%Needs Improvement (1.8 s - 3 s)6%Poor (> 3 s)4%75th Percentile - 0.8 s 
Time to First Byte (TTFB)
0.5 s
Page LoadsGood (≤ 0.8 s)81%Needs Improvement (0.8 s - 1.8 s)12%Poor (> 1.8 s)7%75th Percentile - 0.5 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
64 FCP+10LCP+25TBT+1CLS+25SI+4 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
1,310 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.016
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
2.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 28, 2025, 8:00 AM UTC
  • Emulated Desktop with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 316 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.126 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Reduce JavaScript execution time 2.2 s
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.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
lapeyre.fr
1st party
2,250 ms
1,547 ms
14 ms
1,068 ms
1,067 ms
1 ms
611 ms
56 ms
2 ms
467 ms
364 ms
5 ms
…6.19.0/otBannerSdk.js
(www.lapeyre.fr)
104 ms
60 ms
7 ms
Google Tag Manager
tag-manager
357 ms
310 ms
18 ms
/gtm.js?id=GTM-KPB43N
(www.googletagmanager.com)
246 ms
207 ms
10 ms
/gtag/js?id=…
(www.googletagmanager.com)
111 ms
103 ms
8 ms
Unattributable
323 ms
5 ms
0 ms
Unattributable
323 ms
5 ms
0 ms
sensefuel.com
233 ms
218 ms
11 ms
233 ms
218 ms
11 ms
AB Tasty
analytics
111 ms
103 ms
4 ms
111 ms
103 ms
4 ms
Minimize main-thread work 3.5 s
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 workTBT
Category
Time Spent
Script Evaluation
2,385 ms
Style & Layout
430 ms
Other
270 ms
Garbage Collection
188 ms
Rendering
101 ms
Parse HTML & CSS
88 ms
Script Parsing & Compilation
72 ms
Properly size images Potential savings of 302 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
lapeyre.fr
1st party
431.6 KiB
301.7 KiB
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
92.0 KiB
47.5 KiB
alt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Encar…" alt="alt" loading="lazy" width="588" height="766" class="frz-img" onload="frzRemoveDimensionsTag(this)">
39.6 KiB
31.8 KiB
alt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Encar…" alt="alt" loading="lazy" width="588" height="766" class="frz-img" onload="frzRemoveDimensionsTag(this)">
37.6 KiB
30.2 KiB
alt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Encar…" alt="alt" loading="lazy" width="588" height="766" class="frz-img" onload="frzRemoveDimensionsTag(this)">
32.8 KiB
26.3 KiB
alt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Encar…" alt="alt" loading="lazy" width="588" height="766" class="frz-img" onload="frzRemoveDimensionsTag(this)">
32.4 KiB
26.0 KiB
txt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/Visuels/cra/service-co…" alt="txt" loading="lazy" width="1116" height="806" class="frz-img" onload="frzRemoveDimensionsTag(this)">
22.4 KiB
21.2 KiB
txt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/Visuels/cra/service-po…" alt="txt" loading="lazy" width="1116" height="806" class="frz-img" onload="frzRemoveDimensionsTag(this)">
22.4 KiB
21.1 KiB
txt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/MEA/lapeyre/projet.png…" alt="txt" loading="lazy" width="1348" height="892" class="frz-img" onload="frzRemoveDimensionsTag(this)">
22.0 KiB
18.4 KiB
alt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Push/…" alt="alt" loading="lazy" class="" onload="frzRemoveDimensionsTag(this)">
29.5 KiB
15.4 KiB
txt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/Visuels/cra/marque-up.…" alt="txt" loading="lazy" width="1116" height="684" class="frz-img" onload="frzRemoveDimensionsTag(this)">
20.3 KiB
15.4 KiB
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
26.8 KiB
13.8 KiB
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
25.9 KiB
13.4 KiB
txt
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/Visuels/cra/service-at…" alt="txt" loading="lazy" width="1116" height="806" class="frz-img" onload="frzRemoveDimensionsTag(this)">
8.2 KiB
7.7 KiB
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
6.7 KiB
5.0 KiB
Velux Tout Confort Everfinish blanc à rotation GGU
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/catalogue/standard…" alt="Velux Tout Confort Everfinish blanc à rotation GGU" onerror="javascript:this.src='https://statics.lapeyre.fr/wcsstore/LapeyreSAS/images…" loading="lazy" class="frz-img thumbnail-visu-img" width="390" height="390" onload="frzRemoveDimensionsTag(this)">
7.8 KiB
4.3 KiB
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
5.5 KiB
4.1 KiB
Defer offscreen images Potential savings of 88 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
URL
Resource Size
Potential Savings
lapeyre.fr
1st party
92.0 KiB
85.1 KiB
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
92.0 KiB
85.1 KiB
Unattributable
2.8 KiB
2.8 KiB
chargement en cours
<img id="loaderShopSelectionDestockage" class="popin-selection-loader d-none" src="data:image/svg+xml;charset=utf-8,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.o…" alt="chargement en cours">
2.8 KiB
2.8 KiB
Reduce unused CSS Potential savings of 110 KiB
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.LCPFCP
URL
Transfer Size
Potential Savings
lapeyre.fr
1st party
73.2 KiB
69.2 KiB
39.2 KiB
35.3 KiB
34.0 KiB
33.9 KiB
sensefuel.com
28.4 KiB
24.5 KiB
28.4 KiB
24.5 KiB
Unattributable
18.8 KiB
15.9 KiB
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …
18.8 KiB
15.9 KiB
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
URL
lapeyre.fr
1st party
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
span.push-twix > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
span.push-twix > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
Unattributable
div.owl-item > a.univers-item > div.univers-visu > img
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQQAAAEECAMAAAD51ro4AAAAclBM…">
div.owl-item > a.univers-item > div.univers-visu > img
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQQAAAEECAMAAAD51ro4AAAAVFBM…">
fabriqué en France par Lapeyre loading=
<img src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="fabriqué en France par Lapeyre loading=" lazy"="" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/catalogue/picto/02…" class="lazyfrz">
Existe Aussi sur mesure loading=
<img src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Existe Aussi sur mesure loading=" lazy"="" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/catalogue/picto/02…" class="lazyfrz">
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
URL
Transfer Size
Potential Savings
lapeyre.fr
1st party
32.2 KiB
5.8 KiB
32.2 KiB
5.8 KiB
Enable text compression Potential savings of 4 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
URL
Transfer Size
Potential Savings
early-birds.fr
5.3 KiB
4.2 KiB
…5acaa2b…/identify
(api.early-birds.fr)
5.3 KiB
4.2 KiB
Serve static assets with an efficient cache policy 68 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
lapeyre.fr
1st party
973 KiB
1h
19 KiB
30d
93 KiB
…6.19.0/otBannerSdk.js
(www.lapeyre.fr)
30d
84 KiB
30d
58 KiB
30d
43 KiB
30d
40 KiB
30d
40 KiB
30d
38 KiB
30d
35 KiB
30d
33 KiB
30d
33 KiB
30d
33 KiB
30d
30 KiB
30d
27 KiB
30d
27 KiB
30d
23 KiB
30d
23 KiB
30d
23 KiB
30d
23 KiB
30d
23 KiB
30d
22 KiB
30d
21 KiB
30d
12 KiB
30d
10 KiB
30d
10 KiB
30d
9 KiB
30d
9 KiB
30d
8 KiB
30d
8 KiB
30d
8 KiB
30d
8 KiB
30d
7 KiB
30d
7 KiB
30d
7 KiB
30d
6 KiB
30d
5 KiB
30d
5 KiB
30d
5 KiB
30d
5 KiB
30d
4 KiB
30d
4 KiB
30d
4 KiB
30d
4 KiB
30d
4 KiB
30d
3 KiB
30d
3 KiB
30d
3 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
1 KiB
30d
1 KiB
30d
1 KiB
30d
1 KiB
30d
1 KiB
30d
1 KiB
…resources/blank.gif
(www.lapeyre.fr)
30d
1 KiB
sensefuel.com
217 KiB
5m
188 KiB
5m
29 KiB
sensefuel.live
57 KiB
/fonts/OpenSans-Light.woff2
(static.sensefuel.live)
30d
19 KiB
/fonts/OpenSans-Regular.woff2
(static.sensefuel.live)
30d
19 KiB
/fonts/OpenSans-Bold.woff2
(static.sensefuel.live)
30d
19 KiB
AB Tasty
analytics
3 KiB
/2c2667b….js
(try.abtasty.com)
30s
3 KiB
iGoDigital
analytics
2 KiB
/collect.js
(6417126.collect.igodigital.com)
None
2 KiB
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
URL
Potential Savings
sensefuel.live
240 ms
/fonts/OpenSans-Light.woff2
(static.sensefuel.live)
210 ms
/fonts/OpenSans-Bold.woff2
(static.sensefuel.live)
10 ms
/fonts/OpenSans-Regular.woff2
(static.sensefuel.live)
10 ms
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Source
lapeyre.fr
1st party
Avoid serving legacy JavaScript to modern browsers Potential savings of 40 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
iGoDigital
analytics
12.9 KiB
/collect.js
(6417126.collect.igodigital.com)
6.4 KiB
/collect.js:6:2
(6417126.collect.igodigital.com)
Array.isArray
/collect.js
(6417126.collect.igodigital.com)
6.4 KiB
/collect.js:6:2
(6417126.collect.igodigital.com)
Array.isArray
lapeyre.fr
1st party
12.8 KiB
6.4 KiB
Object.keys
…6.19.0/otBannerSdk.js
(www.lapeyre.fr)
6.3 KiB
Array.prototype.fill
0.1 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
Google Tag Manager
tag-manager
7.5 KiB
/gtm.js?id=GTM-KPB43N
(www.googletagmanager.com)
7.5 KiB
/gtm.js?id=GTM-KPB43N:13:46281
(www.googletagmanager.com)
Date.prototype.toJSON
sensefuel.com
7.1 KiB
7.1 KiB
Object.getOwnPropertyDescriptors
Object.values
AB Tasty
analytics
0.0 KiB
0.0 KiB
@babel/plugin-transform-classes
Reduce unused JavaScript Potential savings of 341 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.LCPFCP
URL
Transfer Size
Potential Savings
Google Tag Manager
tag-manager
371.1 KiB
158.1 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
94.7 KiB
57.9 KiB
/gtag/js?id=…
(www.googletagmanager.com)
137.2 KiB
53.2 KiB
/gtm.js?id=GTM-KPB43N
(www.googletagmanager.com)
139.2 KiB
47.1 KiB
sensefuel.com
187.7 KiB
97.1 KiB
187.7 KiB
97.1 KiB
lapeyre.fr
1st party
141.1 KiB
85.3 KiB
57.5 KiB
49.8 KiB
…6.19.0/otBannerSdk.js
(www.lapeyre.fr)
83.7 KiB
35.4 KiB
Avoid an excessive DOM size 4,059 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
4,059
Maximum DOM Depth
div.sf-searchline > div.sf-search-input-root > div.sf-searchbox > input.sf-search-input-field
<input type="search" class="sf-search-input-field" placeholder="" spellcheck="false">
17
Maximum Child Elements
PRODUITS Promotions Menuiserie porte & fenêtre Cuisine & Electroménager Salle d…
<nav class="nav">
71
Avoid long main-thread tasks 11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
lapeyre.fr
1st party
1,343 ms
1,345 ms
1,069 ms
2,554 ms
85 ms
2,453 ms
76 ms
874 ms
59 ms
436 ms
54 ms
sensefuel.com
215 ms
3,818 ms
136 ms
3,960 ms
79 ms
Google Tag Manager
tag-manager
207 ms
/gtag/js?id=…
(www.googletagmanager.com)
3,675 ms
107 ms
/gtm.js?id=GTM-KPB43N
(www.googletagmanager.com)
3,055 ms
100 ms
Unattributable
128 ms
Unattributable
629 ms
128 ms
AB Tasty
analytics
61 ms
3,614 ms
61 ms
Minimize third-party usage Third-party code blocked the main thread for 230 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
sensefuel.com
217 KiB
115 ms
188 KiB
115 ms
29 KiB
0 ms
Google Tag Manager
tag-manager
377 KiB
107 ms
/gtag/js?id=…
(www.googletagmanager.com)
138 KiB
57 ms
/gtm.js?id=GTM-KPB43N
(www.googletagmanager.com)
140 KiB
50 ms
/gtag/destination?id=…
(www.googletagmanager.com)
96 KiB
0 ms
2 KiB
0 ms
AB Tasty
analytics
86 KiB
11 ms
66 KiB
11 ms
/2c2667b….js
(try.abtasty.com)
3 KiB
0 ms
7 KiB
0 ms
/shared/me.0c0baf9….js
(try.abtasty.com)
4 KiB
0 ms
4 KiB
0 ms
/v1/geoip?weather=false
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
/v1/ua-parser
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
sensefuel.live
59 KiB
0 ms
/fonts/OpenSans-Light.woff2
(static.sensefuel.live)
19 KiB
0 ms
/fonts/OpenSans-Regular.woff2
(static.sensefuel.live)
19 KiB
0 ms
/fonts/OpenSans-Bold.woff2
(static.sensefuel.live)
19 KiB
0 ms
/create/239
(c.search.sensefuel.live)
1 KiB
0 ms
/transmit/239
(l.search.sensefuel.live)
1 KiB
0 ms
early-birds.fr
6 KiB
0 ms
…5acaa2b…/identify
(api.early-birds.fr)
6 KiB
0 ms
iGoDigital
analytics
2 KiB
0 ms
/collect.js
(6417126.collect.igodigital.com)
2 KiB
0 ms
Google Analytics
analytics
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
Optanon
consent-provider
0 KiB
0 ms
…geo/location
(geolocation.onetrust.com)
0 KiB
0 ms
Google/Doubleclick Ads
ad
0 KiB
0 ms
/ccm/collect?en=…
(pagead2.googlesyndication.com)
0 KiB
0 ms
Initial server response time was short Root document took 540 ms
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.LCPFCP
URL
Time Spent
lapeyre.fr
1st party
540 ms
540 ms
Avoid large layout shifts 3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
NOS OFFRES DU MOMENT
<section class="section">
0.016
Web font loaded
Web font loaded
A late network request adjusted the page layout
PRODUITS SERVICES INSPIRATION NOS MAGASINS CONFIGURATEURS MARQUE PROMOTIONS
<ul class="h-nav-list">
0.001
Web font loaded
Web font loaded
Web font loaded
A late network request adjusted the page layout
PRODUITS SERVICES INSPIRATION NOS MAGASINS CONFIGURATEURS MARQUE PROMOTIONS
<ul class="h-nav-list">
0.000
User Timing marks and measures 3 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
Name
Type
Start Time
Duration
frz_deferjs_registerScriptTags
Mark
1,416.86 ms
frz_deferjs_executing
Mark
1,418.86 ms
frz_deferjs_sync_done
Mark
3,048.57 ms
Avoids enormous network payloads Total size was 1,933 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
Google Tag Manager
tag-manager
374.4 KiB
/gtm.js?id=GTM-KPB43N
(www.googletagmanager.com)
140.3 KiB
/gtag/js?id=…
(www.googletagmanager.com)
138.3 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
95.8 KiB
lapeyre.fr
1st party
332.7 KiB
92.7 KiB
…6.19.0/otBannerSdk.js
(www.lapeyre.fr)
84.5 KiB
58.5 KiB
53.8 KiB
43.2 KiB
sensefuel.com
188.3 KiB
188.3 KiB
AB Tasty
analytics
66.1 KiB
66.1 KiB
Avoid chaining critical requests 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 934.915 ms
Initial Navigation
- 49.992 ms, 5.54 KiB
Largest Contentful Paint element 810 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
Phase
% of LCP
Timing
TTFB
20%
160 ms
Load Delay
40%
320 ms
Load Time
11%
90 ms
Render Delay
29%
240 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (14)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
Preconnect to required origins
Warnings: A `<link rel=preconnect>` was found for "https://statics.lapeyre.fr" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
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.
Names and labels
Image elements do not have [alt] attributes
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.
Failing Elements
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
span.push-twix > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
span.push-twix > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.univers-item > div.univers-visu > img
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQQAAAEECAMAAAD51ro4AAAAclBM…">
div.owl-item > a.univers-item > div.univers-visu > img
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQQAAAEECAMAAAD51ro4AAAAVFBM…">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQQAAAEECAMAAAD51ro4AAAARVBM…" class="frz-img " width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
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.
Failing Elements
head > meta
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
item
<button role="button" aria-label="item" class="owl-dot">
div.owl-stage-outer > div.owl-stage > div.owl-item > a.push-twix
<a href="/c/h/conditions-promotion" target="_blank" class="push-twix">
item
<button role="button" aria-label="item" class="owl-dot active">
div.owl-stage-outer > div.owl-stage > div.owl-item > a.push-twix
<a href="/c/h/conditions-promotion" target="_blank" class="push-twix">
item
<button role="button" aria-label="item" class="owl-dot">
div.owl-stage-outer > div.owl-stage > div.owl-item > a.push-twix
<a href="/c/h/conditions-promotion" target="_blank" class="push-twix">
These items highlight common accessibility best practices.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
EN SAVOIR PLUS
<a href="/c/marque" class="btn2 btn2-secondary">
TOUS NOS SERVICES
<a href="/c/les-services" class="btn2 btn2-tertiary">
JE ME LANCE
<a href="/c/projet" class="btn2 btn2-tertiary">
Nouveauté
<span class="thumbnail-postit">
Promotions
<a href="/toutes-les-promotions" class="f-nav-link gooddeal">
Fabrication Française Dans nos usines Lapeyre Pose par un pro Un artisan certif…
<footer class="footer" role="contentinfo">
Tout accepter et fermer
<button id="onetrust-accept-btn-handler">
These are opportunities to improve the legibility of your content.
Tables and lists
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Failing Elements
Promotions Menuiserie porte & fenêtre Cuisine & Electroménager Salle de bains &…
<ul class="nav-list">
Promotions
<a href="/toutes-les-promotions" class="nav-list-link gooddeal">
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Navigation
Some elements have a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Failing Elements
Continuer sans accepter
<button class="onetrust-close-btn-handler banner-close-button" tabindex="1">
These are opportunities to improve keyboard navigation in your application.
ARIA
Uses ARIA roles on incompatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Failing Elements
next/prev
<button type="button" role="presentation" aria-label="next/prev" class="owl-next">
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (22)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
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.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
Heading elements appear in a sequentially-descending order
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.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (27)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
lapeyre.fr
1st party
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Browser errors were logged to the console
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
Source
Description
lapeyre.fr
1st party
failed to evaluate i18n bundle; url=/wcsstore/LapeyreSAS/nls/fr-fr/StoreText.js SyntaxError: Unexpected token ')'
    at eval (eval at e (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:35526), <anonymous>:3:345)
    at Object.e [as load] (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:35972)
    at https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:39467
    at d (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47241)
    at l (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47028)
    at resolve.callback (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47832)
    at d (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47455)
    at l (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47028)
    at resolve.callback (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47832)
    at https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:41227
failed to evaluate i18n bundle; url=/wcsstore/LapeyreSAS/nls/fr/StoreText.js SyntaxError: Unexpected token ')'
    at eval (eval at e (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:35526), <anonymous>:3:345)
    at Object.e [as load] (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:35972)
    at https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:39467
    at d (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47241)
    at l (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47028)
    at resolve.callback (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47832)
    at d (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47455)
    at l (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47028)
    at resolve.callback (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47832)
    at https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:41227
failed to evaluate i18n bundle; url=/wcsstore/LapeyreSAS/nls/StoreText.js SyntaxError: Unexpected token ')'
    at eval (eval at e (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:35526), <anonymous>:3:345)
    at Object.e [as load] (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:35972)
    at https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:39467
    at d (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47241)
    at l (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47028)
    at resolve.callback (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47832)
    at d (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47455)
    at l (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47028)
    at resolve.callback (https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:47832)
    at https://www.lapeyre.fr/wcsstore/dojo116/dojo/dojo.js?frz-v=196:1:41227
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Bootstrap
4.0.0-beta
jQuery
3.5.1
Dojo
1.16.0 (NaN)
core-js
core-js-global@3.24.0
User Experience
Prevents users from pasting into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Failing Elements
div.sf-searchline > div.sf-search-input-root > div.sf-searchbox > input.sf-search-input-field
<input type="search" class="sf-search-input-field" placeholder="" spellcheck="false">
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with `'strict-dynamic'` if necessary.
default-src
High
`'unsafe-inline'` allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
default-src
High
Avoid using plain URL schemes (http:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High
Avoid using plain URL schemes (https:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High
Passed audits (11)
Show Hide
Uses HTTPS
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.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
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.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
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
Links are not crawlable
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
Uncrawlable Link
<a class="h-burger js-nav-inter" aria-label="Menu" onclick="document.body.classList.add('navopen');">
Continuer mes achats
<a onclick="javascript:$('#closeMinishop').click();" class="btn2 btn2-outline-dark">
PRODUITS
<a class="h-nav-link js-nav-inter" onclick="document.body.classList.add('navopen');">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close" onclick="document.body.classList.remove('navopen');">
Menuiserie porte & fenêtre
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU3193775">
Cuisine & Electroménager
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU0001">
Salle de bains & WC
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU0002">
Escalier, Rampe & Main-courante
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU6740123">
Rangement, Dressing & Aménagement
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU3620685">
Jardin & Extérieur
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU0008">
Revêtement sol & mur
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU0007">
Équipement & Outil
<a class="nav-list-link nav-list-inter js-nav2-inter" data-univers="CCU3099822">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Fenêtre
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193777">
Porte-Fenêtre
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193779">
Verrière
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3620703">
Baie vitrée
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193783">
Velux & Lucarne
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193785">
Volet
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193787">
Porte d'entrée
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193789">
Porte d'intérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3193791">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Modèle de cuisine
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU1555698">
Meuble de cuisine & Equipement
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3140528">
Plan de travail de cuisine
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687962">
Carrelage de cuisine & Crédence
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU4644304">
Evier & Robinetterie de cuisine
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687965">
Electroménager & lots
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687997">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Meuble de salle de bains & Rangement
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688001">
Douche
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688016">
Baignoire
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688337">
WC
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688348">
Vasque & Lavabo
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3249510">
Robinetterie de salle de bains & Colonne de douche
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688353">
Sèche-serviette
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3249512">
Carrelage de salle de bains
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688351">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Escalier
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3620709">
Rampe, poteau & Main courante
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU6784819">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Porte de placard
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3620687">
Dressing
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3620696">
Meuble de rangement
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU4850701">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Portail & Motorisation
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687925">
Clôture & Balustrade
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687932">
Porte de garage
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688197">
Store banne & Ombrage
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU4849498">
Terrasse & Escalier extérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688012">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Carrelage intérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687949">
Parquet & Sol d'intérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU688033">
Terrasse & Extérieur
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687954">
Lambris & Parement mural
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU687956">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-1">
Plomberie
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3099824">
Motorisation & Electricité
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3099826">
Sécurité & Surveillance
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3099828">
Produit de pose & d'entretien
<a class="nav-list-link nav-list-inter js-nav3-inter" data-famille="SCU3099830">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
nav.nav > div.nav-i > header.nav-header > a.nav-close
<a class="nav-close">
nav.nav > div.nav-i > header.nav-header > a.nav-back
<a class="nav-back nav-back-2">
Paramétrer les cookies
<a class="ot-sdk-show-settings">
To appear in search results, crawlers need access to your app.
Content Best Practices
Image elements do not have [alt] attributes
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.
Failing Elements
section.hero-img-section > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
span.push-twix > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
span.push-twix > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.push-twix > picture > img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/OP/2025/OP02/Heade…">
div.owl-item > a.univers-item > div.univers-visu > img
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQQAAAEECAMAAAD51ro4AAAAclBM…">
div.owl-item > a.univers-item > div.univers-visu > img
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQQAAAEECAMAAAD51ro4AAAAVFBM…">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQQAAAEECAMAAAD51ro4AAAARVBM…" class="frz-img " width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
div.owl-item > a.univers-item > div.univers-visu > img.frz-img
<img src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" data-frz-src="https://www.lapeyre.fr/fstrz/r/s/statics.lapeyre.fr/img/contrib/categories…" class="frz-img lazyloaded" width="260" height="260" onload="frzRemoveDimensionsTag(this)">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (8)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.