Skip to content
https://freepik.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.

39

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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:70.26 source:map[type:text value:[unattributed]]]]

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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
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

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
Learn more, Upscale an image up to 10K a.group > div.relative > picture > img.size-full
/home/anon-rvmp/features/images/upscale-main.webp?w=526&h...76.1 KiB63.2 KiB
card image div.keen-slider__slide > div.relative > picture > img.size-full
cdn-front.freepik.com/home/anon-rvmp/work/localize-campaigns-2x.webp?w=526&h=60038.8 KiB28.8 KiB
card image a.keen-slider__slide > div.relative > picture > img.size-full
/home/anon-rvmp/creative-suite/social-media/social-post.w...34.8 KiB25.0 KiB
card image div.keen-slider__slide > div.relative > picture > img.size-full
/home/anon-rvmp/work/create-product-visuals-2x.webp?w=526...33.6 KiB23.6 KiB
card image a.keen-slider__slide > div.relative > picture > img.size-full
/home/anon-rvmp/creative-suite/social-media/usecase-resiz...30.6 KiB21.9 KiB
Learn more, Find high-quality images a.group > div.relative > picture > img.size-full
cdn-front.freepik.com/home/anon-rvmp/features/images/find-main.webp?w=526&h=60027.8 KiB20.6 KiB
card image div.keen-slider__slide > div.relative > picture > img.size-full
/home/anon-rvmp/work/videos-visual-prompt-2x.webp?w=526&h...30.4 KiB20.4 KiB
Learn more, Chat with AI to transform images a.group > div.relative > picture > img.size-full
/home/anon-rvmp/features/images/aiassistant-main.webp?w=5...27.4 KiB20.4 KiB
Learn more, Edit an image a.group > div.relative > picture > img.size-full
/home/anon-rvmp/features/images/edit-an-image-main.webp?w...26.9 KiB20.0 KiB
card image a.keen-slider__slide > div.relative > picture > img.size-full
/home/anon-rvmp/creative-suite/social-media/on-brand.webp...25.9 KiB18.6 KiB
Image Extender div.relative > a.block > picture > img.absolute
/home/anon-rvmp/hero-gallery/image-extender.webp?w=648&h=26021.2 KiB17.4 KiB
Image Generator div.relative > a.block > picture > img.absolute
/home/anon-rvmp/hero-gallery/image-generator-2.webp?w=862...22.4 KiB17.4 KiB
Learn more, Create on-brand AI images a.group > div.relative > picture > img.size-full
/home/anon-rvmp/features/images/onbrand-images-2.webp?w=5...23.0 KiB17.1 KiB
Clip Editor div.relative > a.block > picture > img.absolute
cdn-front.freepik.com/home/anon-rvmp/hero-gallery/clip-editor.webp?w=648&h=26017.2 KiB13.4 KiB
Music Generator div.relative > a.block > picture > img.absolute
/home/anon-rvmp/hero-gallery/music-generator.webp?w=378&h...11.4 KiB7.1 KiB
Speak div.relative > a.block > picture > img.absolute
cdn-front.freepik.com/home/anon-rvmp/hero-gallery/voiceover.webp?w=378&h=26012.7 KiB4.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: 802 ms
URLTime Spent
freepik.com/802 ms
www.freepik.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

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

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
Script Evaluation3.2 s
Other1.2 s
Style & Layout567 ms
Script Parsing & Compilation374 ms
Garbage Collection137 ms
Rendering131 ms
Parse HTML & CSS119 ms

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 18.3 KiB
URLTransfer SizeEst Savings
21.9 KiB18.3 KiB

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 12 user timings
●Avoid long main-thread tasks 19 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 130 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 60 ms
○INP breakdown
○Avoid large layout shifts
89

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
Get started for free main.dark > div.mx-auto > div.flex > a.flex
Products div.pb-12 > div.grid > div.mb-2 > button.flex
Get started div.pb-12 > div.grid > div.mb-2 > button.flex
Company div.pb-12 > div.grid > div.mb-2 > button.flex
Get in touch div.pb-12 > div.grid > div.flex > span.w-full

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.grid > div.flex > div.flex > a.flex div.grid > div.flex > div.flex > a.flex
div.grid > div.flex > div.flex > a.flex div.grid > div.flex > div.flex > a.flex
div.grid > div.flex > div.flex > a.flex div.grid > div.flex > div.flex > a.flex
div.grid > div.flex > div.flex > a.flex div.grid > div.flex > div.flex > a.flex
div.grid > div.flex > div.flex > a.flex div.grid > div.flex > div.flex > a.flex
div.grid > div.flex > div.flex > a.flex div.grid > div.flex > div.flex > a.flex
div.grid > div.flex > div.flex > a.flex div.grid > div.flex > div.flex > a.flex
div.grid > div.flex > div.flex > a.flex div.grid > div.flex > div.flex > a.flex

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

Best practices

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta.jsx-3961720867 head > meta.jsx-3961720867

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[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
●`[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
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.
Failed to load resource: the server responded with a status of 400 ()
Not signed in with the identity provider.
●Uses HTTPS
●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 issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
92

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback