veve.me website review

About 723 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

A phone's processor spends 18.1 s on main-thread work while loading, 7.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

The page has 4,432 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1.1 MB and 1.8 s of main-thread time.

20 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

Google Tag Manager costs a phone 997 ms of main-thread work and 507 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

30 files are served with short cache lifetimes, so returning visitors download them again (807 KiB).

Facebook costs a phone 513 ms of main-thread work and 283 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 199 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

18 images could be 497 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Optanon costs a phone 255 ms of main-thread work and 213 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Polyfills for old browsers add 77 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “VeVe promotional banner”.

Visually, the page fills in at 18.8 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 24.3 s. Good is under 3.8 s.

Scripts block taps and scrolling for 4.3 s in total while the page loads. Good is under 200 ms.

Real visitors wait 306 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 1.8 s on a phone. Good is under 1.8 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 168 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.9 MB in 239 requests on a phone: scripts 3.0 MB (122), images 1.4 MB (36) and stylesheets 221 KiB (11). Under 2 MB keeps phones on slow connections fast.

image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 166.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

[role="img"] and [role="image"] elements must have alternative text: 62 elements on the page fail this check, rated serious by axe-core.

7 tap targets are too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements with visible text labels do not have matching accessible names. (8 elements).

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to 67 pages on veve.me and 4 external pages.

The HTML your server sends has 305 of the 697 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.veve.me/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.veve.me/en and / all use the title “VeVe | Buy & Sell Digital Collectibles and Comics”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.veve.me/blog has no meta description, so Google writes the search snippet from whatever text it finds.

/, https://www.veve.me/collectibles/en, https://www.veve.me/comics/en, https://www.veve.me/collectibles/en/market, https://www.veve.me/collectibles/en/drops and https://www.veve.me/collectibles/en/artworks and 5 others use the same meta description. A description written for each page earns more clicks.

https://www.veve.me/collectibles/en, https://www.veve.me/comics/en, https://www.veve.me/veveverse, https://www.veve.me/blog, https://www.veve.me/blog/category/veve/101 and https://www.veve.me/brands have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.veve.me/collectibles/en/market, https://www.veve.me/collectibles/en/drops, https://www.veve.me/collectibles/en//drops and https://www.veve.me/collectibles/en//brands have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.

9 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418 for the full message or use the non-minified dev environm…”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 697 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 5 cookies (measured from a US location before any click).

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.