19/03/2024, 19:58 about:blank

http://localhost:3000/colaboradores

65 62 78 82

Performance Accessibility Best SEO PWA

Practices

65

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

0–49 50–89 90–100

METRICS Expand view

First Contentful Paint Largest Contentful Paint

2.6 s 3.8 s

Total Blocking Time Cumulative Layout Shift

0 ms 0.002

Speed Index

2.6 s

View Treemap

Show audits relevant to: All FCP LCP TBT CLS

DIAGNOSTICS

Enable text compression — Potential savings of 1,197 KiB

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

Transfer Potential
URL
Size Savings

localhost 1st Party 1,328.9 KiB 1,197.0 KiB

/assets/application-3438a93….css (localhost) 1,103.8 KiB 1,028.6 KiB

/assets/turbo.min-c6325b8….js (localhost) 99.2 KiB 72.4 KiB

/assets/flatpickr-ccb36f1….js (localhost) 55.2 KiB 40.3 KiB

/assets/slim-select-b855e6e….js (localhost) 36.8 KiB 28.2 KiB

/colaboradores (localhost) 30.7 KiB 25.3 KiB

/assets/stimulus-loading-3576ce9….js (localhost) 3.2 KiB 2.2 KiB

Reduce unused CSS — Potential savings of 1,104 KiB

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

Transfer Potential
URL
Size Savings

localhost 1st Party 1,104.1 KiB 1,083.9 KiB

/assets/application-3438a93….css (localhost) 1,104.1 KiB 1,083.9 KiB

about:blank 1/24
19/03/2024, 19:58 about:blank

Transfer Potential
URL
Size Savings

Unattributable 20.3 KiB 20.2 KiB

/*! * Font Awesome Free 6.5.1 by @fontawesome - https://fontawesome.com *

20.3 KiB 20.2 KiB
License - https://fonta…

Largest Contentful Paint element — 3,770 ms

This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
LCP

Element

div.navbar__background

Phase % of LCP Timing

TTFB 5% 180 ms

Load Delay 66% 2,490 ms

Load Time 19% 730 ms

Render Delay 10% 370 ms

Minify CSS — Potential savings of 753 KiB

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

Transfer Potential
URL
Size Savings

localhost 1st Party 1,104.1 KiB 752.7 KiB

/assets/application-3438a93….css (localhost) 1,104.1 KiB 752.7 KiB

Preload Largest Contentful Paint image — Potential savings of 500 ms

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more
about preloading LCP elements. LCP

URL Potential Savings

localhost 1st Party 500 ms

div.
na
vb
/assets/header-background-8b27056….png (localhost) 500 ms
ar_
_b
ackground

Reduce unused JavaScript — Potential savings of 563 KiB

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

Transfer Potential
URL
Size Savings

Unattributable 441.6 KiB 407.2 KiB

chrome-extension://jdcfmebflppkljibgpdlboifpcaalolg/content-scripts/capture-
109.7 KiB 109.5 KiB
coupons/loader.js

chrome-extension://jdcfmebflppkljibgpdlboifpcaalolg/content-scripts/capture-
109.7 KiB 97.3 KiB
coupons/loader.js

chrome-extension://jdcfmebflppkljibgpdlboifpcaalolg/content-scripts/cart-
103.9 KiB 92.2 KiB
tracking/loader.js

chrome-extension://jdcfmebflppkljibgpdlboifpcaalolg/content-
96.5 KiB 87.5 KiB
scripts/logger/sentry.js

about:blank 2/24
19/03/2024, 19:58 about:blank

Transfer Potential
URL
Size Savings

chrome-
extension://dmghijelimhndkbmpgbldicpogfkceaj/data/content_script/resources/na 21.9 KiB 20.7 KiB
tive.js

localhost 1st Party 191.2 KiB 155.5 KiB

/assets/turbo.min-c6325b8….js (localhost) 99.2 KiB 84.0 KiB

…../node_modules/@hotwired/turbo/dist/turbo.es2017-esm.js 86.8 KiB 73.7 KiB

…../node_modules/@rails/actioncable/src/connection.js 3.1 KiB 2.9 KiB

…../node_modules/@rails/actioncable/src/connection_monitor.js 2.3 KiB 2.2 KiB

…../node_modules/@rails/actioncable/src/subscriptions.js 1.2 KiB 1.2 KiB

…../node_modules/@rails/actioncable/src/subscription_guarantor.js 0.8 KiB 0.8 KiB

/assets/flatpickr-ccb36f1….js (localhost) 55.2 KiB 51.3 KiB

/assets/slim-select-b855e6e….js (localhost) 36.8 KiB 20.2 KiB

Serve images in next-gen formats — Potential savings of 282 KiB

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

Show 3rd-party resources (1)

Resource Potential
URL
Size Savings

localhost 1st Party 280.2 KiB 271.7 KiB

/assets/header-background-8b27056….png (localhost) 280.2 KiB 271.7 KiB

div.navbar__background

Cloudinary Content 15.3 KiB 9.9 KiB

…
15.3 KiB 9.9 KiB
v166…/n53gmqov8gvn0eue0gkw.jpg (res.cloudinary.com)

Eliminate render-blocking resources — Potential savings of 40 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical
JS/styles. Learn how to eliminate render-blocking resources. FCP LCP

Transfer Potential
URL
Size Savings

JSDelivr CDN Cdn 3.7 KiB 220 ms

…dist/flatpickr.min.css (cdn.jsdelivr.net) 3.7 KiB 220 ms

FontAwesome CDN Cdn 4.3 KiB 280 ms

/b5b2113461.js (kit.fontawesome.com) 4.3 KiB 280 ms

Minify JavaScript — Potential savings of 120 KiB

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

Transfer Potential
URL
Size Savings

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/webext-ad-
104.8 KiB 86.4 KiB
filtering-solution/content.js

chrome-
extension://dmghijelimhndkbmpgbldicpogfkceaj/data/content_script/resources/na 21.9 KiB 10.6 KiB
tive.js

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/polyfill.js 14.0 KiB 8.9 KiB

chrome-
extension://dmghijelimhndkbmpgbldicpogfkceaj/data/content_script/vendor/tinyc 11.8 KiB 5.2 KiB
olor.js

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/adblock-picreplacement.js 9.0 KiB 3.7 KiB

about:blank 3/24
19/03/2024, 19:58 about:blank

Transfer Potential
URL
Size Savings

chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/adblock-functions.js 6.8 KiB 3.1 KiB

chrome-
7.5 KiB 2.4 KiB
extension://dmghijelimhndkbmpgbldicpogfkceaj/data/content_script/inject.js

Serve static assets with an efficient cache policy — 2 resources found

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

Cache Transfer
URL
TTL Size

Cloudinary Content 16 KiB

…v166…/n53gmqov8gvn0eue0gkw.jpg (res.cloudinary.com) 30d 16 KiB

JSDelivr CDN Cdn 4 KiB

…dist/flatpickr.min.css (cdn.jsdelivr.net) 7d 4 KiB

Image elements do not have explicit width and height

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

URL

localhost 1st Party

img.mx-
2.button__s
earch--icon- …icons/icons8-pesquisar-345a9e1….png (localhost)
position

img.button_
_icon--
size.me-2 …icons/icons8-cadastro-colaborador-1515495….png (localhost)

img.button_
_icon--
filter.me-2 …icons/Vector-51fe5ea….png (localhost)

Properly size images — Potential savings of 25 KiB

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

Resource Potential
URL
Size Savings

localhost 1st Party 24.7 KiB 24.6 KiB

/assets/logo-insirius-02@3x-
24.7 KiB 24.6 KiB
9329e93….png (localhost)

img.brand.mt-3

Efficiently encode images — Potential savings of 5 KiB

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

Resource Potential
URL
Size Savings

Cloudinary Content 15.3 KiB 5.2 KiB

…v166…/n53gmqov8gvn0eue0gkw.jpg (res.cloudinary.com) 15.3 KiB 5.2 KiB

Avoid large layout shifts — 5 elements found

These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value

about:blank 4/24
19/03/2024, 19:58 about:blank
due to windowing. Learn how to improve CLS CLS

Element Layout shift impact

div.informationBar__search

0.001

div.dropdown-center

0.000

div.dropdown-center

0.000

div.dropdown-center

0.000

div.dropdown-center

0.000

Initial server response time was short — Root document took 50 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the
Time to First Byte metric. FCP LCP

URL Time Spent

localhost 1st Party 50 ms

/colaboradores (localhost) 50 ms

Avoids enormous network payloads — Total size was 2,228 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload
sizes. LCP

Show 3rd-party resources (3)

Transfer
URL
Size

localhost 1st Party 1,762.0 KiB

/assets/application-3438a93….css (localhost) 1,104.1 KiB

/assets/header-background-8b27056….png (localhost) 280.5 KiB

…font-awesome/fa-solid-900-1264bbf….woff2 (localhost) 153.1 KiB

/assets/turbo.min-c6325b8….js (localhost) 99.5 KiB

/assets/flatpickr-ccb36f1….js (localhost) 55.5 KiB

/assets/slim-select-b855e6e….js (localhost) 37.1 KiB

/colaboradores (localhost) 32.2 KiB

FontAwesome CDN Cdn 153.7 KiB

…webfonts/free-fa-solid-900.woff2 (ka-f.fontawesome.com) 153.7 KiB

Google Fonts Cdn 75.6 KiB

…v19/QGYsz_wNa….woff2 (fonts.gstatic.com) 49.5 KiB

…v15/ijwRs572X….woff2 (fonts.gstatic.com) 26.1 KiB

Avoids an excessive DOM size — 366 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to
avoid an excessive DOM size. TBT

about:blank 5/24
19/03/2024, 19:58 about:blank

Statistic Element Value

Total DOM Elements 366

img.button__logo--
size.me-2
Maximum DOM Depth 11

div.form__standard--box-
white
Maximum Child Elements 24

Avoid chaining critical requests — 4 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 how to avoid chaining critical requests. FCP LCP

Maximum critical path latency: 304.031 ms

Initial Navigation
/colaboradores (localhost)

…dist/flatpickr.min.css (cdn.jsdelivr.net) - 76.174 ms, 3.67 KiB

…themes/material_blue.css (npmcdn.com)

…themes/material_blue.css (npmcdn.com) - 25.204 ms, 3.67 KiB

…dist/slimselect.css (unpkg.com)

…dist/slimselect.css (unpkg.com) - 30.118 ms, 1.95 KiB

/b5b2113461.js (kit.fontawesome.com) - 101.448 ms, 4.33 KiB

JavaScript execution time — 0.3 s

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

Show 3rd-party resources (1)

Total CPU Script Script

URL
Time Evaluation Parse

localhost 1st Party 273 ms 96 ms 41 ms

/colaboradores (localhost) 273 ms 96 ms 41 ms

Unattributable 269 ms 47 ms 43 ms

Unattributable 183 ms 6 ms 0 ms

chrome-extension://jdcfmebflppkljibgpdlboifpcaalolg/content-
86 ms 41 ms 43 ms
scripts/capture-coupons/loader.js

FontAwesome CDN Cdn 84 ms 47 ms 0 ms

/b5b2113461.js (kit.fontawesome.com) 84 ms 47 ms 0 ms

Minimizes main-thread work — 0.8 s

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

Category Time Spent

Other 264 ms

Script Evaluation 253 ms

Script Parsing & Compilation 110 ms

Style & Layout 83 ms

Parse HTML & CSS 26 ms

Rendering 22 ms

Garbage Collection 12 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 how to minimize third-party impact. TBT

about:blank 6/24
19/03/2024, 19:58 about:blank

Transfer Main-Thread
Third-Party
Size Blocking Time

FontAwesome CDN Cdn 213 KiB 0 ms

…webfonts/free-fa-solid-900.woff2 (ka-f.fontawesome.com) 154 KiB 0 ms

…webfonts/free-fa-regular-400.woff2 (ka-f.fontawesome.com) 25 KiB 0 ms

…css/free.min.css?token=b5b2113461 (ka-f.fontawesome.com) 23 KiB 0 ms

…css/free-v4-shims.min.css?token=b5b2113461 (ka-f.fontawesome.com) 5 KiB 0 ms

/b5b2113461.js (kit.fontawesome.com) 4 KiB 0 ms

…css/free-v4-font-face.min.css?token=b5b2113461 (ka-f.fontawesome.com) 1 KiB 0 ms

…css/free-v5-font-face.min.css?token=b5b2113461 (ka-f.fontawesome.com) 1 KiB 0 ms

Google Fonts Cdn 77 KiB 0 ms

…v19/QGYsz_wNa….woff2 (fonts.gstatic.com) 50 KiB 0 ms

…v15/ijwRs572X….woff2 (fonts.gstatic.com) 26 KiB 0 ms

/css?
family=Nunito:400,700|Work+Sans:400,700&display=swap (fonts.googleapis 1 KiB 0 ms
.com)

/css2?
1 KiB 0 ms
family=Public+Sans:wght@200;500&display=swap (fonts.googleapis.com)

jspm.io 74 KiB 0 ms

…js/bootstrap.esm.js (ga.jspm.io) 16 KiB 0 ms

…dist/stimulus.js (ga.jspm.io) 11 KiB 0 ms

…src/autocomplete.js (ga.jspm.io) 2 KiB 0 ms

…_/a0ba12d2.js (ga.jspm.io) 2 KiB 0 ms

…modifiers/preventOverflow.js (ga.jspm.io) 2 KiB 0 ms

…modifiers/computeStyles.js (ga.jspm.io) 2 KiB 0 ms

…modifiers/flip.js (ga.jspm.io) 2 KiB 0 ms

…modifiers/arrow.js (ga.jspm.io) 1 KiB 0 ms

…utils/detectOverflow.js (ga.jspm.io) 1 KiB 0 ms

…modifiers/hide.js (ga.jspm.io) 1 KiB 0 ms

…_/084d303b.js (ga.jspm.io) 1 KiB 0 ms

…lib/popper.js (ga.jspm.io) 1 KiB 0 ms

…lib/index.js (ga.jspm.io) 1 KiB 0 ms

…utils/computeAutoPlacement.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getOffsetParent.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getCompositeRect.js (ga.jspm.io) 1 KiB 0 ms

…modifiers/applyStyles.js (ga.jspm.io) 1 KiB 0 ms

…lib/popper-lite.js (ga.jspm.io) 1 KiB 0 ms

…modifiers/offset.js (ga.jspm.io) 1 KiB 0 ms

…_/7a91f8b9.js (ga.jspm.io) 1 KiB 0 ms

…lib/enums.js (ga.jspm.io) 1 KiB 0 ms

…_/bb24ce41.js (ga.jspm.io) 1 KiB 0 ms

…modifiers/index.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getDocumentRect.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getViewportRect.js (ga.jspm.io) 1 KiB 0 ms

…modifiers/eventListeners.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/listScrollParents.js (ga.jspm.io) 1 KiB 0 ms

…modifiers/popperOffsets.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getLayoutRect.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getScrollParent.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getWindowScrollBarX.js (ga.jspm.io) 1 KiB 0 ms

…_/1ba79728.js (ga.jspm.io) 1 KiB 0 ms

…_/a9ca29ce.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/instanceOf.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getParentNode.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getNodeScroll.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getWindow.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getWindowScroll.js (ga.jspm.io) 1 KiB 0 ms

…utils/getOppositePlacement.js (ga.jspm.io) 1 KiB 0 ms

…_/6a201025.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/isScrollParent.js (ga.jspm.io) 1 KiB 0 ms

…_/b8df2d1e.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getDocumentElement.js (ga.jspm.io) 1 KiB 0 ms

…utils/getMainAxisFromPlacement.js (ga.jspm.io) 1 KiB 0 ms

…_/2d19854a.js (ga.jspm.io) 1 KiB 0 ms

…utils/getOppositeVariationPlacement.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getNodeName.js (ga.jspm.io) 1 KiB 0 ms

about:blank 7/24
19/03/2024, 19:58 about:blank

Transfer Main-Thread
Third-Party
Size Blocking Time

…dom-utils/getComputedStyle.js (ga.jspm.io) 1 KiB 0 ms

…dom-utils/getHTMLElementScroll.js (ga.jspm.io) 1 KiB 0 ms

…_/c7d11060.js (ga.jspm.io) 1 KiB 0 ms

…_/7742d4ca.js (ga.jspm.io) 1 KiB 0 ms

Cloudinary Content 16 KiB 0 ms

…v166…/n53gmqov8gvn0eue0gkw.jpg (res.cloudinary.com) 16 KiB 0 ms

Unpkg Cdn 6 KiB 0 ms

…themes/material_blue.css (npmcdn.com) 4 KiB 0 ms

…dist/slimselect.css (unpkg.com) 2 KiB 0 ms

…themes/material_blue.css (npmcdn.com) 1 KiB 0 ms

…dist/slimselect.css (unpkg.com) 0 KiB 0 ms

Wappalyzer - Technology profiler Chrome Extension 6 KiB 0 ms

chrome-extension://gppongmhjkpfnbhagpmjfkannfbllamg/js/dom.js 4 KiB 0 ms

chrome-extension://gppongmhjkpfnbhagpmjfkannfbllamg/js/js.js 3 KiB 0 ms

JSDelivr CDN Cdn 4 KiB 0 ms

…dist/flatpickr.min.css (cdn.jsdelivr.net) 4 KiB 0 ms

Cloudflare CDN Cdn 2 KiB 0 ms

…1.27.1/slimselect.min.css (cdnjs.cloudflare.com) 2 KiB 0 ms

lewagon.com 1 KiB 0 ms

…users/ssaunier (kitt.lewagon.com) 1 KiB 0 ms

Avoid long main-thread tasks — 2 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long
main-thread tasks TBT

URL Start Time Duration

localhost 1st Party 143 ms

/colaboradores (localhost) 272 ms 143 ms

Unattributable 72 ms

chrome-extension://jdcfmebflppkljibgpdlboifpcaalolg/content-scripts/capture-
484 ms 72 ms
coupons/loader.js

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

PASSED AUDITS (17) Hide

Defer offscreen images

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

Preconnect to required origins

Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party
origins. Learn how to preconnect to required origins. FCP LCP

Avoid multiple page redirects

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

Preload key requests

Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn
how to preload key requests. FCP LCP

Use HTTP/2

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

Use video formats for animated content

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

about:blank 8/24
19/03/2024, 19:58 about:blank

Remove duplicate modules in JavaScript bundles

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

Avoid serving legacy JavaScript to modern browsers

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

User Timing marks and measures

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

All text remains visible during webfont loads

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

Lazy load third-party resources with facades

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to
defer third-parties with a facade. TBT

Largest Contentful Paint image was not lazily loaded

Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Learn more about optimal lazy loading. LCP

Element

div.navbar__background

Uses passive listeners to improve scrolling performance

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

Avoids document.write()

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

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animations CLS

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

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond
delay to user input. Learn more about using the viewport meta tag. TBT

Page didn't prevent back/forward cache restoration

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

62

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-*] attributes do not match their roles

Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes.
Learn how to match ARIA attributes to their roles.

about:blank 9/24
19/03/2024, 19:58 about:blank

Failing Elements

p.navbar__menu

p.navbar__menu.navbar__menu--active.text-light

p.navbar__menu

p.navbar__menu

p.navbar__menu

p.navbar__menu

p.navbar__menu

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those
required children.

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about
roles and required children elements.

Failing Elements

div.ss-content.form__modal--select

input

ARIA input fields do not have accessible names

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

Failing Elements

div.ss-content.form__modal--select

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.

NAMES AND LABELS

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 how to make buttons more accessible.

Failing Elements

button.button__search

about:blank 10/24
19/03/2024, 19:58 about:blank

Image elements do not have [alt] attributes

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

Failing Elements

img.brand.mt-3

img.avatar__navbar-round

img.mx-2.button__search--icon-position

img.button__icon--filter.me-2

img.button__icon--size.me-2

img.button__logo--size.me-2

img.button__logo--size.button__logo--position.ms-2

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 how to make links accessible.

Failing Elements

about:blank 11/24
19/03/2024, 19:58 about:blank

Failing Elements

about:blank 12/24
19/03/2024, 19:58 about:blank

Failing Elements

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

CONTRAST

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

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

Failing Elements

p#list-item-1.subtitle--green

div.form__standard--box-white

div.col-1.d-flex.justify-content-center

div.form__standard--box-white

div.col-3

div.form__standard--box-white

div.col-3

div.form__standard--box-white

div.col-2

div.form__standard--box-white

div.col-1

div.form__standard--box-white

These are opportunities to improve the legibility of your content.

INTERNATIONALIZATION AND LOCALIZATION

about:blank 13/24
19/03/2024, 19:58 about:blank

<html> element does not have a [lang] attribute

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

Failing Elements

html

These are opportunities to improve the interpretation of your content by users in different locales.

TABLES AND LISTS

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

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

Failing Elements

ul.navbar-nav.me-auto

div.dropdown-center

div.dropdown-center

div.dropdown-center

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

ADDITIONAL ITEMS TO MANUALLY CHECK (10) Hide

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls
focusable.

Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive
elements. Learn how to decorate interactive elements with affordance hints.

The page has a logical tab order

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

Visual order on the page follows DOM order

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

User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.

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

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

HTML5 landmark elements are used to improve navigation

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

about:blank 14/24
19/03/2024, 19:58 about:blank

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.

Custom controls have associated labels

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

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.

These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility
review.

PASSED AUDITS (17) Hide

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

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

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

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

[role]s are contained by their required parent element

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

[aria-*] attributes have valid values

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

[aria-*] attributes are valid and not misspelled

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

[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 about the viewport meta tag.

button, link, and menuitem elements have accessible names

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

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

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

[role] values are valid

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

ARIA toggle fields have accessible names

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

Document has a <title> element

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

[id] attributes on active, focusable elements are unique

All focusable elements must have a unique id to ensure that they're visible to assistive technologies. Learn how to fix
duplicate ids.

Form elements have associated labels

about:blank 15/24
19/03/2024, 19:58 about:blank
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about
form element labels.

No element has a [tabindex] value greater than 0

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

Heading elements appear in a sequentially-descending order

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

Values assigned to role="" are valid ARIA roles.

ARIA roles enable assistive technologies to know the role of each element on the web page. If the role values are
misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to
users of assistive technologies. Learn more about ARIA roles.

Image elements do not have [alt] attributes that are redundant text.

Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text
adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more
about the alt attribute.

NOT APPLICABLE (32) Hide

[accesskey] values are unique

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

Elements with role="dialog" or role="alertdialog" have accessible names.

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these
elements. Learn how to make ARIA dialog elements more accessible.

ARIA meter elements have accessible names

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

ARIA progressbar elements have accessible names

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

Elements with the role=text attribute do not have focusable descendents.

Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's
focusable descendents will not be announced. Learn more about the role=text attribute.

ARIA tooltip elements have accessible names

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

ARIA treeitem elements have accessible names

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

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

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

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

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to
structure definition lists correctly.

Definition list items are wrapped in <dl> elements

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

ARIA IDs are unique

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

about:blank 16/24
19/03/2024, 19:58 about:blank

No form fields have multiple labels

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

<frame> or <iframe> elements have a title

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

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

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.

<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.

If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly.
Learn more about the lang attribute.

Input buttons have discernible text.

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input
button. Learn more about input buttons.

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

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

Links are distinguishable without relying on color.

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.

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

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

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

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

<object> elements have alternate text

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

Select elements have associated label elements.

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

Skip links are focusable.

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Tables have different content in the summary attribute and <caption>.

The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table
mark-up helps users of screen readers. Learn more about summary and caption.

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

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

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

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

[lang] attributes have a valid value

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn
how to use the lang attribute.

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

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

about:blank 17/24
19/03/2024, 19:58 about:blank

All heading elements contain content.

A heading with no content or inaccessible text prevent screen reader users from accessing information on the page's
structure. Learn more about headings.

Touch targets have sufficient size and spacing.

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the
targets. Learn more about touch targets.

Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead
of cells with the [colspan] attribute may improve the experience for screen reader users. Learn more about captions.

<td> elements in a large <table> have one or more table headers.

Screen readers have features to make navigating tables easier. Ensuring that <td> elements in a large table (3 or more
cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more
about table headers.

78

Best Practices

GENERAL

Uses third-party cookies — 9 cookies found

Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party
cookies.

Name URL

Cloudflare CDN Cdn

_ga_PHVG60J2FD …1.27.1/slimselect.min.css (cdnjs.cloudflare.com)

_ga_SQCRB0TXZW …1.27.1/slimselect.min.css (cdnjs.cloudflare.com)

lewagon.com

_iub_cs-7967062 …users/ssaunier (kitt.lewagon.com)

_iub_cs-48166262 …users/ssaunier (kitt.lewagon.com)

_hjSessionUser_376674 …users/ssaunier (kitt.lewagon.com)

Cloudinary Content

__cfruid …v166…/n53gmqov8gvn0eue0gkw.jpg (res.cloudinary.com)

cf_clearance …v166…/n53gmqov8gvn0eue0gkw.jpg (res.cloudinary.com)

_ga …v166…/n53gmqov8gvn0eue0gkw.jpg (res.cloudinary.com)

_ga_NKMQJY2D2H …v166…/n53gmqov8gvn0eue0gkw.jpg (res.cloudinary.com)

Issues were logged 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.

Issue type

Cookie

…1.27.1/slimselect.min.css (cdnjs.cloudflare.com)

…users/ssaunier (kitt.lewagon.com)

…v166…/n53gmqov8gvn0eue0gkw.jpg (res.cloudinary.com)

TRUST AND SAFETY

Ensure CSP is effective against XSS attacks

about:blank 18/24
19/03/2024, 19:58 about:blank
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use
a CSP to prevent XSS

Description Directive Severity

No CSP found in enforcement mode High

PASSED AUDITS (12) Hide

Uses HTTPS

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

Avoids deprecated APIs

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

Allows users to paste into input fields

Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more
about user-friendly input fields.

Avoids requesting the geolocation permission on page load

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

Avoids requesting the notification permission on page load

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

Displays images with correct aspect ratio

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

Serves images with appropriate resolution

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

Page has the HTML doctype

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

Properly defines charset

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

Avoids unload event listeners

The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache.
Use pagehide or visibilitychange events instead. Learn more about unload event listeners

No browser errors logged to the console

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser
concerns. Learn more about this errors in console diagnostic audit

Page has valid source maps

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

Show 3rd-party resources (49)

URL Map URL

jspm.io

…src/autocomplete.js (ga.jspm.io) …src/autocomplete.js.map (ga.jspm.io)

…js/bootstrap.esm.js (ga.jspm.io) …js/bootstrap.esm.js.map (ga.jspm.io)

…
…utils/getOppositeVariationPlacement.js (ga.jspm.io) utils/getOppositeVariationPlacement.js.map (g
a.jspm.io)

about:blank 19/24
19/03/2024, 19:58 about:blank

URL Map URL

…
…utils/getOppositePlacement.js (ga.jspm.io)
utils/getOppositePlacement.js.map (ga.jspm.io)

…
…utils/getMainAxisFromPlacement.js (ga.jspm.io) utils/getMainAxisFromPlacement.js.map (ga.js
pm.io)

…utils/detectOverflow.js (ga.jspm.io) …utils/detectOverflow.js.map (ga.jspm.io)

…
…utils/computeAutoPlacement.js (ga.jspm.io) utils/computeAutoPlacement.js.map (ga.jspm.io
)

…lib/popper.js (ga.jspm.io) …lib/popper.js.map (ga.jspm.io)

…lib/popper-lite.js (ga.jspm.io) …lib/popper-lite.js.map (ga.jspm.io)

…
…modifiers/preventOverflow.js (ga.jspm.io)
modifiers/preventOverflow.js.map (ga.jspm.io)

…modifiers/popperOffsets.js (ga.jspm.io) …modifiers/popperOffsets.js.map (ga.jspm.io)

…modifiers/offset.js (ga.jspm.io) …modifiers/offset.js.map (ga.jspm.io)

…modifiers/hide.js (ga.jspm.io) …modifiers/hide.js.map (ga.jspm.io)

…modifiers/flip.js (ga.jspm.io) …modifiers/flip.js.map (ga.jspm.io)

…modifiers/eventListeners.js (ga.jspm.io) …modifiers/eventListeners.js.map (ga.jspm.io)

…modifiers/computeStyles.js (ga.jspm.io) …modifiers/computeStyles.js.map (ga.jspm.io)

…modifiers/arrow.js (ga.jspm.io) …modifiers/arrow.js.map (ga.jspm.io)

…modifiers/applyStyles.js (ga.jspm.io) …modifiers/applyStyles.js.map (ga.jspm.io)

…lib/enums.js (ga.jspm.io) …lib/enums.js.map (ga.jspm.io)

…dom-utils/listScrollParents.js (ga.jspm.io) …dom-utils/listScrollParents.js.map (ga.jspm.io)

…dom-utils/isScrollParent.js (ga.jspm.io) …dom-utils/isScrollParent.js.map (ga.jspm.io)

…dom-utils/instanceOf.js (ga.jspm.io) …dom-utils/instanceOf.js.map (ga.jspm.io)

…dom-
…dom-utils/getWindowScrollBarX.js (ga.jspm.io)
utils/getWindowScrollBarX.js.map (ga.jspm.io)

…dom-
…dom-utils/getWindowScroll.js (ga.jspm.io)
utils/getWindowScroll.js.map (ga.jspm.io)

…dom-utils/getWindow.js (ga.jspm.io) …dom-utils/getWindow.js.map (ga.jspm.io)

…dom-
…dom-utils/getViewportRect.js (ga.jspm.io)
utils/getViewportRect.js.map (ga.jspm.io)

…dom-utils/getScrollParent.js (ga.jspm.io) …dom-utils/getScrollParent.js.map (ga.jspm.io)

…dom-utils/getParentNode.js (ga.jspm.io) …dom-utils/getParentNode.js.map (ga.jspm.io)

…dom-utils/getOffsetParent.js (ga.jspm.io) …dom-utils/getOffsetParent.js.map (ga.jspm.io)

…dom-utils/getNodeScroll.js (ga.jspm.io) …dom-utils/getNodeScroll.js.map (ga.jspm.io)

…dom-utils/getNodeName.js (ga.jspm.io) …dom-utils/getNodeName.js.map (ga.jspm.io)

…dom-utils/getLayoutRect.js (ga.jspm.io) …dom-utils/getLayoutRect.js.map (ga.jspm.io)

…dom-
…dom-utils/getHTMLElementScroll.js (ga.jspm.io)
utils/getHTMLElementScroll.js.map (ga.jspm.io)

…dom-
…dom-utils/getDocumentRect.js (ga.jspm.io)
utils/getDocumentRect.js.map (ga.jspm.io)

…dom-
…dom-utils/getDocumentElement.js (ga.jspm.io)
utils/getDocumentElement.js.map (ga.jspm.io)

…dom-
…dom-utils/getComputedStyle.js (ga.jspm.io)
utils/getComputedStyle.js.map (ga.jspm.io)

…dom-
…dom-utils/getCompositeRect.js (ga.jspm.io)
utils/getCompositeRect.js.map (ga.jspm.io)

…_/c7d11060.js (ga.jspm.io) …_/c7d11060.js.map (ga.jspm.io)

about:blank 20/24
19/03/2024, 19:58 about:blank

URL Map URL

…_/bb24ce41.js (ga.jspm.io) …_/bb24ce41.js.map (ga.jspm.io)

…_/b8df2d1e.js (ga.jspm.io) …_/b8df2d1e.js.map (ga.jspm.io)

…_/a9ca29ce.js (ga.jspm.io) …_/a9ca29ce.js.map (ga.jspm.io)

…_/a0ba12d2.js (ga.jspm.io) …_/a0ba12d2.js.map (ga.jspm.io)

…_/7a91f8b9.js (ga.jspm.io) …_/7a91f8b9.js.map (ga.jspm.io)

…_/7742d4ca.js (ga.jspm.io) …_/7742d4ca.js.map (ga.jspm.io)

…_/6a201025.js (ga.jspm.io) …_/6a201025.js.map (ga.jspm.io)

…_/2d19854a.js (ga.jspm.io) …_/2d19854a.js.map (ga.jspm.io)

…_/1ba79728.js (ga.jspm.io) …_/1ba79728.js.map (ga.jspm.io)

…_/084d303b.js (ga.jspm.io) …_/084d303b.js.map (ga.jspm.io)

…dist/stimulus.js (ga.jspm.io) …dist/stimulus.js.map (ga.jspm.io)

localhost 1st Party

/assets/turbo.min-c6325b8….js (localhost) /assets/turbo.min.js-ceaa544….map (localhost)

Unattributable

chrome-
extension://gighmmpiobklfepjocnamgkkbiglidom/vendor/@eyeo/
webext-ad-filtering-solution/content.js

NOT APPLICABLE (2) Hide

Fonts with font-display: optional are preloaded

Preload optional fonts so first-time visitors may use them. Learn more about preloading fonts

Detected JavaScript libraries

All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.

82

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.

CONTENT BEST PRACTICES

Document does not have a meta description

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

Image elements do not have [alt] attributes

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

Failing Elements

img.brand.mt-3

img.avatar__navbar-round

img.mx-2.button__search--icon-position

about:blank 21/24
19/03/2024, 19:58 about:blank

Failing Elements

img.button__icon--filter.me-2

img.button__icon--size.me-2

img.button__logo--size.me-2

img.button__logo--size.button__logo--position.ms-2

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

ADDITIONAL ITEMS TO MANUALLY CHECK (1) Hide

Structured data is valid

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

Run these additional validators on your site to check additional SEO best practices.

PASSED AUDITS (9) Hide

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

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond
delay to user input. Learn more about using the viewport meta tag. TBT

Document has a <title> element

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

Page has successful HTTP status code

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

Links have descriptive text

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Links are crawlable

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

Page isn’t blocked from indexing

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

robots.txt is valid

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

Document has a valid hreflang

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

Document avoids plugins

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

about:blank 22/24
19/03/2024, 19:58 about:blank

NOT APPLICABLE (3) Hide

Document has a valid rel=canonical

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

Document uses legible font sizes

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

Tap targets are sized appropriately

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

PWA
These checks validate the aspects of a Progressive Web App. Learn what
makes a good Progressive Web App.

INSTALLABLE

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 about manifest
installability requirements.

Failure reason

Page has no manifest <link> URL

PWA OPTIMIZED

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 about splash screens.

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 about theming the address bar.

Content is sized correctly for the viewport

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 how to size content for the viewport.

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

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond
delay to user input. Learn more about using the viewport meta tag. TBT

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 about maskable manifest icons.

ADDITIONAL ITEMS TO MANUALLY CHECK (3) Hide

Site works cross-browser

To reach the most number of users, sites should work across every major browser. Learn about cross-browser compatibility.

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 about page transitions.

Each page has a URL

about:blank 23/24
19/03/2024, 19:58 about:blank
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media.
Learn more about providing deep links.

These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect
your score but it's important that you verify them manually.

Captured at Mar 19, 2024, 7:56 Emulated Desktop with Single page session
PM GMT-3 Lighthouse 11.4.0
Initial page load Custom throttling Using Chromium 122.0.0.0 with
devtools

Generated by Lighthouse 11.4.0 | File an issue

about:blank 24/24