Skip to content
Audit Complete

Results for https://webs.com

Visit site
SaaS / Software · estimated Tracking: signups
Spain Spain · Madrid Completed: Apr 21, 2026 19:20 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Room to improve — your 29.6s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Google Search Console · 3592 peers
You 72
·
Avg 73
At average
0 50 100
Better than 33% of Google Search Console sites See full Google Search Console benchmark →
Google Workspace · 1679 peers
You 72
·
Avg 73
At average
0 50 100
Better than 25% of Google Workspace sites See full Google Workspace benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

Page weighs 11.7 MB (3.9 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › 404 Error Page
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwebs.com)](https://beavercheck.com/results/bca62384-00cc-4e1e-8f04-1ddb04b9a975)
<a href="https://beavercheck.com/results/bca62384-00cc-4e1e-8f04-1ddb04b9a975"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwebs.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwebs.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 29.6s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 29.6s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~28%.

Speed (2)

Page takes 29.6s to load

+12% bounce

Users abandon at ~3s — you're 27.1s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 3.3s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (1)

1 broken link(s) on the page

+2% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$500 investment → $0.99/month returns

Payback period: > 2 years First-year ROI: -98%

Investment

$500

5h · 5 findings

Monthly returns

$0.99 /mo

~$12 / year

  • Bandwidth savings $0.99

Regulatory risk avoided

No applicable regulations in this jurisdiction

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$0.99 / month at risk

~$12 / year if left unfixed

Bandwidth Waste

$0.99 /mo

12321.0 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.2 MB per page load
    Saves $0.99/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

26
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
97
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
58
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

12.25 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

29.57 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.27 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

12.25 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

33.12 s

Detailed Report

Audit breakdown by category with detailed findings.

26

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

RequestCache TTLTransfer Size
cdn.quantummetric.com/qscripts/quantum-vistaprint.js300.0 s138.7 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
fe-assets.workmagic.io/pixel/latest/wm.min.js1800.0 s83.9 KiB
cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_01f9dc8d10300.0 s49.3 KiB
/signals/config/1050145865347054?v=2.9.303&r=stable&domai...1200.0 s46.3 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
b-code.liadm.com/a-051j.min.js86400.0 s45.9 KiB
/swan/v3/fonts/tiempos-regular2.e4e5aee576677174d2fbcddb1...86400.0 s38.7 KiB
/swan/v3/fonts/graphic_regular2.7c96db81b23a97fd67cbeb7e7...86400.0 s36.1 KiB
/swan/v3/fonts/graphic_medium2.3829398551b96ac319a4812246...86400.0 s34.9 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms12.3 KiB
evs.dcp.vpdcp.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js0.0 ms9.5 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
ct.pinterest.com/static/ct/token_create.js7200.0 s3.9 KiB
cdn.veritonic.com/static/vpr.min.js0.0 ms2.7 KiB
s.pinimg.com/ct/lib/main.10d2511a.js1209600.0 s27.6 KiB
/next-integrations/actions/algolia-plugins/cb031e19c7ec5e...0.0 ms2.5 KiB
tags.creativecdn.com/Sou99GdoKN3iP18UHlb8.js3600.0 s2.7 KiB
cdn.attn.tv/vp/dtag.js120.0 s2.1 KiB
cdn.attn.tv/growth-tag-assets/client-configs/Vkc.js120.0 s2.0 KiB
s.pinimg.com/ct/core.js7200.0 s2.1 KiB
js.adsrvr.org/universal_pixel.js0.0 ms935 B
/collect?v=2&fmt=js&pid=1245164&time=1776799177571&url=ht...0.0 ms912 B
/rp.gif?ts=1776799177563&id=t2_he8iaecu&event=PageVisit&m...0.0 ms666 B
www.vistaprint.com/swan/v3/icons/polish.f96d8f23d25c94848faad3002d02b45e.svg86400.0 s1.6 KiB
/swan/v3/icons/guaranteed_satisfaction.f5e5ab2db7017b2604...86400.0 s1.3 KiB
www.vistaprint.com/swan/v3/icons/phone.e2d8fff5c99f40dc6096bc97d3c2e04b.svg86400.0 s1.2 KiB
js.adsrvr.org/universal_pixel.js0.0 ms442 B
www.vistaprint.com/swan/v3/icons/live_chat.0c91b22f94451864870cbcfb132e04d6.svg86400.0 s976 B
/swan/v3/icons/browse_designs.b4620fac13a93ee4c9d6e812951...86400.0 s933 B
d7pet6vgg99z9.cloudfront.net/JS-build/en-us/ca-controller-production-en-us.js0.0 ms354 B
/swan/v3/icons/work_with_a_pro.54f00512b71a6a5080a43705e0...86400.0 s864 B
www.vistaprint.com/swan/v3/icons/search.0ed88af2d9772071041f88a0eb491cc0.svg86400.0 s781 B
/swan/v3/icons/arrow_right.7e7f4793540a01cdedae0eb039b23b...86400.0 s767 B
www.vistaprint.com/swan/v3/icons/check.f40333dc3e38ee20800b3d79994563c7.svg86400.0 s719 B
/swan/v3/styles/field-set.d41d8cd98f00b204e9800998ecf8427...86400.0 s581 B
/swan/v3/styles/pricing.d41d8cd98f00b204e9800998ecf8427e....86400.0 s457 B
/swan/v3/styles/button.d41d8cd98f00b204e9800998ecf8427e.m...86400.0 s427 B
www.vistaprint.com/swan/v3/styles/icon.d41d8cd98f00b204e9800998ecf8427e.min.css86400.0 s256 B
/tr/?id=1050145865347054&ev=PageView&dl=https%3A%2F%2Fwww...0.0 ms19 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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:352.646 label:Time to first byte subpart:timeToFirstByte] map[duration:45.941 label:Resource load delay subpart:resourceLoadDelay] map[duration:79.939 label:Resource load duration subpart:resourceLoadDuration] map[duration:2052.283 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: A smiling woman in branded Gym Sisters workout gear, alongside the Gym Sisters …
path: 1,HTML,1,BODY,1,MAIN,0,DIV,7,DIV,2,DIV,0,DIV,0,DIV,0,IMG
selector: div.swan-banner > div.swan-banner-image-container > div.swan-banner-image > img.swan-fluid-image
snippet: <img alt="A smiling woman in branded Gym Sisters workout gear, alongside the Gym Sis…" srcset="https://cms.cloudinary.vpsvc.com/image/upload/w_320/f_avif/q_auto/v1741353…" src="https://cms.cloudinary.vpsvc.com/image/upload/w_768/f_avif/q_auto/v1741353…" sizes="(max-width: 768px) 100vw, (max-width: 2840px) 50vw, …" loading="eager" fetchpriority="high" class="swan-fluid-image">

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.

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
Get found on Yelp promo background image div.swan-banner > div.swan-banner-image-container > div.swan-banner-image > img.swan-fluid-image
/image/upload/f_auto/q_auto/v1756719037/digital/partners/...242.1 KiB234.1 KiB
Vista x Wix Domain name div.swan-visible-xs > div.swan-banner-image-container > div.swan-banner-image > img.swan-fluid-image
/image/upload/w_768/f_avif/q_auto/v1670452392/digital/par...71.9 KiB56.6 KiB
A smiling woman in branded Gym Sisters workout gear, alongside the Gym Sisters … div.swan-banner > div.swan-banner-image-container > div.swan-banner-image > img.swan-fluid-image
/image/upload/w_768/f_avif/q_auto/v1741353552/digital/par...37.5 KiB30.4 KiB
Woman in branded Pom Pom t-shirt, with pink and yellow website, mobile, and soc… div.swan-grid-container > div.swan-row > div.swan-col-12 > img.swan-fluid-image
/image/upload/w_768/f_avif/q_auto/v1739267791/digital/par...37.9 KiB28.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

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

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 6.7 s 1.2 MiB
URLTransfer SizeEst Savings
/assets/ubik/web/@vp/chatbot-ui/1.0.66/lib/web/systemjs/c...183.0 KiB119.9 KiB
/assets/ubik/web/@vp/swan/3.34.0/systemjs/web/systemjs/sw...166.7 KiB101.9 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js109.2 KiB84.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-PKH9B2B&gtm=4e64k0h2149.6 KiB79.2 KiB
www.googletagmanager.com/gtag/js?id=G-3TW2S49QDP&cx=c&gtm=4e64k0h2169.2 KiB64.4 KiB
www.googletagmanager.com/gtag/js?id=DC-9815365&cx=c&gtm=4e64k0h2129.9 KiB60.4 KiB
www.googletagmanager.com/gtag/js?id=DC-14876881&cx=c&gtm=4e64k0h2129.7 KiB60.2 KiB
www.googletagmanager.com/gtag/js?id=AW-620967259&cx=c&gtm=4e64k0h2144.0 KiB56.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-MQMB4G9R&gtm=4e64k0h2142.2 KiB56.2 KiB
www.googletagmanager.com/gtag/js?id=AW-618990810&cx=c&gtm=4e64k0h2144.0 KiB55.7 KiB
www.googletagmanager.com/gtag/js?id=AW-867422543&cx=c&gtm=4e64k0h2137.7 KiB54.5 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js105.2 KiB54.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-TX2GVCC&l=dataLayer185.6 KiB52.7 KiB
/assets/ubik/web/@vp/react-bookends/10.46.7/lib/web/syste...102.0 KiB49.5 KiB
/assets/ubik/web/@vp/tracking/11.14.2173/systemjs/web/tra...100.5 KiB48.2 KiB
/assets/ubik/web/@vp/auth/7.0.16/lib/web/systemjs/auth-CB...53.9 KiB42.1 KiB
/assets/ubik/web/@vp/fragment-wix-websites-fragments/1.5....48.6 KiB35.7 KiB
/assets/ubik/web/@vp/fragment-wix-websites-fragments/1.5....50.1 KiB34.6 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB32.8 KiB
cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_01f9dc8d1048.8 KiB30.0 KiB
cdn.quantummetric.com/qscripts/quantum-vistaprint.js138.1 KiB29.1 KiB
/assets/ubik/web/@vp/ubik-react/19.2.3/dist/web/react-dom...54.2 KiB20.3 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.

URLTotal CPU TimeScript EvaluationScript Parse
/assets/ubik/web/@vp/ubik-react/19.2.3/dist/web/react-dom...1.6 s1.5 s1.0 ms
Unattributable1.3 s284 ms0.0 ms
www.vistaprint.com/digital-marketing/webs-shutdown1.3 s849 ms38 ms
cdn.quantummetric.com/qscripts/quantum-vistaprint.js591 ms509 ms50 ms
www.googletagmanager.com/gtm.js?id=GTM-PKH9B2B&gtm=4e64k0h2528 ms477 ms39 ms
www.googletagmanager.com/gtm.js?id=GTM-TX2GVCC&l=dataLayer446 ms347 ms56 ms
www.googletagmanager.com/gtm.js?id=GTM-MQMB4G9R&gtm=4e64k0h2401 ms327 ms41 ms
www.googletagmanager.com/gtag/js?id=G-3TW2S49QDP&cx=c&gtm=4e64k0h2370 ms326 ms40 ms
www.googletagmanager.com/gtag/js?id=AW-620967259&cx=c&gtm=4e64k0h2295 ms226 ms33 ms
www.googletagmanager.com/gtag/js?id=AW-618990810&cx=c&gtm=4e64k0h2281 ms240 ms38 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js257 ms216 ms40 ms
www.googletagmanager.com/gtag/js?id=AW-867422543&cx=c&gtm=4e64k0h2256 ms219 ms33 ms
cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_01f9dc8d10228 ms201 ms15 ms
www.googletagmanager.com/gtag/js?id=DC-14876881&cx=c&gtm=4e64k0h2195 ms158 ms36 ms
www.googletagmanager.com/gtag/js?id=DC-9815365&cx=c&gtm=4e64k0h2162 ms134 ms26 ms
js-agent.newrelic.com/nr-spa-1.277.0.min.js138 ms119 ms8.7 ms
/signals/config/1050145865347054?v=2.9.303&r=stable&domai...131 ms114 ms17 ms
/assets/ubik/web/@vp/ubik-react/19.2.3/dist/web/react-dom...126 ms105 ms18 ms
connect.facebook.net/en_US/fbevents.js125 ms95 ms29 ms
b-code.liadm.com/a-051j.min.js124 ms107 ms13 ms
fe-assets.workmagic.io/pixel/latest/wm.min.js108 ms85 ms22 ms
/assets/ubik/web/@vp/auth-react/7.0.16/lib/web/systemjs/a...108 ms107 ms0.3 ms
/assets/ubik/web/@vp/fragment-wix-websites-fragments/1.5....103 ms102 ms0.2 ms
/assets/ubik/web/@vp/newrelic-browser-micro-agent/1.0.5/d...102 ms86 ms2.2 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js93 ms53 ms40 ms
/assets/ubik/web/@vp/auth/7.0.16/lib/web/systemjs/auth-CB...88 ms67 ms13 ms
s.pinimg.com/ct/lib/main.10d2511a.js83 ms56 ms8.9 ms
/assets/ubik/web/@vp/swan/3.34.0/systemjs/web/systemjs/sw...80 ms14 ms46 ms
/assets/ubik/web/@vp/ubik-logging/2.2.13/lib/web/systemjs...72 ms71 ms0.9 ms
snap.licdn.com/li.lms-analytics/insight.min.js65 ms54 ms5.0 ms
/assets/ubik/web/@vp/chatbot-ui/1.0.66/lib/web/systemjs/c...60 ms9.3 ms50 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js56 ms43 ms13 ms
evs.dcp.vpdcp.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js54 ms48 ms3.9 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.

CategoryTime Spent
Script Evaluation8.0 s
Other1.2 s
Script Parsing & Compilation949 ms
Parse HTML & CSS219 ms
Garbage Collection189 ms
Style & Layout188 ms
Rendering20 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 13.5 KiB

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
Wix Vista Wix Black Logo div.swan-banner-text-container > div.swan-banner-text > div.swan-banner-eyebrow > img.swan-fluid-image
/image/upload/w_320/f_avif/q_auto/v1732610556/digital/par...

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
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 48 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 320 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 240 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
97

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.

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.swan-bounded-content > div.site-header-main > nav.site-header-links > a.site-header-link div.swan-bounded-content > div.site-header-main > nav.site-header-links > a.site-header-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]` 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
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
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
`[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
`[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
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.
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.
58

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
node:diagnostics_channelAllowed

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
AttributionReporting

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
Access to script at 'node:diagnostics_channel' from origin 'https://www.vistaprint.com' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: chrome, chrome-extension, chrome-untrusted, data, http, https, isolated-app.
Failed to load resource: net::ERR_FAILED
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 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
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.

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
connect a domain you already own. div.swan-banner-text-container > div.swan-banner-text > p.swan-banner-footnote > a.swan-link
Claim your free Yelp page div.swan-banner-text-container > div.swan-banner-text > div.swan-banner-links > a.swan-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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

57
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
58
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.11 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.87 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

351 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.11 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

8.38 s

Detailed Report

Audit breakdown by category with detailed findings.

57

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

RequestCache TTLTransfer Size
cdn.quantummetric.com/qscripts/quantum-vistaprint.js300.0 s138.7 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
fe-assets.workmagic.io/pixel/latest/wm.min.js1800.0 s83.9 KiB
cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_01f9dc8d10300.0 s49.3 KiB
/signals/config/1050145865347054?v=2.9.303&r=stable&domai...1200.0 s46.3 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
b-code.liadm.com/a-051j.min.js86400.0 s45.9 KiB
/swan/v3/fonts/tiempos-regular2.e4e5aee576677174d2fbcddb1...86400.0 s39.2 KiB
/swan/v3/fonts/graphic_regular2.7c96db81b23a97fd67cbeb7e7...86400.0 s36.3 KiB
/swan/v3/fonts/graphic_medium2.3829398551b96ac319a4812246...86400.0 s35.2 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms12.3 KiB
evs.dcp.vpdcp.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js0.0 ms9.5 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...86400.0 s10.7 KiB
cdn.veritonic.com/static/vpr.min.js0.0 ms2.7 KiB
s.pinimg.com/ct/lib/main.10d2511a.js1209600.0 s27.3 KiB
/next-integrations/actions/algolia-plugins/cb031e19c7ec5e...0.0 ms2.5 KiB
tags.creativecdn.com/Sou99GdoKN3iP18UHlb8.js3600.0 s2.7 KiB
cdn.attn.tv/vp/dtag.js120.0 s2.1 KiB
cdn.attn.tv/growth-tag-assets/client-configs/Vkc.js120.0 s2.0 KiB
ct.pinterest.com/static/ct/token_create.js7200.0 s2.2 KiB
s.pinimg.com/ct/core.js7200.0 s2.1 KiB
js.adsrvr.org/universal_pixel.js0.0 ms935 B
/collect?v=2&fmt=js&pid=1245164&time=1776799200046&url=ht...0.0 ms690 B
/rp.gif?ts=1776799199815&id=t2_he8iaecu&event=PageVisit&m...0.0 ms666 B
/swan/v3/icons/guaranteed_satisfaction.f5e5ab2db7017b2604...86400.0 s1.5 KiB
www.vistaprint.com/swan/v3/icons/phone.e2d8fff5c99f40dc6096bc97d3c2e04b.svg86400.0 s1.5 KiB
/swan/v3/icons/browse_designs.b4620fac13a93ee4c9d6e812951...86400.0 s1.1 KiB
www.vistaprint.com/swan/v3/icons/polish.f96d8f23d25c94848faad3002d02b45e.svg86400.0 s1.1 KiB
js.adsrvr.org/universal_pixel.js0.0 ms442 B
/swan/v3/icons/work_with_a_pro.54f00512b71a6a5080a43705e0...86400.0 s1.1 KiB
www.vistaprint.com/swan/v3/icons/search.0ed88af2d9772071041f88a0eb491cc0.svg86400.0 s1011 B
/swan/v3/icons/arrow_right.7e7f4793540a01cdedae0eb039b23b...86400.0 s998 B
www.vistaprint.com/swan/v3/icons/live_chat.0c91b22f94451864870cbcfb132e04d6.svg86400.0 s976 B
www.vistaprint.com/swan/v3/icons/check.f40333dc3e38ee20800b3d79994563c7.svg86400.0 s950 B
d7pet6vgg99z9.cloudfront.net/JS-build/en-us/ca-controller-production-en-us.js0.0 ms354 B
www.vistaprint.com/swan/v3/styles/icon.d41d8cd98f00b204e9800998ecf8427e.min.css86400.0 s560 B
/swan/v3/styles/button.d41d8cd98f00b204e9800998ecf8427e.m...86400.0 s548 B
/swan/v3/styles/pricing.d41d8cd98f00b204e9800998ecf8427e....86400.0 s546 B
/swan/v3/styles/field-set.d41d8cd98f00b204e9800998ecf8427...86400.0 s545 B
/tr/?id=1050145865347054&ev=PageView&dl=https%3A%2F%2Fwww...0.0 ms19 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.

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

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.

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
Get found on Yelp promo background image div.swan-banner > div.swan-banner-image-container > div.swan-banner-image > img.swan-fluid-image
/image/upload/f_auto/q_auto/v1756719037/digital/partners/...242.1 KiB210.8 KiB
Woman in branded Pom Pom t-shirt, with pink and yellow website, mobile, and soc… div.swan-grid-container > div.swan-row > div.swan-col-12 > img.swan-fluid-image
/image/upload/w_1440/f_avif/q_auto/v1739267791/digital/pa...67.1 KiB57.4 KiB
Vista x Wix Domains div.swan-hidden-xs > div.swan-banner-image-container > div.swan-banner-image > img.swan-fluid-image
/image/upload/w_1440/f_avif/q_auto/v1744352497/digital/pa...37.0 KiB25.7 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: 260 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 410 ms 1.2 MiB
URLTransfer SizeEst Savings
/assets/ubik/web/@vp/chatbot-ui/1.0.66/lib/web/systemjs/c...182.8 KiB119.8 KiB
/assets/ubik/web/@vp/swan/3.34.0/systemjs/web/systemjs/sw...166.3 KiB101.6 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js109.2 KiB84.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-PKH9B2B&gtm=4e64h1149.8 KiB79.3 KiB
www.googletagmanager.com/gtag/js?id=G-3TW2S49QDP&cx=c&gtm=4e64h1169.4 KiB64.1 KiB
www.googletagmanager.com/gtag/js?id=DC-9815365&cx=c&gtm=4e64h1130.1 KiB60.4 KiB
www.googletagmanager.com/gtag/js?id=DC-14876881&cx=c&gtm=4e64h1129.9 KiB60.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-MQMB4G9R&gtm=4e64h1142.5 KiB56.1 KiB
www.googletagmanager.com/gtag/js?id=AW-620967259&cx=c&gtm=4e64h1144.2 KiB55.9 KiB
www.googletagmanager.com/gtag/js?id=AW-618990810&cx=c&gtm=4e64h1144.2 KiB55.6 KiB
www.googletagmanager.com/gtag/js?id=AW-867422543&cx=c&gtm=4e64h1137.9 KiB55.3 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js105.2 KiB54.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-TX2GVCC&l=dataLayer185.9 KiB52.8 KiB
/assets/ubik/web/@vp/react-bookends/10.46.7/lib/web/syste...102.1 KiB49.5 KiB
/assets/ubik/web/@vp/tracking/11.14.2173/systemjs/web/tra...100.6 KiB48.2 KiB
/assets/ubik/web/@vp/auth/7.0.16/lib/web/systemjs/auth-CB...53.9 KiB42.1 KiB
/assets/ubik/web/@vp/fragment-wix-websites-fragments/1.5....48.6 KiB35.7 KiB
/assets/ubik/web/@vp/fragment-wix-websites-fragments/1.5....50.1 KiB34.6 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB33.0 KiB
cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_01f9dc8d1048.8 KiB30.0 KiB
cdn.quantummetric.com/qscripts/quantum-vistaprint.js138.1 KiB29.0 KiB
/assets/ubik/web/@vp/ubik-react/19.2.3/dist/web/react-dom...54.2 KiB20.3 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.

CategoryTime Spent
Script Evaluation2.3 s
Other356 ms
Script Parsing & Compilation297 ms
Parse HTML & CSS67 ms
Style & Layout55 ms
Garbage Collection54 ms
Rendering7.5 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 13.4 KiB

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
Wix Vista Wix Black Logo div.swan-banner-text-container > div.swan-banner-text > div.swan-banner-eyebrow > img.swan-fluid-image
/image/upload/w_320/f_avif/q_auto/v1732610556/digital/par...

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
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 51 user timings
Avoid long main-thread tasks 12 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 180 ms
Server Backend Latencies 250 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 180 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
100

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.

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]` 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
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
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
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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
`[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
`[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
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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.
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.
58

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
node:diagnostics_channelAllowed

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
AttributionReporting

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
Access to script at 'node:diagnostics_channel' from origin 'https://www.vistaprint.com' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: chrome, chrome-extension, chrome-untrusted, data, http, https, isolated-app.
Failed to load resource: net::ERR_FAILED
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 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
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.

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
connect a domain you already own. div.swan-banner-text-container > div.swan-banner-text > p.swan-banner-footnote > a.swan-link
Claim your free Yelp page div.swan-banner-text-container > div.swan-banner-text > div.swan-banner-links > a.swan-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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback