Skip to content
Audit Complete

Results for https://persee.fr

Visit site
FR · EUR (€) Applicable regulations: RGPD · ePrivacy Directive · EAA Dev cost: €80/hr How jurisdiction is detected

URL substituted: You submitted https://persee.fr but we scanned https://www.persee.fr instead — the HTTPS certificate on the submitted hostname didn't cover that name, so we retried on the www. variant

Spain Spain · Madrid Completed: Apr 22, 2026 22:52 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)
D69

Site Health

Score: 69 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

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.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

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

Liferay · 6 peers
You 69
·
Avg 73
At average
0 50 100
AlloyUI · 6 peers
You 69
·
Avg 73
At average
0 50 100

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

No Content-Security-Policy header found

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

Security › Content Security Policy
3

1 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
4

11 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
5

3 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

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%2Fpersee.fr)](https://beavercheck.com/results/1630058a-1e49-4581-9ba9-167feacc3123)
<a href="https://beavercheck.com/results/1630058a-1e49-4581-9ba9-167feacc3123"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpersee.fr" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fpersee.fr

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
3 accessibility issues exclude users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

1 critical 6 warning

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

Speed (1)

Page takes 16.7s to load

+12% bounce

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

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

Trust (1)

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 Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

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, …)

Navigation (3)

11 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

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

1 broken link(s) on the page

+2% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

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

Return on Investment

€440 investment → €0.79/month returns + EUR 120,500,000 risk avoided

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

Investment

€440

6h · 5 findings

Monthly returns

€0.79 /mo

~€9.54 / year

  • Bandwidth savings €0.79

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • RGPD EUR 20,000,000
  • EAA EUR 500,000

€80 — 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

€440

5.5 developer hours at €80/hr

Based on France rates (€80/hr)

Quick wins
€80 2 fixes in ~60 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

€10,041,667 / month at risk

~€120,500,010 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveRGPDEAA
  • No privacy policy link detected
    RGPD: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    RGPD: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    RGPD: EUR 10,000 – EUR 20,000,000

+10 more

Bandwidth Waste

€0.79 /mo

10729.9 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.1 MB per page load
    Saves €0.79/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.

54
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
64
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
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.

13.90 s

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

16.70 s

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

119 ms

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

0.000

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

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

20.13 s

Detailed Report

Audit breakdown by category with detailed findings.

54

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.

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
div.persee_content-nobox > div.persee_content > div.content > img div.persee_content-nobox > div.persee_content > div.content > img
/documents/10099/1595712/Bandeau_RA2024.png/fc2d5a89-5408...245.5 KiB214.2 KiB
  div.persee_content > div.content > header#header-banner > section#banner
/documents/10099/1609937/bandeau_versa/fe5e99f9-73fb-4b11...158.2 KiB123.8 KiB
Bluesky section#follow-us > p > a > img
/documents/10099/0/Bluesky_White.png/b483ef21-dbfc-4825-b...84.9 KiB84.8 KiB
div.content > p > a > img div.content > p > a > img
/documents/10099/1367650/ehess.png/a1fc2282-9b58-4d7c-8f5...59.8 KiB54.5 KiB
div.persee_content > div.content > a > img div.persee_content > div.content > a > img
/documents/10099/1367650/cbc.png/35c91685-2aae-4c3f-bb5c-...56.4 KiB51.4 KiB
div.content > p > a > img div.content > p > a > img
/documents/10099/1367650/cls.png/391a0243-e2d2-4591-806c-...48.1 KiB42.3 KiB
div.persee_content > div.content > p > img div.persee_content > div.content > p > img
/documents/10099/1595712/Bandeau_Keepers.png/d825d1ea-714...49.2 KiB29.2 KiB
X section#follow-us > p > a > img
/documents/10099/0/X_logo_white.png/a20e15fc-1439-472b-94...27.5 KiB27.3 KiB
CNRS section#partner > section#tutelles > a > img
www.persee.fr/static/LOGO_CNRS_BLEU.png18.6 KiB18.3 KiB
Ministère de l'éducation nationale, de l'enseignement supérieur et de la recher… section#partner > section#financeur > a > img
/documents/10099/505733/MENESR_logo_portail.png/e9ae2f42-...18.5 KiB12.7 KiB
persee.fr header#navi > section#site-title > a.logo > img
www.persee.fr/static/persee.png9.3 KiB4.6 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-1-SECTION
nodeLabel:  
path: 1,HTML,2,BODY,4,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,HEADER,0,SECTION
selector: div.persee_content > div.content > header#header-banner > section#banner
snippet: <section id="banner" style="background-image: url(&quot;/documents/10099/1609937/bandeau_versa/fe5e99f9-73fb…&quot;);">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.persee.fr/http/1.1
/persee-theme/css/aui.css?browserId=other&themeId=persee_...http/1.1
/html/css/main.css?browserId=other&themeId=persee_WAR_per...http/1.1
/html/portlet/asset_publisher/css/main.css?browserId=othe...http/1.1
/persee-search-portlet/webjars/font-awesome/7.0.0/css/fon...http/1.1
/persee-search-portlet/webjars/font-awesome/7.0.0/css/sol...http/1.1
/persee-search-portlet/webjars/font-awesome/7.0.0/css/bra...http/1.1
/html/portlet/journal/css/main.css?browserId=other&themeI...http/1.1
/html/js/barebone.jsp?browserId=other&themeId=persee_WAR_...http/1.1
/html/portlet/journal/js/main.js?browserId=other&minifier...http/1.1
/html/portlet/journal/js/navigation.js?browserId=other&mi...http/1.1
/persee-theme/css/main.css?browserId=other&themeId=persee...http/1.1
www.persee.fr/static/persee.pnghttp/1.1
www.persee.fr/persee-theme/images/skin/persee/picto/search-1.pnghttp/1.1
www.persee.fr/static/LOGO_CNRS_BLEU.pnghttp/1.1
/documents/10099/505733/ENS_2024-11/1a6cc584-1c59-4629-9c...http/1.1
/documents/10099/505733/MENESR_logo_portail.png/e9ae2f42-...http/1.1
/documents/10099/1595712/Bandeau_Keepers.png/d825d1ea-714...http/1.1
/documents/10099/1595712/Bandeau_RA2024.png/fc2d5a89-5408...http/1.1
www.persee.fr/persee-theme/images/picto/more-news-1.pnghttp/1.1
www.persee.fr/persee-theme/images/picto/more-news-alt-1.pnghttp/1.1
/documents/10099/1367650/cls.png/391a0243-e2d2-4591-806c-...http/1.1
/documents/10099/1367650/cbc.png/35c91685-2aae-4c3f-bb5c-...http/1.1
/documents/10099/1367650/ehess.png/a1fc2282-9b58-4d7c-8f5...http/1.1
/documents/10099/0/LinkedIn_white.png/4e038376-f4c3-4405-...http/1.1
/documents/10099/0/X_logo_white.png/a20e15fc-1439-472b-94...http/1.1
/documents/10099/0/Bluesky_White.png/b483ef21-dbfc-4825-b...http/1.1
www.persee.fr/persee-theme/images/skin/persee/picto/back2top-3.pnghttp/1.1
/persee-theme/js/main.js?browserId=other&minifierType=js&...http/1.1
/combo/?browserId=other&minifierType=&languageId=fr_FR&b=...http/1.1
www.persee.fr/persee-theme/images/onglet.pnghttp/1.1
www.persee.fr/persee-theme/images/trame.pnghttp/1.1
/documents/10099/1609937/bandeau_versa/fe5e99f9-73fb-4b11...http/1.1
www.persee.fr/persee-theme/images/skin/persee/picto/bullet-full-3.pnghttp/1.1
www.persee.fr/persee-theme/css/fonts/ens/BebasNeueBold-webfont.woff2http/1.1
/persee-search-portlet/webjars/font-awesome/7.0.0/webfont...http/1.1
www.persee.fr/persee-theme/css/fonts/ens/BebasNeueRegular-webfont.woff2http/1.1
/combo/?browserId=other&minifierType=&languageId=fr_FR&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=fr_FR&b=...http/1.1
/html/js/liferay/available_languages.jsp?browserId=other&...http/1.1
/combo/?browserId=other&minifierType=&languageId=fr_FR&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=fr_FR&b=...http/1.1
www.persee.fr/favicon.icohttp/1.1

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
value: No additional origins are good candidates for preconnecting

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.

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

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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

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
persee.fr header#navi > section#site-title > a.logo > img
www.persee.fr/static/persee.png
div.content > p > a > img div.content > p > a > img
/documents/10099/1367650/cls.png/391a0243-e2d2-4591-806c-...
div.content > p > a > img div.content > p > a > img
/documents/10099/1367650/ehess.png/a1fc2282-9b58-4d7c-8f5...
div.persee_content > div.content > a > img div.persee_content > div.content > a > img
/documents/10099/1367650/cbc.png/35c91685-2aae-4c3f-bb5c-...
div.persee_news > p > a.picto > img.default-picto div.persee_news > p > a.picto > img.default-picto
www.persee.fr/persee-theme/images/picto/more-news-1.png

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
Optimize viewport for mobile
User Timing marks and measures 5 user timings
JavaScript execution time 0.5 s
Minimizes main-thread work 1.2 s
Avoid long main-thread tasks 3 long tasks found
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 20 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 360 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
64

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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FR EN body.persee > header#sidebar
Informations Au sujet de persee.fr Votre collection sur persee.fr   Nous contac… div.persee_content-nobox > div.persee_content > div.content > footer#footer

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

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
Portail Persée body.persee > header#persee-headbar > a.a_css
alités div.portlet-body > div.persee_news > h3 > span.perseePrimary
en chiffres div.portlet-body > div#doc-count > h4.title > span.emphasis
nous ? div.persee_content-nobox > div.persee_content > h4.title > span.perseePrimary

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
info.persee.fr div.persee_content > div.content > p > a
info.persee.fr div.persee_content > div.content > p > a
Publications de l'EHESS div.persee_content > div.content > p > a
Les Jeux olympiques div.content > ul > li > a
Les origines des jeux olympiques mythes et réalités div.content > ul > li > a
Les jeux olympiques dans l'Antiquité div.content > ul > li > a
Jeux Olympiques : du signal universel à la pluralité des images div.content > ul > li > a
Jeux et enjeux olympiques div.content > ul > li > a
Chiffres clés et premières analyses des Jeux olympiques et paralympiques div.content > ul > li > a
Persée footer > footer#footer-small > section#copyright > a

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
Persée en chiffres div.portlet-borderless-container > div.portlet-body > div#doc-count > h4.title

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.persee_news > p > a.picto > img.default-picto div.persee_news > p > a.picto > img.default-picto

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
  div.content > header#header-banner > section#banner > a
div.portlet-body > div.persee_news > p > a.picto div.portlet-body > div.persee_news > p > a.picto
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content > div.content > p > a div.persee_content > div.content > p > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content-withpic > div.persee_content > div.content > a div.persee_content-withpic > div.persee_content > div.content > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content > div.content > p > a div.persee_content > div.content > p > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Au sujet de persee.fr div.content > footer#footer > section#information > a
Votre collection sur persee.fr div.content > footer#footer > section#information > a
Interopérabilité div.content > footer#footer > section#resources > a
Modèles documentaires div.content > footer#footer > section#resources > a
Statistiques de consultation div.content > footer#footer > section#resources > a
Kit logos div.content > footer#footer > section#resources > a
CGU div.content > footer#footer > section#misc > a
Mentions légales div.content > footer#footer > section#misc > a
Crédits div.content > footer#footer > section#misc > a
Politique d'archivage pérenne div.content > footer#footer > section#misc > a

These items highlight common accessibility best practices.

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

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Ministère de l'éducation nationale, de l'enseignement supérieur et de la recher… section#partner > section#financeur > a > img
/documents/10099/505733/MENESR_logo_portail.png/e9ae2f42-...200 x 177200 x 177300 x 266

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
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
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.persee_news > p > a.picto > img.default-picto div.persee_news > p > a.picto > img.default-picto

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

67
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
64
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
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.

2.44 s

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

3.53 s

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

0 ms

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

0.034

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

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

3.54 s

Detailed Report

Audit breakdown by category with detailed findings.

67

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.

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
div.persee_content-nobox > div.persee_content > div.content > img div.persee_content-nobox > div.persee_content > div.content > img
/documents/10099/1595712/Bandeau_RA2024.png/fc2d5a89-5408...245.5 KiB235.6 KiB
  div.persee_content > div.content > header#header-banner > section#banner
/documents/10099/1609937/bandeau_versa/fe5e99f9-73fb-4b11...158.2 KiB123.8 KiB
Bluesky section#follow-us > p > a > img
/documents/10099/0/Bluesky_White.png/b483ef21-dbfc-4825-b...84.9 KiB84.9 KiB
div.content > p > a > img div.content > p > a > img
/documents/10099/1367650/ehess.png/a1fc2282-9b58-4d7c-8f5...59.8 KiB54.5 KiB
div.persee_content > div.content > a > img div.persee_content > div.content > a > img
/documents/10099/1367650/cbc.png/35c91685-2aae-4c3f-bb5c-...56.4 KiB51.4 KiB
div.persee_content > div.content > p > img div.persee_content > div.content > p > img
/documents/10099/1595712/Bandeau_Keepers.png/d825d1ea-714...49.2 KiB42.9 KiB
div.content > p > a > img div.content > p > a > img
/documents/10099/1367650/cls.png/391a0243-e2d2-4591-806c-...48.1 KiB42.3 KiB
X section#follow-us > p > a > img
/documents/10099/0/X_logo_white.png/a20e15fc-1439-472b-94...27.5 KiB27.4 KiB
CNRS section#partner > section#tutelles > a > img
www.persee.fr/static/LOGO_CNRS_BLEU.png18.6 KiB18.5 KiB
Ministère de l'éducation nationale, de l'enseignement supérieur et de la recher… section#partner > section#financeur > a > img
/documents/10099/505733/MENESR_logo_portail.png/e9ae2f42-...18.5 KiB12.7 KiB
persee.fr header#navi > section#site-title > a.logo > img
www.persee.fr/static/persee.png9.3 KiB7.8 KiB
ENS Lyon section#partner > section#tutelles > a > img
/documents/10099/505733/ENS_2024-11/1a6cc584-1c59-4629-9c...4.2 KiB4.1 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-1-SECTION
nodeLabel:  
path: 1,HTML,2,BODY,4,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,HEADER,0,SECTION
selector: div.persee_content > div.content > header#header-banner > section#banner
snippet: <section id="banner" style="background-image: url(&quot;/documents/10099/1609937/bandeau_versa/fe5e99f9-73fb…&quot;);">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.persee.fr/http/1.1
/persee-theme/css/aui.css?browserId=other&themeId=persee_...http/1.1
/html/css/main.css?browserId=other&themeId=persee_WAR_per...http/1.1
/html/portlet/asset_publisher/css/main.css?browserId=othe...http/1.1
/persee-search-portlet/webjars/font-awesome/7.0.0/css/fon...http/1.1
/persee-search-portlet/webjars/font-awesome/7.0.0/css/sol...http/1.1
/persee-search-portlet/webjars/font-awesome/7.0.0/css/bra...http/1.1
/html/portlet/journal/css/main.css?browserId=other&themeI...http/1.1
/html/js/barebone.jsp?browserId=other&themeId=persee_WAR_...http/1.1
/html/portlet/journal/js/main.js?browserId=other&minifier...http/1.1
/html/portlet/journal/js/navigation.js?browserId=other&mi...http/1.1
/persee-theme/css/main.css?browserId=other&themeId=persee...http/1.1
www.persee.fr/static/persee.pnghttp/1.1
www.persee.fr/persee-theme/images/skin/persee/picto/search-1.pnghttp/1.1
www.persee.fr/static/LOGO_CNRS_BLEU.pnghttp/1.1
/documents/10099/505733/ENS_2024-11/1a6cc584-1c59-4629-9c...http/1.1
/documents/10099/505733/MENESR_logo_portail.png/e9ae2f42-...http/1.1
/documents/10099/1595712/Bandeau_Keepers.png/d825d1ea-714...http/1.1
/documents/10099/1595712/Bandeau_RA2024.png/fc2d5a89-5408...http/1.1
www.persee.fr/persee-theme/images/picto/more-news-1.pnghttp/1.1
www.persee.fr/persee-theme/images/picto/more-news-alt-1.pnghttp/1.1
/documents/10099/1367650/cls.png/391a0243-e2d2-4591-806c-...http/1.1
/documents/10099/1367650/cbc.png/35c91685-2aae-4c3f-bb5c-...http/1.1
/documents/10099/1367650/ehess.png/a1fc2282-9b58-4d7c-8f5...http/1.1
/documents/10099/0/LinkedIn_white.png/4e038376-f4c3-4405-...http/1.1
/documents/10099/0/X_logo_white.png/a20e15fc-1439-472b-94...http/1.1
/documents/10099/0/Bluesky_White.png/b483ef21-dbfc-4825-b...http/1.1
www.persee.fr/persee-theme/images/skin/persee/picto/back2top-3.pnghttp/1.1
/persee-theme/js/main.js?browserId=other&minifierType=js&...http/1.1
/combo/?browserId=other&minifierType=&languageId=fr_FR&b=...http/1.1
www.persee.fr/persee-theme/images/onglet.pnghttp/1.1
www.persee.fr/persee-theme/images/trame.pnghttp/1.1
/documents/10099/1609937/bandeau_versa/fe5e99f9-73fb-4b11...http/1.1
www.persee.fr/persee-theme/images/skin/persee/picto/bullet-full-3.pnghttp/1.1
www.persee.fr/persee-theme/css/fonts/ens/BebasNeueBold-webfont.woff2http/1.1
/persee-search-portlet/webjars/font-awesome/7.0.0/webfont...http/1.1
www.persee.fr/persee-theme/css/fonts/ens/BebasNeueRegular-webfont.woff2http/1.1
/combo/?browserId=other&minifierType=&languageId=fr_FR&b=...http/1.1
/combo/?browserId=other&minifierType=&languageId=fr_FR&b=...http/1.1
/html/js/liferay/available_languages.jsp?browserId=other&...http/1.1
/combo/?browserId=other&minifierType=&languageId=fr_FR&b=...http/1.1
www.persee.fr/favicon.icohttp/1.1

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
value: No additional origins are good candidates for preconnecting

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.

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

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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

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
persee.fr header#navi > section#site-title > a.logo > img
www.persee.fr/static/persee.png
div.content > p > a > img div.content > p > a > img
/documents/10099/1367650/cls.png/391a0243-e2d2-4591-806c-...
div.content > p > a > img div.content > p > a > img
/documents/10099/1367650/ehess.png/a1fc2282-9b58-4d7c-8f5...
div.persee_content > div.content > a > img div.persee_content > div.content > a > img
/documents/10099/1367650/cbc.png/35c91685-2aae-4c3f-bb5c-...
div.persee_news > p > a.picto > img.default-picto div.persee_news > p > a.picto > img.default-picto
www.persee.fr/persee-theme/images/picto/more-news-1.png

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
Optimize viewport for mobile
Max Potential First Input Delay 50 ms
User Timing marks and measures 5 user timings
JavaScript execution time 0.1 s
Minimizes main-thread work 0.3 s
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 300 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid long main-thread tasks
Avoid non-composited animations
64

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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FR EN body.persee > header#sidebar
Informations Au sujet de persee.fr Votre collection sur persee.fr   Nous contac… div.persee_content-nobox > div.persee_content > div.content > footer#footer

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

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
Portail Persée body.persee > header#persee-headbar > a.a_css
alités div.portlet-body > div.persee_news > h3 > span.perseePrimary
en chiffres div.portlet-body > div#doc-count > h4.title > span.emphasis
nous ? div.persee_content-nobox > div.persee_content > h4.title > span.perseePrimary

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
info.persee.fr div.persee_content > div.content > p > a
info.persee.fr div.persee_content > div.content > p > a
Publications de l'EHESS div.persee_content > div.content > p > a
Les Jeux olympiques div.content > ul > li > a
Les origines des jeux olympiques mythes et réalités div.content > ul > li > a
Les jeux olympiques dans l'Antiquité div.content > ul > li > a
Jeux Olympiques : du signal universel à la pluralité des images div.content > ul > li > a
Jeux et enjeux olympiques div.content > ul > li > a
Chiffres clés et premières analyses des Jeux olympiques et paralympiques div.content > ul > li > a
Persée footer > footer#footer-small > section#copyright > a

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
Persée en chiffres div.portlet-borderless-container > div.portlet-body > div#doc-count > h4.title

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.persee_news > p > a.picto > img.default-picto div.persee_news > p > a.picto > img.default-picto

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
  div.content > header#header-banner > section#banner > a
div.portlet-body > div.persee_news > p > a.picto div.portlet-body > div.persee_news > p > a.picto
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content > div.content > p > a div.persee_content > div.content > p > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content-withpic > div.persee_content > div.content > a div.persee_content-withpic > div.persee_content > div.content > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content > div.content > p > a div.persee_content > div.content > p > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Au sujet de persee.fr div.content > footer#footer > section#information > a
Votre collection sur persee.fr div.content > footer#footer > section#information > a
Interopérabilité div.content > footer#footer > section#resources > a
Modèles documentaires div.content > footer#footer > section#resources > a
Statistiques de consultation div.content > footer#footer > section#resources > a
Kit logos div.content > footer#footer > section#resources > a
CGU div.content > footer#footer > section#misc > a
Mentions légales div.content > footer#footer > section#misc > a
Crédits div.content > footer#footer > section#misc > a
Politique d'archivage pérenne div.content > footer#footer > section#misc > a

These items highlight common accessibility best practices.

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.persee_content-nobox > div.persee_content > div.content > img div.persee_content-nobox > div.persee_content > div.content > img
/documents/10099/1595712/Bandeau_RA2024.png/fc2d5a89-5408...290 x 209 (1.39)690 x 480 (1.44)
div.persee_content > div.content > p > img div.persee_content > div.content > p > img
/documents/10099/1595712/Bandeau_Keepers.png/d825d1ea-714...290 x 134 (2.16)670 x 300 (2.23)

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
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
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a
div.persee_content-withpic > div.persee_content > h4.title > a div.persee_content-withpic > div.persee_content > h4.title > a

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.persee_news > p > a.picto > img.default-picto div.persee_news > p > a.picto > img.default-picto

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