Skip to content
https://padlet.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

49

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.

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:43.035 source:map[column:4434 line:6 type:source-location url:https://padlet.net/ui/assets/vue-CASbMAcE.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.928 source:map[column:2137 line:0 type:source-location url:https://padlet.net/ui/assets/window_size-hPQO1gKj.js urlProvider:network]] map[reflowTime:43.035 source:map[column:7716 line:1 type:source-location url:https://padlet.net/ui/assets/LandsideHomeV2Page-DZQfbIKn.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...24.8 KiB18.6 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...24.1 KiB18.1 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...22.4 KiB16.8 KiB
div.-mt-3 > div.flex > div.image-thumbnail-crop-frame > img.beethoven-success div.-mt-3 > div.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_412&url=https%3A%2F%2...20.2 KiB15.9 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...20.7 KiB15.5 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...20.3 KiB15.2 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...18.5 KiB13.9 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...16.0 KiB12.0 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...15.7 KiB11.8 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...15.7 KiB11.8 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...15.4 KiB11.6 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...11.5 KiB8.7 KiB
footer.flex > div.flex > div.image-thumbnail-crop-frame > img.beethoven-success footer.flex > div.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Ch_156%2Cw_2211&url=http...49.5 KiB7.7 KiB
Padlet crane div.flex > div.flex > a.flex > img.crane-icon
padlet.net/logos/padlet_crane_icon.webp5.2 KiB5.1 KiB
ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success ul.w-full > li.flex > div.image-thumbnail-crop-frame > img.beethoven-success
/1/image.webp?t=c_limit%2Cdpr_2%2Cw_326&url=https%3A%2F%2...6.1 KiB4.6 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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: 370 ms 56.4 KiB
URLTransfer SizeEst Savings
padlet.net/ui/assets/tailwind-D-QE9oDO.css57.3 KiB56.4 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 940 ms 168.6 KiB
URLTransfer SizeEst Savings
padlet.net/ui/assets/surface_attachments-BxXKYV3s.js120.0 KiB112.0 KiB
padlet.net/ui/assets/vue-CASbMAcE.js104.1 KiB56.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Other1.6 s
Script Evaluation1.6 s
Style & Layout400 ms
Parse HTML & CSS161 ms
Script Parsing & Compilation68 ms
Rendering27 ms
Garbage Collection15 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Padlet crane div.relative > div.z-landside-header-logo > a.flex > img.crane-icon
padlet.net/logos/padlet_crane_icon.webp
Padlet crane div.flex > div.flex > a.flex > img.crane-icon
padlet.net/logos/padlet_crane_icon.webp

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,273 KiB
●Avoid long main-thread tasks 13 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 200 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 160 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
96

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
Log in div.relative > div.flex > a.no-underline > span.flex-1
Sign up div.relative > div.flex > a.no-underline > span.flex-1
Sign up - it’s free div.flex > div.flex > a.no-underline > span.flex-1
Make a board div.flex > div.flex > a.no-underline > span.flex-1
Explore more div.flex > div.flex > a.no-underline > span.flex-1
Make a sandbox div.flex > div.flex > a.no-underline > span.flex-1
Explore more div.flex > div.flex > a.no-underline > span.flex-1
Sign up for free div.flex > div.flex > a.no-underline > span.flex-1
Product nav.px-2 > button.select-none > div.flex > h2#ProductFooterSectionTitle
Solutions nav.px-2 > button.select-none > div.flex > h2#SolutionsFooterSectionTitle
Support nav.px-2 > button.select-none > div.flex > h2#SupportFooterSectionTitle
Company nav.px-2 > button.select-none > div.flex > h2#CompanyFooterSectionTitle
Legal nav.px-2 > button.select-none > div.flex > h2#LegalFooterSectionTitle
English (US) section > div > button.select-none > span.me-1.5

These are opportunities to improve the legibility of your content.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●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`

Send Feedback