vb-distro.com website review

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.7 s).

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

About 193 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

About 651 KiB of JavaScript is downloaded but never used on this page.

1 long task block the main thread while loading, the longest for 361 ms. During a long task the page ignores taps.

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

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

15 KiB could be saved by minifying CSS.

1 third-party service load with your homepage (Google Fonts), adding 78 KiB and 1 ms of main-thread time.

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

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

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

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “UK duty-stamped vaping products, now available to trade. Or…”. Most of its time is resource load delay (12.7 s).

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.6 MB in 40 requests on a phone: images 4.2 MB (26), scripts 1,009 KiB (2) and stylesheets 214 KiB (4). Under 2 MB keeps phones on slow connections fast.

uk-duty-stamped-banner-1000.jpg 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).

5 images (661 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

4 images are downloaded at several times the size a phone draws them, for example nagham-hayati-pro-ultra-25k.jpg at 720 px wide, shown at 172 px. Resized copies would save about 267 KiB.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 25 characters: “VB Home | VB Distribution”. Between 30 and 65 characters leaves room to say what you do and for whom.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 127 pages on vb-distro.com and 7 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://vb-distro.com/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://vb-distro.com/shop/category/vpd-vapes-29, https://vb-distro.com/shop/hayati-pro-max-4k-prefilled-pod-kit-20mg-5996, https://vb-distro.com/shop/hayati-pro-max-4k-prefilled-pods-20mg-5997, https://vb-distro.com/shop/hayati-pro-max-6k-prefilled-pod-kit-20mg-5998, https://vb-distro.com/shop/hayati-pro-max-6k-prefilled-pods-20mg-5999 and https://vb-distro.com/shop/hayati-pro-ultra-25k-prefilled-pod-kit-20mg-6000 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://vb-distro.com/shop/hayati-pro-max-6k-prefilled-pod-kit-20mg-5998, https://vb-distro.com/shop/hayati-pro-max-6k-prefilled-pods-20mg-5999, https://vb-distro.com/shop/hayati-pro-ultra-25k-prefilled-pod-kit-20mg-6000, https://vb-distro.com/shop/hayati-pro-ultra-25k-prefilled-pods-20mg-6001, https://vb-distro.com/shop/category/pre-vpd-vapes-30 and https://vb-distro.com/shop/hayati-pro-max-6k-vape-kit-452 and 5 others took over 3 s to send their HTML from our server.

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

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 334 words of visible text.

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

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.

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