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.

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:53.271 source:map[type:text value:[unattributed]]] map[reflowTime:0.487 source:map[column:86058 line:18 type:source-location url:https://js.hs-analytics.net/analytics/1776896400000/21774584.js urlProvider:network]]]

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

value: No additional origins are good candidates for preconnecting

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
js.hs-analytics.net/analytics/1776896400000/21774584.js	300.0 s	42.3 KiB
js.usemessages.com/conversations-embed.js	600.0 s	33.0 KiB
js.hubspot.com/web-interactives-embed.js	600.0 s	28.5 KiB
js.hs-banner.com/v2/21774584/banner.js	300.0 s	24.1 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
js.hsadspixel.net/pixels.js	600.0 s	3.9 KiB
script.crazyegg.com/pages/scripts/0071/0991.js	300.0 s	2.7 KiB
cdn.firstpromoter.com/fpr.js	0.0 ms	2.5 KiB
js.hs-scripts.com/21774584.js	90.0 s	1.1 KiB
/collect?v=2&fmt=js&pid=1201353&time=1776896587097&li_ads...	0.0 ms	271 B
dashboard.visme.co/register-visme3.js	691200.0 s	2.5 KiB

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.

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
Collaboration `div.col-lg-4 > div.bg-white > picture.d-block > img.br-12`	www.visme.co/wp-content/themes/visme/images/2022/teams/hp-team-1.webp	75.5 KiB	60.8 KiB
div.visme-video-hero > div.visme-video-hero__video-wrapper > picture > img.visme-video-hero__preview `div.visme-video-hero > div.visme-video-hero__video-wrapper > picture > img.visme-video-hero__preview`	www.visme.co/wp-content/themes/visme/images/2022/hero/homepage/video-preview.jpg	51.3 KiB	34.9 KiB
Precise communication `div.col-lg-4 > div.bg-white > picture.d-block > img.br-12`	www.visme.co/wp-content/themes/visme/images/2022/teams/hp-team-2.webp	26.8 KiB	7.6 KiB
Asset management `div.col-lg-4 > div.bg-white > picture.d-block > img.br-12`	www.visme.co/wp-content/themes/visme/images/2022/teams/hp-team-3.webp	25.3 KiB	6.1 KiB
div.flickity-viewport > div.flickity-slider > div.visme-companies-slider-item > div.visme-companies-slider-item-logo `div.flickity-viewport > div.flickity-slider > div.visme-companies-slider-item > div.visme-companies-slider-item-logo`	www.visme.co/wp-content/themes/visme/images/partners/florida-panthers.png	12.6 KiB	5.3 KiB
div.flickity-viewport > div.flickity-slider > div.visme-companies-slider-item > div.visme-companies-slider-item-logo `div.flickity-viewport > div.flickity-slider > div.visme-companies-slider-item > div.visme-companies-slider-item-logo`	www.visme.co/wp-content/themes/visme/images/partners/denver-broncos.png	12.2 KiB	4.9 KiB
li.visme-types__item > a.visme-types__link > div.visme-type__wrapper > div.visme-type__thumb `li.visme-types__item > a.visme-types__link > div.visme-type__wrapper > div.visme-type__thumb`	www.visme.co/wp-content/themes/visme/images/2024/homepage/data.png	6.4 KiB	4.3 KiB
li.visme-types__item > a.visme-types__link > div.visme-type__wrapper > div.visme-type__thumb `li.visme-types__item > a.visme-types__link > div.visme-type__wrapper > div.visme-type__thumb`	www.visme.co/wp-content/themes/visme/images/2024/homepage/whiteboards.png	6.1 KiB	4.0 KiB

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
www.visme.co/wp-content/themes/visme/css/bs/bootstrap.min.css	11.3 KiB
www.visme.co/wp-content/themes/visme/build/homepage6/homepage6.bundle.min.css	6.0 KiB
www.visme.co/wp-content/plugins/litespeed-cache/assets/css/litespeed-dummy.css	476 B
www.visme.co/wp-content/themes/visme/css/style-live-footer.css	2.7 KiB
www.visme.co/wp-content/themes/visme/build/homepage6/homepage6.critical.min.css	3.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: 205 ms

URL	Time Spent
visme.co/	205 ms
www.visme.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

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	779 ms
Other	624 ms
Style & Layout	388 ms
Rendering	122 ms
Script Parsing & Compilation	97 ms
Parse HTML & CSS	28 ms
Garbage Collection	13 ms

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
The page has an unload handler in a sub frame.	Actionable

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 245.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=AW-1053096647&cx=c&gtm=4e64k1	144.4 KiB	105.9 KiB
www.googletagmanager.com/gtag/js?id=G-QXSBG5DLSV	177.2 KiB	58.2 KiB
www.googletagmanager.com/gtag/js?id=AW-1053096647	144.3 KiB	55.6 KiB
/pages/versioned/commontransformations-scripts/df70602680...	71.7 KiB	25.2 KiB

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

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●User Timing marks and measures 15 user timings

●JavaScript execution time 0.7 s

●Avoid long main-thread tasks 3 long tasks found

●Avoid non-composited animations 3 animated elements found

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

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 270 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP request discovery

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
“In this digital age, social media is playing an increasingly larger role in th… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“At the Broncos, we recommend Visme to other teams, brands, or organizations lo… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“We use Visme not just for reporting but also for engaging our stakeholders and… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“The hours saved each month from meeting time, working back and forth between t… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“It’s easy to create something in Visme quickly that looks like we sent it out … `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“I absolutely recommend Visme due to its dynamic functionality and ability to i… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“Visme is something that I would highly recommend. It made us look a lot better… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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 Free `nav.v-nav > ul.v-actions > li.v-action > button.v-action-btn`
CASE STUDIES `main.has-sticky-menu > section.pt-5 > div.container > p.user-select-none`
Read this case study `div > div.visme-testimonial-slider__slide-author > p.ps-1 > a.visme-testimonial-slider__slide-button`
FEATURES `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
TEAMWORK `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
CREATE FROM A TO Z `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
SOLUTIONS FOR EVERYONE `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
INTEGRATIONS `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
CREATE `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
USE CASES `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
RESOURCES `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
COMPANY `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
SUPPORT `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
RECENT FEATURES & ARTICLES `footer.footer-21-v1 > div.footer-container > div.block-blog-container > strong.heading`
Copyright 2026 Easy WebContent, LLC. (DBA Visme). All rights reserved. Proudly … `footer.footer-21-v1 > div.footer-container > div.block-menus-container > p.copyright`

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-*]` attributes match their roles

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

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

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

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

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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

○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.googleadservices.com/pagead/conversion_async.js line 31, col 421

●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

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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

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.visme.co/templates/	More
www.visme.co/graph-maker/	Learn more
www.visme.co/templates/	Learn more
www.visme.co/brand-design-tool/	Learn more
www.visme.co/social-media-scheduler/	Learn more
www.visme.co/icon-finder/	Learn more
www.visme.co/animation-interactivity/	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`