Website review, no card needed

united-vintage.com logo

united-vintage.com website review

Visit site (opens in a new tab)Reviewed 19 November 202643 issues · 90 checks

This review found 43 issues worth fixing on united-vintage.com, 16 of them high impact, across 90 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.4 s2.1 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.8 s
Jun 6, 20263.0 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.0 s
Aug 8, 20262.9 s
Aug 15, 20262.6 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Oct 31, 20262.5 s
Nov 7, 20262.4 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
288 ms192 msMay 30Nov 14227 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026220 ms
Jun 6, 2026233 ms
Jun 13, 2026253 ms
Jun 20, 2026269 ms
Jun 27, 2026274 ms
Jul 4, 2026275 ms
Jul 11, 2026277 ms
Jul 18, 2026269 ms
Jul 25, 2026256 ms
Aug 1, 2026256 ms
Aug 8, 2026246 ms
Aug 15, 2026239 ms
Aug 22, 2026239 ms
Aug 29, 2026237 ms
Sep 5, 2026246 ms
Sep 12, 2026248 ms
Sep 19, 2026248 ms
Sep 26, 2026242 ms
Oct 3, 2026229 ms
Oct 10, 2026218 ms
Oct 17, 2026211 ms
Oct 24, 2026206 ms
Oct 31, 2026203 ms
Nov 7, 2026216 ms
Nov 14, 2026227 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of united-vintage.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. united-vintage.com at 1.1 s1.1 s
  2. united-vintage.com at 2.3 s2.3 s
  3. united-vintage.com at 3.4 s3.4 s
  4. united-vintage.com at 4.5 s4.5 s
  5. united-vintage.com at 5.7 s5.7 s
  6. united-vintage.com at 6.8 s6.8 s
  7. united-vintage.com at 7.9 s7.9 s
  8. united-vintage.com at 9.1 s9.1 s

Speed

11 to fix57
  • Improve image delivery

    6.1 s · 1.5 MB

    13 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.1 s faster on a phone.

  • Reduce unused JavaScript

    2.1 s · 889 KiB

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

  • Main-thread work: 7.4 s

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

  • 4,159 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, weglot.com and rebuyengine.com and others), adding 2.9 MB and 1.1 s of main-thread time.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    950 ms

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

  • Shopify adds 434 ms

    434 ms

    Shopify costs a phone 434 ms of main-thread work and 2.1 MB 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.

  • Reduce unused CSS

    450 ms · 111 KiB

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

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 322 ms. During a long task the page ignores taps.

  • rebuyengine.com adds 116 ms

    116 ms

    rebuyengine.com costs a phone 116 ms of main-thread work and 332 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.

  • Use efficient cache lifetimes

    50 ms · 194 KiB

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

  • Legacy JavaScript

    51 KiB

    Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 116 ms

    116 ms

    Your server sent the HTML in 116 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 18.3 s

    18.3 s

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

  • Time to Interactive: 30.1 s

    30.1 s

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

  • Speed Index: 7.4 s

    7.4 s

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

  • Real-user LCP: 2.7 s

    2.7 s

    Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 243 ms

    243 ms

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Total Blocking Time: 250 ms

    250 ms

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

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -2%

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

5 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 499 ms

    499 ms

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

  • Largest content (LCP) got 19% faster for real visitors

    -19%

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

  • Cumulative Layout Shift: 0.076

    0.076

    The layout barely moves while loading (CLS 0.076, good is under 0.1).

Images and page weight

4 to fix25
  • Page weight: 6.2 MB in 607 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 607 requests on a phone: images 2.5 MB (289), scripts 2.0 MB (117) and other files 1,017 KiB (162). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    IMG_6406.jpg weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    1.1 MB

    4 images are downloaded at several times the size a phone draws them, for example IMG_6406.jpg at 4,208 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

  • An image on the first screen is lazy-loaded

    bf_12.png 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).

  • About 1.8 g of CO₂ per visit

    1.77 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

11 to fixGoogle 8689
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Form elements should have a visible label (3 elements)

    Form elements should have a visible label: 3 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 38 images without alt text

    38 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (22 elements)

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

  • Heading levels should only increase by one (2 elements)

    Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • ARIA role should be appropriate for the element (8 elements)

    ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 55 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • 2 H1 headlines

    There are 2 <h1> headlines (“@media screen and (max-width: 749px) { .header__h…” and “DÉJÀ MENTIONNÉ DANS...”). One clear main headline is easier for people and search engines.

  • 81 internal links, 7 external

    The homepage links to 81 pages on united-vintage.com and 7 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Leading Vintage Wholesale in Europe. Spécialisée dans la vente de vêtements de marque streetwear et vintage de seconde …”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Vente en gros Vêtements De Marque Vintage | United Vintage”.

  • Canonical URL set

    The canonical URL is https://www.united-vintage.com/.

  • Structured data in place

    Structured data found: FAQPage, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.united-vintage.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,105 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.united-vintage.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 2 linked pages are broken

    Your homepage links to https://www.united-vintage.com/collections/le-plus-populaire and https://www.united-vintage.com/collections/polaires-pulls, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 4 pages without a meta description

    https://www.united-vintage.com/collections/summer-drop-express-delivery, https://www.united-vintage.com/pages/loyalty-program, https://www.united-vintage.com/pages/refer-a-friend and https://www.united-vintage.com/pages/consulting have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://www.united-vintage.com/collections/summer-drop-express-delivery, https://www.united-vintage.com/collections/spring-best-seller-2025, https://www.united-vintage.com/collections/wholesale, https://www.united-vintage.com/collections/hoodie-sweat-shirts, https://www.united-vintage.com/collections/vestes-manteaux and https://www.united-vintage.com/collections/spring-summer and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    31 of 35 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No risk reducer

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

  • About 578 words of copy

    The homepage carries about 578 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP BLACK FRIDAY NOW”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “SHOP BLACK FRIDAY NOW”, “Mix Sweat/Hoodie Zippé €190,00 SHOP NOW” and “Mix Hoodie €190,00 SHOP NOW”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 35 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 53 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at united-vintage.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 19 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Provesource · Bucks · Microsoft Clarity · Infinite Scroll · Klaviyo Email Marketing Sms · Weglot Translate Your Store · Kaching Bundles · Countdown Timer · Rivo Loyalty Rewards Referrals · Air Reviews · Section Factory · Upcart · Cowlendar · Bestpush · avada.io · snapchat.com · rebuyengine.com · cloudfront.net · provesrc.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on united-vintage.com, including 20 speed issues and 1 SEO issue. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25