Skip to content
Audit Complete

Results for https://ulule.com

Visit site
Spain Spain · Madrid Completed: Apr 22, 2026 23:08 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C71

Site Health

Score: 71 / 100

Based on 8 categories, 0 sections

Room to improve — your 23.0s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Contentful · 86 peers
You 71
·
Avg 73
At average
0 50 100
Better than 11% of Contentful sites See full Contentful benchmark →
Adobe Fonts · 229 peers
You 71
·
Avg 73
At average
0 50 100
Better than 18% of Adobe Fonts sites See full Adobe Fonts benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

Cookie 'SERVERID' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security
3

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
4

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
5

Page weighs 7.4 MB (4.0 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fulule.com)](https://beavercheck.com/results/dd2bd4f0-bad4-4c27-80f9-82757cd561e9)
<a href="https://beavercheck.com/results/dd2bd4f0-bad4-4c27-80f9-82757cd561e9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fulule.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fulule.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 23.0s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

4 security gaps detected — browsers may warn visitors about your site.
Your LCP is 23.0s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~28%.

Speed (2)

Page takes 23.0s to load

+12% bounce

Users abandon at ~3s — you're 20.5s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 672ms

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€340 investment → €0.93/month returns + EUR 500,000 risk avoided

Payback period: > 2 years First-year ROI: -97%

Investment

€340

4h · 5 findings

Monthly returns

€0.93 /mo

~€11 / year

  • Bandwidth savings €0.93

Regulatory risk avoided

EUR 500,000

if kept compliant

  • EAA EUR 500,000

€170 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€340

4.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€170 4 fixes in ~120 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€41,668 / month at risk

~€500,011 / year if left unfixed

Compliance Risk

€500,000

EAA
  • No <main> landmark found
    EAA: EUR 1,000 – EUR 500,000
  • 5 of 5 <nav> elements are unlabeled
    EAA: EUR 1,000 – EUR 500,000
  • Skip navigation link is missing (WCAG 2.4.1)
    EAA: EUR 1,000 – EUR 500,000

+3 more

Bandwidth Waste

€0.93 /mo

12567.0 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.3 MB per page load
    Saves €0.93/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

44
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
72
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.32 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

23.02 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

672 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

7.90 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

23.42 s

Detailed Report

Audit breakdown by category with detailed findings.

44

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Container@3x div.ywBngKLG > div.ywBngKL2 > div.ywBngKLD > img.ywBngKLF
/guty4ttb9vho/2tOiWLnoTqtZdMFLT1GVmj/dc4eb2ef3cfbff5ccf83...577.5 KiB523.5 KiB
INCONTOURNABLE ROUEN, balades & découvertes a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/f99e55731ca62a810c15c5c6876a1401ca82dcee/thumbna...323.0 KiB296.4 KiB
⚜️Les Messagers des Étoiles ✨ a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/feb139ee44305fcd3ca7351b0b2f7f9a3616e9d7/thumbna...232.2 KiB205.6 KiB
Explore Kyrgyzstan 2nd Edition - Self-drive Guide a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/2eeaea899fdf86724c731155350be352d16e70e7/thumbna...285.0 KiB200.1 KiB
Out Soon: 1992 - 2008 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/992498caf7204eee6969e9e0993313f6e3564b4e/thumbna...179.2 KiB152.6 KiB
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/158/048/407/9/ab75776436af6d7bb261d836fcaa83d7.png160.3 KiB127.5 KiB
media.ulule.com/tags/cta/156/927/311/3/8c8ff5576558bb45cbc5ca979d96ca42.png182.6 KiB125.8 KiB
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/cta-role.png138.9 KiB85.2 KiB
media.ulule.com/tags/cta/156/900/665/1/2b70c78a08715b4a3b965e7c7941cb1f.png111.7 KiB78.8 KiB
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/161/046/749/8/8061847bfd7d1fa442dc55efae6fb8af.jpg133.6 KiB76.3 KiB
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/158/473/172/9/11ae6849f4730fbae6ddc572108472b2.png91.2 KiB58.3 KiB
div#axeptio_overlay > div.sc-gVgoRu > button#axeptio_main_button > img div#axeptio_overlay > div.sc-gVgoRu > button#axeptio_main_button > img
/2021/04/04679a11-4c38-4bd2-a8a6-708ab1329e15.png?auto=fo...5.0 KiB4.5 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-2-IMG
nodeLabel: ⚜️Les Messagers des Étoiles ✨
path: 1,HTML,1,BODY,13,DIV,3,DIV,2,SECTION,2,DIV,1,DIV,0,DIV,0,DIV,0,A,0,DIV,0,DIV,0,IMG
selector: a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
snippet: <img alt="⚜️Les Messagers des Étoiles ✨" loading="lazy" class="ykwPWD1K" srcset="https://img-cache.ulule.com/display/feb139ee44305fcd3ca7351b0b2f7f9a3616e9…" src="https://img-cache.ulule.com/display/feb139ee44305fcd3ca7351b0b2f7f9a3616e9…">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 806 ms
URLTime Spent
ulule.com/806 ms
www.ulule.com/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.3 s
Other1.3 s
Style & Layout680 ms
Rendering496 ms
Script Parsing & Compilation287 ms
Garbage Collection77 ms
Parse HTML & CSS48 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/cta-role.png
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/163/666/340/0/e1164d9edee2faf56663a64936d5b7c1.jpg
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/158/473/172/9/11ae6849f4730fbae6ddc572108472b2.png
Container@3x div.ywBngKLG > div.ywBngKL2 > div.ywBngKLD > img.ywBngKLF
/guty4ttb9vho/2tOiWLnoTqtZdMFLT1GVmj/dc4eb2ef3cfbff5ccf83...
div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img
/2021/03/Cookies 1B.png?auto=format&fit=crop&w=170&h=auto...
div#axeptio_overlay > div.sc-gVgoRu > button#axeptio_main_button > img div#axeptio_overlay > div.sc-gVgoRu > button#axeptio_main_button > img
/2021/04/04679a11-4c38-4bd2-a8a6-708ab1329e15.png?auto=fo...

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

Layout shift culprits
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
User Timing marks and measures 8 user timings
Avoid long main-thread tasks 16 long tasks found
Avoid non-composited animations 7 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 50 ms
Server Backend Latencies 100 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 140 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
72

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.yFtv2XoH > section.yFtv2XoQ > nav.yFtv2Xo4 > button.yISLuFS8 div.yFtv2XoH > section.yFtv2XoQ > nav.yFtv2Xo4 > button.yISLuFS8
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J
div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English Français Español Italiano Nederlands div.yqWWT5Y1 > div.ybW5ux3 > div.ybhkXym > select
$ (USD) € (EUR) £ (GBP) kr (DKK) kr (NOK) $ (AUD) $ (CAD) fr. (CHF) kr (SEK) $ … div.yqWWT5Y1 > div.ybW5ux3 > div.ybhkXym > select

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.yFtv2Xo7 > div.yFtv2XoH > section.yFtv2XoQ > a.yWlR9E2 nav.yFtv2Xo7 > div.yFtv2XoH > section.yFtv2XoQ > a.yWlR9E2

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OK! div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_acceptAll
TWINKLE EDITIONS a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€12,033 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
D-15 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
OUNTRAVELA PUBLISHING a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
200 / 100 div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1
D-34 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
AFTERCLUB.BE a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
561 / 500 div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1
H-23 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
DOROTHÉE PIATEK a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€4,824 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
D-32 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
SEE ALL PROJECTS div.yJvPGO9 > section.yJvPGO93 > a.yhxEDjC > button.yw80WrDU
SEE ALL CHANNELS div.yJvPGO9 > section.yJvPGO93 > a.yhxEDjC > button.yw80WrDU
SEE ALL CALLS FOR PROPOSALS div.yJvPGO9 > section.yJvPGO93 > a.yhxEDjC > button.yw80WrDU
Language and site currency footer.yFQ85FB1 > div.yqWWT5YE > div.yqWWT5Y1 > p.yNg1KOr9M

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Help and resources div.yqWWT5YB > section.yfqtpdS1 > label.ysnXvh91 > h3.yNg1KOr9O

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ongoing Lutte contre la précarité alimentaire chez les jeunes de 16 à 25 ans … div#__next > div.yJvPGO9 > section.yJvPGO93 > ul.yqMj87a

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ongoing Lutte contre la précarité alimentaire chez les jeunes de 16 à 25 ans … ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Pour révéler, célébrer et récompenser les talents qui perpétuent l’exc… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Accompagner les porteurs de projet engagés dans la transition énergéti… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Soutien de projets sur les thématiques du bien vieillir, de l’aide aux… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Les hommes et les femmes qui œuvrent pour une société plus inclusive e… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Des projets de nouvelles lignes aériennes élaborées et gérées localeme… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
No, thanks div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_dismiss
I want to choose div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_configure
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Uncaught Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Search nav#search-form > form.ygYwA3Wc > div.ygYwA3WZ > a.yIdeCPc2

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

84
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
79
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.11 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.14 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

6 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.005

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.87 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.00 s

Detailed Report

Audit breakdown by category with detailed findings.

84

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/156/927/311/3/8c8ff5576558bb45cbc5ca979d96ca42.png182.6 KiB164.1 KiB
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/158/048/407/9/ab75776436af6d7bb261d836fcaa83d7.png160.3 KiB144.6 KiB
div.ywBngKLG > div.ywBngKL2 > div.ywBngKLD > img.ywBngKLF div.ywBngKLG > div.ywBngKL2 > div.ywBngKLD > img.ywBngKLF
/guty4ttb9vho/3nMpi1hc3u06iqP7Elfu85/c06f62939748e22e02ec...153.7 KiB123.2 KiB
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/161/046/749/8/8061847bfd7d1fa442dc55efae6fb8af.jpg133.6 KiB114.9 KiB
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/156/900/665/1/2b70c78a08715b4a3b965e7c7941cb1f.png111.7 KiB95.9 KiB
media.ulule.com/tags/cta/cta-on-hp-scd-hd.jpg96.8 KiB79.3 KiB
Kookboek "Totally Nuts about Nuts"🌰 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/c9c8c67d6c02f272bfe74acc05719581d02f0d33/thumbna...84.0 KiB77.9 KiB
media.ulule.com/tags/cta/158/473/172/9/11ae6849f4730fbae6ddc572108472b2.png91.2 KiB75.4 KiB
🍁 Astres, Spectres et Chanterelles : cosy romantasy 🍄‍🟫 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/459a03da045b19e794257efe8949ab61de90f90b/thumbna...75.8 KiB69.7 KiB
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/sampik.png72.9 KiB55.9 KiB
INCONTOURNABLE ROUEN, balades & découvertes a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/e46fd56b9079708aa467c30b51555632ff5dcdb7/thumbna...61.3 KiB55.2 KiB
Operation partner image a.yzFhXihB > picture.yqtX2RD1 > div.ybWyyJ5 > img.yMQwVjj
/guty4ttb9vho/6okvFrv8SDZoO43oqweGoO/04f6090654099f47af81...57.3 KiB49.0 KiB
⚜️Les Messagers des Étoiles ✨ a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/96334f4ea959ceed8fd750eb065d18070b4e5a8b/thumbna...52.6 KiB46.5 KiB
Operation partner image a.yzFhXihB > picture.yqtX2RD1 > div.ybWyyJ5 > img.yMQwVjj
/guty4ttb9vho/XY8THwM32jcDFrDlYAgZo/4c4fc64031216ac1bec46...54.3 KiB46.1 KiB
Operation partner image a.yzFhXihB > picture.yqtX2RD1 > div.ybWyyJ5 > img.yMQwVjj
/guty4ttb9vho/MKRgkz6Hv16GeRIBbVCxq/e48a2edf6d3625a8b9775...53.9 KiB45.7 KiB
Love Love Magazine #10 - Obsession a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/f938361d27364004ee9c59ff632e7ca1450baf3a/thumbna...46.4 KiB40.3 KiB
Operation partner image a.yzFhXihB > picture.yqtX2RD1 > div.ybWyyJ5 > img.yMQwVjj
/guty4ttb9vho/5O9qVsPwF0nqepBmzR4ki0/1c4e852fdf808ae696c8...46.7 KiB38.4 KiB
Operation partner image a.yzFhXihB > picture.yqtX2RD1 > div.ybWyyJ5 > img.yMQwVjj
/guty4ttb9vho/6UisYZHBIQ01hI3WhelaVO/a10358ca8ae17cdcaf80...43.6 KiB35.4 KiB
Writing(with)plants - the care(work)book a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/db9efc1d1abd838e2be29e626483394496f221dc/thumbna...38.3 KiB32.2 KiB
Operation partner image a.yzFhXihB > picture.yqtX2RD1 > div.ybWyyJ5 > img.yMQwVjj
/guty4ttb9vho/4bMIQBhrCj0oy3XBshlJPZ/469547ca0a2ef30e68d1...38.0 KiB29.7 KiB
Out Soon: 1992 - 2008 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/e36cae982c5766efcae5f313b880302c7ccd15fc/thumbna...33.5 KiB27.4 KiB
Women eLife magazine féminin ouvert sur le monde a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/5fb98e480256678b37417b041e0b575235faac72/thumbna...25.4 KiB19.3 KiB
EFENDIM a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/7438d9b33b921230c993ff3af0283d19dc7fbcaa/thumbna...24.1 KiB18.0 KiB
Once Upon a Time... Moana Pozzi a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1T > img.ykwPWD1K
/display/8a3e5c4c5f4ef5c3e64f7e60495d9c8a88da88d1/thumbna...23.9 KiB17.8 KiB
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/163/666/340/0/e1164d9edee2faf56663a64936d5b7c1.jpg27.1 KiB14.6 KiB
div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img
/2021/03/Cookies 1B.png?auto=format&fit=crop&w=170&h=auto...7.9 KiB4.7 KiB
div#axeptio_overlay > div.sc-gVgoRu > button#axeptio_main_button > img div#axeptio_overlay > div.sc-gVgoRu > button#axeptio_main_button > img
/2021/04/04679a11-4c38-4bd2-a8a6-708ab1329e15.png?auto=fo...4.2 KiB4.0 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 251 ms
URLTime Spent
ulule.com/251 ms
www.ulule.com/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/156/927/311/3/8c8ff5576558bb45cbc5ca979d96ca42.png
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/156/900/665/1/2b70c78a08715b4a3b965e7c7941cb1f.png
ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6 ul.yhq1Q761 > li > a.yjFrCHo > img.yjFrCHo6
media.ulule.com/tags/cta/sampik.png
div.ywBngKLG > div.ywBngKL2 > div.ywBngKLD > img.ywBngKLF div.ywBngKLG > div.ywBngKL2 > div.ywBngKLD > img.ywBngKLF
/guty4ttb9vho/3nMpi1hc3u06iqP7Elfu85/c06f62939748e22e02ec...
div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img div > div.sc-fodVek > div.sc-fFucqa > img.Illustration__Img
/2021/03/Cookies 1B.png?auto=format&fit=crop&w=170&h=auto...
div#axeptio_overlay > div.sc-gVgoRu > button#axeptio_main_button > img div#axeptio_overlay > div.sc-gVgoRu > button#axeptio_main_button > img
/2021/04/04679a11-4c38-4bd2-a8a6-708ab1329e15.png?auto=fo...

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

Layout shift culprits
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 60 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
User Timing marks and measures 8 user timings
JavaScript execution time 0.5 s
Minimizes main-thread work 1.5 s
Avoid long main-thread tasks 1 long task found
Avoid non-composited animations 7 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 50 ms
Server Backend Latencies 90 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 120 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
79

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J
div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > button.ybmTWUm
div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J
div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J div.yeS1LGwF > div.yeS1LGwE > div.yeS1LGwI > button.yQIvc4J

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OK! div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_acceptAll
TWINKLE EDITIONS a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€12,033 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
D-15 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
OUNTRAVELA PUBLISHING a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
200 / 100 div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1
D-34 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
AFTERCLUB.BE a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
561 / 500 div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1
H-23 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
DOROTHÉE PIATEK a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€4,824 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
D-32 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
PULSE ÉDITIONS a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
185 / 300 div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1
FOUR EYES EDITIONS a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€7,507 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
D-16 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
LE PRINTEMPS DES SONNEURS a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
522 / 125 div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1
Extension a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
THE NUTTY FARMER a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€905 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
D-6 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
PATRICK GORGEON a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€312 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
D-8 a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1W > div.ykwPWD17
LOVE LOVE MAGAZINE a.ybRczrN8 > div.ybRczrN8 > div.ykwPWD1V > div.yQmnfbSJI
€802 div.ykwPWD1W > div.ykwPWD17 > div.yQ7rHNU1 > span.yihFAe4
SEE ALL PROJECTS div.yJvPGO9 > section.yJvPGO93 > a.yhxEDjC > button.yw80WrDU
SEE ALL CHANNELS div.yJvPGO9 > section.yJvPGO93 > a.yhxEDjC > button.yw80WrDU
SEE ALL CALLS FOR PROPOSALS div.yJvPGO9 > section.yJvPGO93 > a.yhxEDjC > button.yw80WrDU
Language and site currency footer.yFQ85FB1 > div.yqWWT5YE > div.yqWWT5Y1 > p.yNg1KOr9M

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Help and resources div.yqWWT5YB > section.yfqtpdS1 > label.ysnXvh91 > h3.yNg1KOr9O

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ongoing Lutte contre la précarité alimentaire chez les jeunes de 16 à 25 ans … div#__next > div.yJvPGO9 > section.yJvPGO93 > ul.yqMj87a

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ongoing Lutte contre la précarité alimentaire chez les jeunes de 16 à 25 ans … ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Pour révéler, célébrer et récompenser les talents qui perpétuent l’exc… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Accompagner les porteurs de projet engagés dans la transition énergéti… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Soutien de projets sur les thématiques du bien vieillir, de l’aide aux… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Les hommes et les femmes qui œuvrent pour une société plus inclusive e… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li
Ongoing Des projets de nouvelles lignes aériennes élaborées et gérées localeme… ul.yqMj87a > div.yeS1LGwF > div.yzAPy2t > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
No, thanks div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_dismiss
I want to choose div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_configure
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Uncaught Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Search nav#search-form > form.ygYwA3Wc > div.ygYwA3WZ > a.yIdeCPc2

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV
li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV li > a.yjFrCHo > div.yjFrCHo1 > img.yDYOaVsV

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback