Lighthouse Report

There were issues affecting this run of Lighthouse:

The page may not be loading as expected because your test URL (https://www.anassekazib2022.fr/) was redirected to https://anassekazib2022.fr/mindex.php. Try testing the second URL directly.

Performance

First Contentful Paint

4.6 s

First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Speed Index

4.8 s

Speed Index shows how quickly the contents of a page are visibly populated. Learn more.

Largest Contentful Paint

Error!

Something went wrong with recording the trace over your page load. Please run Lighthouse again. (NO_LCP)

Time to Interactive

7.8 s

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

Total Blocking Time

20 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.

Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.

Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.

Serve images in next-gen formats

16.5 s

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL	Resource Size	Potential Savings
/img/anassemobile.png (anassekazib2022.fr)	3,134.0 KiB	2,712.9 KiB
/img/nosPropositions.png (anassekazib2022.fr)	513.7 KiB	450.0 KiB
/img/anasseRassemblement.jpg (anassekazib2022.fr)	188.0 KiB	65.2 KiB
/img/SoutenuParRPLongBlanc.png (anassekazib2022.fr)	85.3 KiB	39.4 KiB

Avoid multiple page redirects

1.93 s

Redirects introduce additional delays before the page can be loaded. Learn more.

URL	Time Spent
https://www.anassekazib2022.fr	1,100 ms
/mindex.php (anassekazib2022.fr)	830 ms
/mindex.php (anassekazib2022.fr)	0 ms

Remove unused JavaScript

1.51 s

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

URL	Transfer Size	Potential Savings
…config/110…?v=2.9.61&r=stable (connect.facebook.net)	86.7 KiB	68.3 KiB
/jquery-3.3.1.min.js (code.jquery.com)	29.8 KiB	22.4 KiB
/jquery-3.5.1.min.js (code.jquery.com)	30.4 KiB	21.3 KiB

Eliminate render-blocking resources

1.1 s

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL	Transfer Size	Potential Savings
/css/bootstrap.css (anassekazib2022.fr)	25.2 KiB	900 ms
/css/normalize.css (anassekazib2022.fr)	1.9 KiB	150 ms
/acd0307bf4.js (kit.fontawesome.com)	4.4 KiB	1,010 ms
/css?family=Roboto:300,400,500,700,900&display=swap (fonts.googleapis.com)	1.4 KiB	780 ms
/jquery-3.3.1.min.js (code.jquery.com)	29.8 KiB	1,510 ms
…umd/popper.min.js (cdnjs.cloudflare.com)	6.7 KiB	930 ms
…css/bootstrap.min.css (stackpath.bootstrapcdn.com)	24.9 KiB	1,290 ms
/jquery-3.5.1.min.js (code.jquery.com)	30.4 KiB	520 ms
…js/bootstrap.min.js (stackpath.bootstrapcdn.com)	15.3 KiB	320 ms

Properly size images

0.6 s

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

	URL	Resource Size	Potential Savings
	/img/SoutenuParRPLongBlanc.png (anassekazib2022.fr)	85.3 KiB	83.9 KiB
	/img/LogoAK2022-rouge.png (anassekazib2022.fr)	41.3 KiB	36.9 KiB

Remove unused CSS

0.3 s

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL	Transfer Size	Potential Savings
/css/bootstrap.css (anassekazib2022.fr)	25.2 KiB	23.9 KiB
…css/bootstrap.min.css (stackpath.bootstrapcdn.com)	24.9 KiB	23.7 KiB
/! Font Awesome Free 5.15.4 by @fontawesome - https://fontawesome.com * License - https://fonta...	12.0 KiB	12.0 KiB

Minify CSS

0.17 s

Minifying CSS files can reduce network payload sizes. Learn more.

URL	Transfer Size	Potential Savings
/css/bootstrap.css (anassekazib2022.fr)	25.2 KiB	4.7 KiB

Minify JavaScript

0.15 s

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL	Transfer Size	Potential Savings
/js/style.js (anassekazib2022.fr)	24.7 KiB	8.5 KiB

Preconnect to required origins

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Preload Largest Contentful Paint image

Preload the image used by the LCP element in order to improve your LCP time. Learn more.

Serve static assets with an efficient cache policy 19 resources found

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

URL	Cache TTL	Transfer Size
/img/anassemobile.png (anassekazib2022.fr)	15 m	3,138 KiB
/img/nosPropositions.png (anassekazib2022.fr)	15 m	515 KiB
/img/anasseRassemblement.jpg (anassekazib2022.fr)	15 m	188 KiB
/img/SoutenuParRPLongBlanc.png (anassekazib2022.fr)	15 m	86 KiB
/img/LogoAK2022-rouge.png (anassekazib2022.fr)	15 m	42 KiB
/css/bootstrap.css (anassekazib2022.fr)	15 m	25 KiB
/js/style.js (anassekazib2022.fr)	15 m	25 KiB
/css/style.css?v=1.4 (anassekazib2022.fr)	15 m	3 KiB
/css/normalize.css (anassekazib2022.fr)	15 m	2 KiB
/img/logo-lid-menu.png (anassekazib2022.fr)	15 m	2 KiB
/css/event.css (anassekazib2022.fr)	15 m	1 KiB
/css/layout.css?v=1.2 (anassekazib2022.fr)	15 m	1 KiB
/css/font.css (anassekazib2022.fr)	15 m	1 KiB
/js/scroll.js (anassekazib2022.fr)	15 m	1 KiB
/js/eventscript.js (anassekazib2022.fr)	15 m	0 KiB
…config/110…?v=2.9.61&r=stable (connect.facebook.net)	20 m	87 KiB
/en_US/fbevents.js (connect.facebook.net)	20 m	27 KiB
/videos/videoplayback.mp4 (anassekazib2022.fr)	1 h	4,531 KiB
/analytics.js (www.google-analytics.com)	2 h	20 KiB

Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL	Potential Savings
/t/1bbe346….woff2 (db.onlinewebfonts.com)	480 ms
…v48/TK3IWkUHH….woff2 (fonts.gstatic.com)	100 ms

Image elements do not have explicit width and height

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

	URL	Failing Elements
	/img/logo-lid-menu.png (anassekazib2022.fr)	img <img class="logo-menu" src="img/logo-lid-menu.png">
	/img/LogoAK2022-rouge.png (anassekazib2022.fr)	logo Anasse <img src="img/LogoAK2022-rouge.png" width="100" class="d-inline-block align-top" alt="logo Anasse">
	/img/logo-lid-menu.png (anassekazib2022.fr)	img <img class="logo-menu" src="img/logo-lid-menu.png">
	/img/anasseRassemblement.jpg (anassekazib2022.fr)	img <img src="img/anasseRassemblement.jpg">
	/img/nosPropositions.png (anassekazib2022.fr)	img <img src="img/nosPropositions.png">
	/img/SoutenuParRPLongBlanc.png (anassekazib2022.fr)	img <img src="img/SoutenuParRPLongBlanc.png">

Avoid enormous network payloads Total size was 4,487 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL	Transfer Size
/img/anassemobile.png (anassekazib2022.fr)	3,138.2 KiB
/img/nosPropositions.png (anassekazib2022.fr)	514.5 KiB
/img/anasseRassemblement.jpg (anassekazib2022.fr)	188.5 KiB
…config/110…?v=2.9.61&r=stable (connect.facebook.net)	86.7 KiB
/img/SoutenuParRPLongBlanc.png (anassekazib2022.fr)	85.6 KiB
…webfonts/free-fa-brands-400.woff2 (ka-f.fontawesome.com)	75.8 KiB
/img/LogoAK2022-rouge.png (anassekazib2022.fr)	41.5 KiB
/gtm.js?id=GTM-P52GNT2 (www.googletagmanager.com)	40.3 KiB
/jquery-3.5.1.min.js (code.jquery.com)	30.4 KiB
/jquery-3.3.1.min.js (code.jquery.com)	29.8 KiB

Avoid chaining critical requests 20 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Maximum critical path latency: 1,500 ms

Initial Navigation

https://www.anassekazib2022.fr

/mindex.php

(anassekazib2022.fr)

/mindex.php

(anassekazib2022.fr)

/css/style.css?v=1.4

(anassekazib2022.fr)

- 130 ms, 2.60 KiB

/css/bootstrap.css

(anassekazib2022.fr)

- 140 ms, 25.17 KiB

/css/font.css

(anassekazib2022.fr)

/t/1bbe346….woff2

(db.onlinewebfonts.com)

- 480 ms, 13.27 KiB

/css/layout.css?v=1.2

(anassekazib2022.fr)

- 130 ms, 1.01 KiB

/css/normalize.css

(anassekazib2022.fr)

- 120 ms, 1.91 KiB

/css?family=Roboto:300,400,500,700,900&display=swap

(fonts.googleapis.com)

…v30/KFOmCnqEu….woff2

(fonts.gstatic.com)

- 90 ms, 11.38 KiB

/css/event.css

(anassekazib2022.fr)

/css?family=Open+Sans

(fonts.googleapis.com)

- 80 ms, 0.62 KiB

/css?family=Montserrat

(fonts.googleapis.com)

- 80 ms, 0.52 KiB

/css?family=Oswald:400,700

(fonts.googleapis.com)

…v48/TK3IWkUHH….woff2

(fonts.gstatic.com)

- 100 ms, 17.60 KiB

…css/bootstrap.min.css

(stackpath.bootstrapcdn.com)

- 60 ms, 24.91 KiB

…webfonts/free-fa-brands-400.woff2

(ka-f.fontawesome.com)

- 140 ms, 75.75 KiB

/acd0307bf4.js

(kit.fontawesome.com)

- 110 ms, 4.37 KiB

/jquery-3.3.1.min.js

(code.jquery.com)

- 100 ms, 29.83 KiB

…umd/popper.min.js

(cdnjs.cloudflare.com)

- 90 ms, 6.75 KiB

/jquery-3.5.1.min.js

(code.jquery.com)

- 110 ms, 30.39 KiB

…js/bootstrap.min.js

(stackpath.bootstrapcdn.com)

- 60 ms, 15.29 KiB

…2.1.3/jquery.min.js

(cdnjs.cloudflare.com)

- 70 ms, 26.75 KiB

/js/eventscript.js

(anassekazib2022.fr)

- 120 ms, 0.37 KiB

/js/style.js

(anassekazib2022.fr)

- 120 ms, 24.67 KiB

/js/scroll.js

(anassekazib2022.fr)

- 130 ms, 0.67 KiB

Keep request counts low and transfer sizes small 44 requests • 9,018 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type	Requests	Transfer Size
Total	44	9,018.1 KiB
Media	1	4,531.2 KiB
Image	9	3,970.9 KiB
Script	13	312.5 KiB
Font	4	118.0 KiB
Stylesheet	11	60.9 KiB
Other	5	14.3 KiB
Document	1	10.3 KiB
Third-party	25	447.6 KiB

Avoid long main-thread tasks 6 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

URL	Start Time	Duration
…config/110…?v=2.9.61&r=stable (connect.facebook.net)	8,754 ms	79 ms
/mindex.php (anassekazib2022.fr)	2,546 ms	66 ms
/acd0307bf4.js (kit.fontawesome.com)	4,399 ms	61 ms
/analytics.js (www.google-analytics.com)	7,263 ms	58 ms
Unattributable	1,099 ms	55 ms
/acd0307bf4.js (kit.fontawesome.com)	4,758 ms	51 ms

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn more.

Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Initial server response time was short Root document took 120 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more.

URL	Time Spent
/mindex.php (anassekazib2022.fr)	120 ms

Preload key requests

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.

Use HTTP/2

HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.

Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more

Remove duplicate modules in JavaScript bundles

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

Avoid serving legacy JavaScript to modern browsers Potential savings of 11 KiB

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More

URL		Potential Savings
…config/110…?v=2.9.61&r=stable (connect.facebook.net)		11.4 KiB
…config/110…?v=2.9.61&r=stable:20:1574 (connect.facebook.net)	@babel/plugin-transform-classes
…config/110…?v=2.9.61&r=stable:20:28511 (connect.facebook.net)	Array.prototype.filter
…config/110…?v=2.9.61&r=stable:20:34625 (connect.facebook.net)	Array.from
…config/110…?v=2.9.61&r=stable:20:36131 (connect.facebook.net)	Array.prototype.includes
…config/110…?v=2.9.61&r=stable:20:36375 (connect.facebook.net)	Array.prototype.map
…config/110…?v=2.9.61&r=stable:20:36585 (connect.facebook.net)	Array.prototype.reduce
…config/110…?v=2.9.61&r=stable:20:37170 (connect.facebook.net)	Array.prototype.find
…umd/popper.min.js (cdnjs.cloudflare.com)		0.1 KiB
…umd/popper.min.js:4:10983 (cdnjs.cloudflare.com)	@babel/plugin-transform-classes
/en_US/fbevents.js (connect.facebook.net)		0.0 KiB
/en_US/fbevents.js:24:2302 (connect.facebook.net)	@babel/plugin-transform-classes

Avoids an excessive DOM size 662 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

Statistic	Element	Value
Total DOM Elements		662
Maximum DOM Depth	MARS <span class="month">	11
Maximum Child Elements	Nationalité Afghanistan Afrique du Sud Albanie Algérie Allemagne Andorre Angola… <select name="entry.381221457" required="required" class="form-control" placeholder="Nationalité *">	260

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

JavaScript execution time 0.2 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL	Total CPU Time	Script Evaluation	Script Parse
/mindex.php (anassekazib2022.fr)	633 ms	10 ms	4 ms
Unattributable	425 ms	5 ms	1 ms
…config/110…?v=2.9.61&r=stable (connect.facebook.net)	94 ms	71 ms	15 ms
/gtm.js?id=GTM-P52GNT2 (www.googletagmanager.com)	78 ms	62 ms	6 ms
/analytics.js (www.google-analytics.com)	71 ms	58 ms	2 ms

Minimizes main-thread work 1.6 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

Category	Time Spent
Other	603 ms
Script Evaluation	386 ms
Style & Layout	346 ms
Parse HTML & CSS	93 ms
Rendering	70 ms
Script Parsing & Compilation	56 ms

Minimize third-party usage Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party	Transfer Size	Main-Thread Blocking Time
Google Analytics	20 KiB	2 ms
/analytics.js (www.google-analytics.com)	20 KiB	2 ms
Facebook	114 KiB	0 ms
…config/110…?v=2.9.61&r=stable (connect.facebook.net)	87 KiB	0 ms
/en_US/fbevents.js (connect.facebook.net)	27 KiB	0 ms
FontAwesome CDN	94 KiB	0 ms
…webfonts/free-fa-brands-400.woff2 (ka-f.fontawesome.com)	76 KiB	0 ms
…css/free.min.css?token=acd0307bf4 (ka-f.fontawesome.com)	13 KiB	0 ms
jQuery CDN	60 KiB	0 ms
/jquery-3.5.1.min.js (code.jquery.com)	30 KiB	0 ms
/jquery-3.3.1.min.js (code.jquery.com)	30 KiB	0 ms
Google Tag Manager	40 KiB	0 ms
/gtm.js?id=GTM-P52GNT2 (www.googletagmanager.com)	40 KiB	0 ms
Bootstrap CDN	40 KiB	0 ms
…css/bootstrap.min.css (stackpath.bootstrapcdn.com)	25 KiB	0 ms
…js/bootstrap.min.js (stackpath.bootstrapcdn.com)	15 KiB	0 ms
Cloudflare CDN	34 KiB	0 ms
…2.1.3/jquery.min.js (cdnjs.cloudflare.com)	27 KiB	0 ms
…umd/popper.min.js (cdnjs.cloudflare.com)	7 KiB	0 ms
Google Fonts	32 KiB	0 ms
…v48/TK3IWkUHH….woff2 (fonts.gstatic.com)	18 KiB	0 ms
…v30/KFOmCnqEu….woff2 (fonts.gstatic.com)	11 KiB	0 ms
Other Google APIs/SDKs	0 KiB	0 ms
Google/Doubleclick Ads	0 KiB	0 ms

Lazy load third-party resources with facades

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.

Largest Contentful Paint element 0 elements found

This is the largest contentful element painted within the viewport. Learn More

Avoid large layout shifts

These DOM elements contribute most to the CLS of the page.

Uses passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.

Avoids document.write()

For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn more

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.

Buttons do not have an accessible name

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.

Failing Elements
button <button type="button" class="btn btn-danger btn-circle btn-lg">
button <button type="button" class="btn btn-danger btn-circle btn-lg ">
button <button type="button" class="btn btn-danger btn-circle btn-lg ">
button <button type="button" class="btn btn-danger btn-circle btn-lg ">

No form fields have multiple labels

Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.

Failing Elements
input <input class="form-check-inline" type="radio" value="Madame" id="defaultCheck2" name="entry.1729341933" required="">

Image elements do not have [alt] attributes

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

Failing Elements
img <img class="logo-menu" src="img/logo-lid-menu.png">
img <img src="img/SoutenuParRPLongBlanc.png">

Links do not have a discernible name

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

Failing Elements
a <a href="https://www.facebook.com/anasse.kazib/" target="_blank" class="mr-2">
a <a href="https://www.instagram.com/anassekazib/" target="_blank" class="mr-2">
a <a href="https://twitter.com/AnasseKazib" target="_blank" class="mr-2">
a <a href="https://www.revolutionpermanente.fr/" target="_blank" class="mr-2">
a <a target="_blank" href="https://www.revolutionpermanente.fr/" width="100%">

Background and foreground colors do not have a sufficient contrast ratio.

Low-contrast text is difficult or impossible for many users to read. Learn more.

Failing Elements
Faire un don <h5 class="text-big-left text-light ">
Informations personnelles * <h5 class="text-big-left text-light ">
J'ai lu et j'accepte les mentions d'information relatives au recueil de mes don… <label class="form-check-label" for="defaultCheck2">
Soumettre <button type="submit" class="btn btn-light btn-lg btn-block">
/anasse.kazib/ <a target="_blank" href="https://www.facebook.com/anasse.kazib/" class="mb-0">
@anassekazib <a target="_blank" href="https://www.instagram.com/anassekazib/">
@AnasseKazib <a target="_blank" href="https://twitter.com/AnasseKazib">

[id] attributes on active, focusable elements are not unique

All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.

Failing Elements
input <input name="entry.104042299" type="text" class="form-control" id="formGroupExampleInput2" placeholder="Nom" required="">
input <input name="entry.964304263" type="text" class="form-control" id="inputCity" placeholder="Adresse">

Heading elements are not in a sequentially-descending order

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

Failing Elements
Faire un don <h5 class="text-big-left text-light ">

ARIA IDs are not unique

The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.

Failing Elements
input <input class="form-check-inline" type="radio" value="Madame" id="defaultCheck2" name="entry.1729341933" required="">

The page has a logical tab order

Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.

Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.

The user's focus is directed to new content added to the page

If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.

User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.

Custom controls have associated labels

Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn more.

Visual order on the page follows DOM order

DOM order matches the visual order, improving navigation for assistive technology. Learn more.

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn more.

HTML5 landmark elements are used to improve navigation

Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.

[aria-*] attributes match their roles

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.

[aria-hidden="true"] is not present on the document <body>

Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.

[aria-hidden="true"] elements do not contain focusable descendents

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.

[aria-*] attributes have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.

[aria-*] attributes are valid and not misspelled

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.

The page contains a heading, skip link, or landmark region

Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.

Document has a <title> element

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.

<html> element has a [lang] attribute

If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.

<html> element has a valid value for its [lang] attribute

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.

Form elements have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.

<video> elements contain a <track> element with [kind="captions"]

When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.

[accesskey] values are unique

Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.

button, link, and menuitem elements have accessible names

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

ARIA input fields have accessible names

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

ARIA meter elements have accessible names

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

ARIA progressbar elements have accessible names

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

[role]s have all required [aria-*] attributes

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.

Elements with an ARIA [role] that require children to contain a specific [role] have all required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.

[role]s are contained by their required parent element

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.

[role] values are valid

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

ARIA toggle fields have accessible names

When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

ARIA treeitem elements have accessible names

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.

Definition list items are wrapped in <dl> elements

Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.

<frame> or <iframe> elements have a title

Screen reader users rely on frame titles to describe the contents of frames. Learn more.

<input type="image"> elements have [alt] text

When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.

Lists contain only <li> elements and script supporting elements (<script> and <template>).

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

List items (<li>) are contained within <ul> or <ol> parent elements

Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.

The document does not use <meta http-equiv="refresh">

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.

<object> elements have [alt] text

Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.

No element has a [tabindex] value greater than 0

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.

Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.

Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.

<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.

Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.

[lang] attributes have a valid value

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.

Best Practices

Does not use HTTPS 1 insecure request found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.

Insecure URL	Request Resolution
/mindex.php (anassekazib2022.fr)	Allowed

Links to cross-origin destinations are unsafe

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.

Failing Anchors
a <a href="https://www.facebook.com/anasse.kazib/" target="_blank" class="mr-2">
a <a href="https://www.instagram.com/anassekazib/" target="_blank" class="mr-2">
a <a href="https://twitter.com/AnasseKazib" target="_blank" class="mr-2">
a <a href="https://www.revolutionpermanente.fr/" target="_blank" class="mr-2">
a <a href="https://www.facebook.com/anasse.kazib/" target="_blank" class="mr-2">
a <a href="https://www.instagram.com/anassekazib/" target="_blank" class="mr-2">
a <a href="https://twitter.com/AnasseKazib" target="_blank" class="mr-2">
a <a href="https://www.revolutionpermanente.fr/" target="_blank" class="mr-2">
/anasse.kazib/ <a target="_blank" href="https://www.facebook.com/anasse.kazib/" class="mb-0">
@anassekazib <a target="_blank" href="https://www.instagram.com/anassekazib/">
@AnasseKazib <a target="_blank" href="https://twitter.com/AnasseKazib">
a <a target="_blank" href="https://www.revolutionpermanente.fr/" width="100%">

Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.

Library Version	Vulnerability Count	Highest Severity
jQuery@2.1.3	4	Medium

Avoids requesting the geolocation permission on page load

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.

Avoids requesting the notification permission on page load

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.

Allows users to paste into password fields

Preventing password pasting undermines good security policy. Learn more.

Displays images with correct aspect ratio

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

Serves images with appropriate resolution

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.

Page has the HTML doctype

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.

Properly defines charset

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.

Avoids unload event listeners

The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn More

Avoids Application Cache

Application Cache is deprecated. Learn more.

Detected JavaScript libraries

All front-end JavaScript libraries detected on the page. Learn more.

Name	Version
Bootstrap	4.3.1
jQuery	2.1.3
core-js	core-js-pure@3.0.0

Avoids deprecated APIs

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

No browser errors logged to the console

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more

Page has valid source maps

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.

URL	Map URL
…2.1.3/jquery.min.js (cdnjs.cloudflare.com)	…2.1.3/jquery.min.map (cdnjs.cloudflare.com)
Warning: missing 1 item in `.sourcesContent`
/js/style.js (anassekazib2022.fr)	/js/bootstrap.js.map (anassekazib2022.fr)
Error: Invalid response status code: 404
…js/bootstrap.min.js (stackpath.bootstrapcdn.com)	…js/bootstrap.min.js.map (stackpath.bootstrapcdn.com)
…umd/popper.min.js (cdnjs.cloudflare.com)	…umd/popper.min.js.map (cdnjs.cloudflare.com)

No issues in the Issues panel in Chrome Devtools

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Fonts with font-display: optional are preloaded

Preload `optional` fonts so first-time visitors may use them. Learn More

SEO

These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more.

Links are not crawlable

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

Uncrawlable Link
3 MARS RASSEMBLEMENT DE SOLIDARITÉ : PAS DE RÉPRESSION CONTRE ANASSE KAZIB ! A… <a class="event">

Image elements do not have [alt] attributes

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

Failing Elements
img <img class="logo-menu" src="img/logo-lid-menu.png">
img <img src="img/SoutenuParRPLongBlanc.png">

Structured data is valid

Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.

Has a <meta name="viewport"> tag with width or initial-scale

Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.

Document has a <title> element

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.

Document has a meta description

Meta descriptions may be included in search results to concisely summarize page content. Learn more.

Page has successful HTTP status code

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.

Links have descriptive text

Descriptive link text helps search engines understand your content. Learn more.

Page isn’t blocked from indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.

Document has a valid hreflang

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.

Document uses legible font sizes 99.64% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.

Source	Selector	% of Page Text	Font Size
/css/event.css:117:8 (anassekazib2022.fr)	.title	0.24%	9.6px
/css/event.css:125:14 (anassekazib2022.fr)	.description	0.12%	9.6px
Legible text		99.64%	≥ 12px

Document avoids plugins

Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.

Tap targets are sized appropriately 100% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

robots.txt is valid

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.

Document has a valid rel=canonical

Canonical links suggest which URL to show in search results. Learn more.

Progressive Web App

These checks validate the aspects of a Progressive Web App. Learn more.

Web app manifest or service worker do not meet the installability requirements 1 reason

Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.

Failure reason
No manifest was fetched

Does not register a service worker that controls page and start_url

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.

Redirects HTTP traffic to HTTPS

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.

Is not configured for a custom splash screen

Failures: No manifest was fetched.

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.

Does not set a theme color for the address bar.

Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

The browser address bar can be themed to match your site. Learn more.

Content is not sized correctly for the viewport

The viewport size of 376px does not match the window size of 360px.

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.

Has a <meta name="viewport"> tag with width or initial-scale

Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.

Does not provide a valid apple-touch-icon

For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.

Manifest doesn't have a maskable icon

No manifest was fetched

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.

Site works cross-browser

To reach the most number of users, sites should work across every major browser. Learn more.

Page transitions don't feel like they block on the network

Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more.

Each page has a URL

Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more.