Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	40 ms
/v2/styles/font/OpenSans-Semibold.woff2?browser=CHROME&su...	5.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: img_"hand_roy"

path: 1,HTML,1,BODY,2,DIV,0,DIV,0,DIV,0,DIV,1,DIV,14,DIV,0,IMG

selector: div.animation-container > div.animation-scene > div#hand_roy > img.asset-with-shadow

snippet: <img class="asset-with-shadow" alt="img_"hand_roy"" src="https://cdn2.pearltrees.com/v2/asset/home/single/hand_right.png?230fd">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
934452450b66.edge.sdk.awswaf.com/934452450b66/c4b8876d5ebf/challenge.js	501.5 KiB	863 ms
ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js	32.8 KiB	386 ms
fonts.googleapis.com/css?family=Roboto	1.9 KiB	267 ms
www.google.com/recaptcha/api.js?render=6LdRbaMUAAAAAG73QO2jGZaDyi3rSWYU2fY84ghz	1.0 KiB	305 ms
/ajax/libs/jquery.waitforimages/1.5.0/jquery.waitforimage...	1.2 KiB	268 ms
cdn.pearltrees.com/v2static/js/home/signForm.js?20260420-19h14-10464	8.4 KiB	80 ms
cdn.pearltrees.com/v2/vendor/jquery.placeholder.js	1.4 KiB
cdn.pearltrees.com/v2/vendor/jquery.validate.min.js?20260420-19h14-10464	6.6 KiB
cdn.pearltrees.com/v2/vendor/bootstrap/css/bootstrap.min.css	17.1 KiB	284 ms
/v2static/css/homev2/homeSignFormsStyle.css?20260420-19h1...	5.1 KiB
cdn.pearltrees.com/v2static/css/homev2/homePageStyle.css?20260420-19h14-10464	3.3 KiB
cdn.pearltrees.com/v2/bower_components/modernizr/modernizr.js	4.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
img_"banksy_street" `div.animation-container > div.animation-scene > div#banksy_street > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/banksy_street.png?6a706	50.3 KiB	47.9 KiB
img_"note" `div.animation-container > div.animation-scene > div#note > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/note.png?b0c72	47.9 KiB	45.6 KiB
img_"origami" `div.animation-container > div.animation-scene > div#origami > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/origami.png?e40c9	40.9 KiB	38.5 KiB
img_"city_night" `div.animation-container > div.animation-scene > div#city_night > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/city_night.png?9c3cc	40.5 KiB	38.1 KiB
img_"city" `div.animation-container > div.animation-scene > div#city > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/city.png?0e7aa	39.4 KiB	37.1 KiB
img_"calligraphic" `div.animation-container > div.animation-scene > div#calligraphic > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/calligraphic.png?e87a5	33.1 KiB	30.8 KiB
img_"roa_street" `div.animation-container > div.animation-scene > div#roa_street > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/roa_street.png?5d2b3	32.3 KiB	29.9 KiB
img_"bike" `div.animation-container > div.animation-scene > div#bike > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/bike.png?d7bec	31.8 KiB	29.5 KiB
img_"roy_lichtenstein" `div.animation-container > div.animation-scene > div#roy_lichtenstein > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/plane.png?7b0f1	34.1 KiB	28.9 KiB
img_"jazz" `div.animation-container > div.animation-scene > div#jazz > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/jazz.png?2974f	30.5 KiB	28.2 KiB
img_"NY" `div.animation-container > div.animation-scene > div#NY > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/NY.png?e9873	22.0 KiB	19.6 KiB
img_"white_rabbit" `div.animation-container > div.animation-scene > div#white_rabbit > img.asset-with-shadow`	cdn2.pearltrees.com/v2/asset/home/single/white_rabbit.png?c71ee	20.1 KiB	14.8 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 455 ms

URL	Time Spent
pearltrees.com/	265 ms
www.pearltrees.com/	190 ms
www.pearltrees.com/	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 410 ms 452.1 KiB

URL	Transfer Size	Est Savings
934452450b66.edge.sdk.awswaf.com/934452450b66/c4b8876d5ebf/challenge.js	501.1 KiB	243.8 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	177.0 KiB
cdn.pearltrees.com/v2/app/config-no-jquery.20260420-19h14-10464.js	58.5 KiB	31.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 17.6 KiB

URL	Transfer Size	Est Savings
cdn.pearltrees.com/v2/app/config-no-jquery.20260420-19h14-10464.js	58.6 KiB	11.6 KiB
cdn2.pearltrees.com/v2/app/home/mainhome.js?v=20260420-19h14-10464	49.6 KiB	6.0 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 16.3 KiB

URL	Transfer Size	Est Savings
cdn.pearltrees.com/v2/vendor/bootstrap/css/bootstrap.min.css	16.6 KiB	16.3 KiB

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

●Max Potential First Input Delay 100 ms

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 2,154 KiB

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.2 s

●Avoid long main-thread tasks 2 long tasks found

●Avoid non-composited animations 9 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 40 ms

●Avoid large layout shifts 15 layout shifts found

○INP breakdown

○User Timing marks and measures

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.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About Pearltrees `div#footer-container-placeholder > div#footer-container-placeholder-inner > footer > a#first_footer_link`
About Pearltrees AI `div#footer-container-placeholder > div#footer-container-placeholder-inner > footer > a.link`
iOS app `div#footer-container-placeholder > div#footer-container-placeholder-inner > footer > a.not_in_space`
Android app `div#footer-container-placeholder > div#footer-container-placeholder-inner > footer > a.link`
Contact `div#footer-container-placeholder > div#footer-container-placeholder-inner > footer > a.link`
Popular `div#footer-container-placeholder > div#footer-container-placeholder-inner > footer > a.link`
Privacy policy `div#footer-container-placeholder > div#footer-container-placeholder-inner > footer > a.link`
Terms of service `div#footer-container-placeholder > div#footer-container-placeholder-inner > footer > a.link`
FAQs `div#footer-container-placeholder > div#footer-container-placeholder-inner > footer > a#last_footer_link`
Add and transform your content with Pearltrees AI `div.left-container > div.animation-container > div.animation-scene > div#message2`
Organize everything `div.right-container > div#logo-container > div#logoText > span`
Create your account `div.signup_page > div#form_header > div.fh_title > span.text-with-shadow`
Log in `div.from_button_container > div.from_button_container_right > div.form_change > span.form_button_with_over`
Pearltrees Premium `div.signup_page > div#b2b_footer > div#premium_button > a.form_button_b2b`
Pearltrees Education `div.signup_page > div#b2b_footer > div#education_button > a.form_button_b2b`
Manuels Ouverts `div.signup_page > div#b2b_footer > div#manuels_ouverts_button > a.form_button_b2b`
It's quick and it's free `div.right-container > div#signin-container > div#explain_footer > div.signup_page`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

●`[role]` values are valid

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

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

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○`[role]`s are contained by their required parent element

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

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

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○Heading elements appear in a sequentially-descending order

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

○Input buttons have discernible text.

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

○Links are distinguishable without relying on color.

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

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

Best Practices

Trust and Safety

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
www.pearltrees.com/	Allowed

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`