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
/static.vecteezy.com/system/resources/previews/002/905/17...	0.0 ms	40.2 KiB
widget.trustpilot.com/trustboxes/53aa8807dec7e10d38f59f32/main.js	86400.0 s	27.4 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
cdn.speedcurve.com/js/lux.js?id=4230272118	3600.0 s	11.3 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
widget.trustpilot.com/bootstrap/v5/tp.widget.bootstrap.min.js	86400.0 s	8.1 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	0 B
/static.vecteezy.com/system/resources/previews/002/905/17...	0.0 ms	0 B
/static.vecteezy.com/system/resources/previews/002/905/17...	0.0 ms	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.

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

value: No additional origins are good candidates for preconnecting

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: 805 ms

URL	Time Spent
vecteezy.com/	805 ms
www.vecteezy.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.

Estimated savings: 220 ms 567.9 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	241.8 KiB
g.vecteezy.com/gtag/js?id=G-NPD8287EHK&cx=c&gtm=4e64h1	218.8 KiB	88.2 KiB
/gtm.js?id=GTM-5WKDQHJ&gtm_auth=27tsf_LMzUbKAlIWPPQ6dg&gt...	199.2 KiB	82.5 KiB
accounts.google.com/gsi/client	95.6 KiB	71.7 KiB
www.googletagmanager.com/gtag/destination?id=AW-961015877&cx=c&gtm=4e64h1	144.9 KiB	61.4 KiB
static.vecteezy.com/vite/assets/init-turbo-B6lBEHaH-1.js	26.6 KiB	22.2 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.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	1.4 s	302 ms	0.0 ms
www.vecteezy.com/	704 ms	98 ms	13 ms
static.vecteezy.com/vite/assets/stimulus-helpers-Bg5ApOVk-1.js	664 ms	652 ms	0.1 ms
static.vecteezy.com/vite/assets/fp-BNLdf16n-1.js	282 ms	167 ms	0.2 ms
g.vecteezy.com/gtag/js?id=G-NPD8287EHK&cx=c&gtm=4e64h1	226 ms	188 ms	35 ms
www.googletagmanager.com/gtag/destination?id=AW-961015877&cx=c&gtm=4e64h1	221 ms	177 ms	42 ms
scripts.clarity.ms/0.8.59/clarity.js	188 ms	174 ms	6.9 ms
/gtm.js?id=GTM-5WKDQHJ&gtm_auth=27tsf_LMzUbKAlIWPPQ6dg&gt...	176 ms	132 ms	38 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	166 ms	86 ms	80 ms
static.vecteezy.com/vite/assets/stimulus-Cq41p_up-1.js	162 ms	110 ms	0.3 ms
static.vecteezy.com/vite/assets/init-turbo-B6lBEHaH-1.js	86 ms	70 ms	0.4 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	62 ms	41 ms	5.5 ms

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	2.7 s
Other	1.4 s
Style & Layout	416 ms
Script Parsing & Compilation	267 ms
Parse HTML & CSS	182 ms
Garbage Collection	87 ms
Rendering	39 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/static.vecteezy.com/system/resources/previews/002/905/17...	1.6 MiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
g.vecteezy.com/gtag/js?id=G-NPD8287EHK&cx=c&gtm=4e64h1	219.2 KiB
/gtm.js?id=GTM-5WKDQHJ&gtm_auth=27tsf_LMzUbKAlIWPPQ6dg&gt...	199.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-961015877&cx=c&gtm=4e64h1	145.4 KiB
www.vecteezy.com/	133.8 KiB
accounts.google.com/gsi/client	96.4 KiB
/static.vecteezy.com/system/resources/previews/002/905/17...	40.2 KiB
widget.trustpilot.com/trustboxes/53aa8807dec7e10d38f59f32/main.js	27.4 KiB
static.vecteezy.com/vite/assets/init-turbo-B6lBEHaH-1.js	27.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

●Forced reflow

●Improve image delivery

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 15 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 120 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○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
Sign Up `div.ez-site-header__session-nav > form.button_to > button#session_nav_btn_sign_up > span.ez-site-header__menu-item--sign-up__text`
section.home-landing__why-vecteezy > div.home-landing__why-vecteezy__reasons > div.home-landing__why-vecteezy__reason > div.home-landing__why-vecteezy__text `section.home-landing__why-vecteezy > div.home-landing__why-vecteezy__reasons > div.home-landing__why-vecteezy__reason > div.home-landing__why-vecteezy__text`
div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature `div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature`
div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature `div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature`
div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature `div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature`
div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature `div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature`
div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature `div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature`
div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature `div.unlock-vecteezy__content > div.unlock-vecteezy__body > ul.unlock-vecteezy__features > li.unlock-vecteezy__feature`
body.homepage-index > div.home-landing__wrapper > div.home-landing__creator-community > h3.home-landing__creator-community__subheader `body.homepage-index > div.home-landing__wrapper > div.home-landing__creator-community > h3.home-landing__creator-community__subheader`
a.home-landing__creator-community__creator-grid__item > div.home-landing__creator-community__creator-grid__item__bottom > div.home-landing__creator-community__creator-grid__item__bottom__username-resources > em.home-landing__creator-community__creator-grid__item__bottom__resource-count `a.home-landing__creator-community__creator-grid__item > div.home-landing__creator-community__creator-grid__item__bottom > div.home-landing__creator-community__creator-grid__item__bottom__username-resources > em.home-landing__creator-community__creator-grid__item__bottom__resource-count`
a.home-landing__creator-community__creator-grid__item > div.home-landing__creator-community__creator-grid__item__bottom > div.home-landing__creator-community__creator-grid__item__bottom__username-resources > em.home-landing__creator-community__creator-grid__item__bottom__resource-count `a.home-landing__creator-community__creator-grid__item > div.home-landing__creator-community__creator-grid__item__bottom > div.home-landing__creator-community__creator-grid__item__bottom__username-resources > em.home-landing__creator-community__creator-grid__item__bottom__resource-count`

These are opportunities to improve the legibility of your content.

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All Images Photos PNGs PSDs SVGs Templates Vectors Videos Motion Graphics Edito… `div.ez-layout__inner-col > form.ez-search-form > div.ez-search-form__wrapper > div.inline-filters`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.home-landing__why-vecteezy > div.home-landing__why-vecteezy__reasons > div.home-landing__why-vecteezy__reason > h4.home-landing__why-vecteezy__header `section.home-landing__why-vecteezy > div.home-landing__why-vecteezy__reasons > div.home-landing__why-vecteezy__reason > h4.home-landing__why-vecteezy__header`
Our Network `div.footer-primary-nav > div.primary-nav-menu > div.primary-nav-menu__header-wrap > h4.primary-nav-menu__header`

These are opportunities to improve keyboard navigation in your application.

Tables and lists

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Popular: Background 67 Happy Birthday Flowers Mother's Day `section.home-masthead > div.ez-layout__inner-col > div.trending-searches > ul.trending-searches__links`
Portrait of laughing little girl and her mother having fun together at home pho… `div.featured-grid-section > div.ez-layout__inner-col > section#home-featured-grid--0 > ul#grid7062`
Mother holding two children on Mother's Day vector `div.featured-grid-section > div.ez-layout__inner-col > section#home-featured-grid--1 > ul#grid5842`
Minimalist User Interface with Glass Morphism Style vector `div.featured-grid-section > div.ez-layout__inner-col > section#home-featured-grid--2 > ul#grid5013`
div.home-landing__wrapper > section.home-landing__section > div.trusted-by-component__trusted-by > ul.trusted-by-component__trusted-by__logos `div.home-landing__wrapper > section.home-landing__section > div.trusted-by-component__trusted-by > ul.trusted-by-component__trusted-by__logos`

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

Best practices

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms of Use `div.brand-details-component__info > ul.brand-details-component__legal-items > li.brand-details-component__legal-item > a`
Privacy Policy `div.brand-details-component__info > ul.brand-details-component__legal-items > li.brand-details-component__legal-item > a`
Fair Use Policy `div.brand-details-component__info > ul.brand-details-component__legal-items > li.brand-details-component__legal-item > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

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

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

●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

●Links have a discernible name

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

●Deprecated ARIA roles were not used

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

●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-hidden="true"]` elements do not contain focusable descendents

○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

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

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

○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

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	www.googletagmanager.com/gtag/destination?id=AW-961015877&cx=c&gtm=4e64h1 line 599, col 244

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
	`A bad HTTP response code (403) was received when fetching the script.`
aplo-evnt.com/api/v1/intent_pixel/track_request?app_id=69d0175dc05a5400115a5d45	`Failed to load resource: the server responded with a status of 400 ()`
www.vecteezy.com/	`Not signed in with the identity provider.`

●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 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 DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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.

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
MoreExpand more navigation `div.ez-site-header__inner > div.explore-nav > span.ez-drop-down__title > a.ez-drop-down__title__link`

To appear in search results, crawlers need access to your app.

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid