Lighthouse Mobile

· 0 checks — Mobile 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.

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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/signals/config/454624666197363?v=2.9.303&r=stable&domain...	1200.0 s	44.8 KiB
/analytics.js/v1/osFXvgg64wCFCbqGsPDxwNVR11o6fNWB/analyti...	120.0 s	28.8 KiB
consent.cookiebot.com/uc.js	1009.0 s	27.0 KiB
widget.trustpilot.com/trustboxes/53aa8807dec7e10d38f59f32/main.js	86400.0 s	24.7 KiB
widget.trustpilot.com/bootstrap/v5/tp.widget.bootstrap.min.js	86400.0 s	8.1 KiB
/consentconfig/4635c9e1-8a34-42e3-8c59-14c10950505e/fruit...	66251.0 s	951 B
/tr/?id=454624666197363&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	16 B
widget.trustpilot.com/bootstrap/v5/tp.widget.bootstrap.min.js	86400.0 s	0 B

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/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.woff2	75 ms
fonts.gstatic.com/s/droidserif/v20/tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnSGjW7BA.woff2	60 ms
fonts.gstatic.com/s/droidserif/v20/tDbK2oqRg1oM3QBjjcaDkOr4nAfcHi6FRUI.woff2	55 ms
fonts.gstatic.com/s/droidserif/v20/tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwGtT0rU.woff2	45 ms
fonts.gstatic.com/s/droidserif/v20/tDbI2oqRg1oM3QBjjcaDkOr9rAXWGQyH.woff2	40 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: Anstronaut with flying fruits.

path: 3,HTML,1,BODY,1,DIV,1,DIV,1,SECTION,0,DIV,0,DIV,0,DIV,3,DIV,0,IMG

selector: div.padding-global > div.container-large > div.hero_image-home > img

snippet: <img alt="Anstronaut with flying fruits." loading="lazy" src="https://fruits.b-cdn.net/astronaut-fruits-mobile.webp">

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

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
/644288dc40e71417a289a3c2/js/webflow.schunk.bfd3dce119ae4...	40.1 KiB	2.6 s
/644288dc40e71417a289a3c2/js/webflow.schunk.de3387ee41b6f...	13.9 KiB	1.1 s
/644288dc40e71417a289a3c2/css/fruits-website.webflow.shar...	22.9 KiB	1.2 s
ajax.googleapis.com/ajax/libs/webfont/1.6.26/webfont.js	5.9 KiB	1.0 s
/js/jquery-3.5.1.min.dc5e7f18c8.js?site=644288dc40e71417a...	31.0 KiB	2.3 s
/644288dc40e71417a289a3c2/js/webflow.46028795.ae4a0e9776c...	5.1 KiB	935 ms
consent.cookiebot.com/uc.js	27.0 KiB	1.8 s

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
Anstronaut with flying fruits. `div.padding-global > div.container-large > div.hero_light-image > img`	fruits.b-cdn.net/light-accent.webp	11.0 KiB	5.0 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: 801 ms

URL	Time Spent
fruits.co/	801 ms
www.fruits.co/	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 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 29.9 KiB

URL	Transfer Size	Est Savings
/644288dc40e71417a289a3c2/css/fruits-website.webflow.shar...	22.4 KiB	18.7 KiB
	13.5 KiB	11.2 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: 0.0 ms 58.8 KiB

URL	Transfer Size	Est Savings
connect.facebook.net/en_US/fbevents.js	96.5 KiB	33.8 KiB
/4635c9e1-8a34-42e3-8c59-14c10950505e/cc.js?renew=false&r...	102.2 KiB	25.0 KiB

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.

Category	Time Spent
Script Evaluation	988 ms
Other	542 ms
Style & Layout	221 ms
Script Parsing & Compilation	127 ms
Parse HTML & CSS	86 ms
Rendering	70 ms
Garbage Collection	59 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
Anstronaut with flying fruits. `div.padding-global > div.container-large > div.hero_image-home > img`	fruits.b-cdn.net/astronaut-fruits-mobile.webp
Anstronaut with flying fruits. `div.padding-global > div.container-large > div.hero_light-image > img`	fruits.b-cdn.net/light-accent.webp
Heart icon `div.footer-bottom_content > div.vertical-body > div.horizontal-body > img.footer-heart-icon`	/644288dc40e71417a289a3c2/64c94bd4e6396fb77552abe3_heart.svg

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

●Max Potential First Input Delay 110 ms

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,333 KiB

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 9 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 140 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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
More TLDs `div.container-large > div.section-component > div.flexbox-centered > a.text-link-orange`
Sell with fruits `div.padding-xhuge > div.section-component > div.top-seller_wrapper > a.button`

These are opportunities to improve the legibility of your content.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.form-block > form#wf-form-Domain-Search > div.submit-button_wrapper > input.query-button `div.form-block > form#wf-form-Domain-Search > div.submit-button_wrapper > input.query-button`

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.footer-bottom_content-wrapper > div.footer-bottom_content > div.vertical-body > a.footer-brand-link `div.footer-bottom_content-wrapper > div.footer-bottom_content > div.vertical-body > a.footer-brand-link`

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.

○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

●Form elements have associated labels

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

●`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

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

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

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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●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

○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

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

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

○Links are distinguishable without relying on color.

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

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

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

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

○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

User Experience

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
Anstronaut with flying fruits. `div.padding-global > div.container-large > div.hero_light-image > img`	fruits.b-cdn.net/light-accent.webp	412 x 232	257 x 145	618 x 348

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 / Warning	Source
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 769

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.

Source	Description
tag.clearbitscripts.com/v1/pk_bf22e96a38606e242bb2ddf3d24a478c/tags.js	`Failed to load resource: the server responded with a status of 404 ()`

●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

●Page has the HTML doctype

●Properly defines charset

●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

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.

Link destination	Link Text
www.fruits.co/explore/for-buyer	Learn more

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`