vanlandstore.com website review

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

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

8 third-party services load with your homepage (Shopify, Facebook and Klaviyo and others), adding 2.0 MB and 1.2 s of main-thread time.

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

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

Shopify costs a phone 565 ms of main-thread work and 956 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.

7 images could be 262 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Klaviyo costs a phone 161 ms of main-thread work and 309 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 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

11 KiB JavaScript is shipped twice across bundles.

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.

3 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

12 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.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.2 MB in 496 requests on a phone: scripts 1.6 MB (222), other files 996 KiB (186) and images 939 KiB (29). Under 2 MB keeps phones on slow connections fast.

zamp.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).

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is only 8 characters: “Van Land”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 269 characters; Google truncates after about 160, so the end of your pitch is cut.

Your <h1> is empty.

The homepage links to 387 pages on vanlandstore.com and 18 external pages.

https://vanlandstore.com/collections/awnings, https://vanlandstore.com/collections/bumpers-winches, https://vanlandstore.com/collections/cargo-carriers, https://vanlandstore.com/collections/flares, https://vanlandstore.com/collections/fuel-tanks and https://vanlandstore.com/collections/inflatable-couches and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://vanlandstore.com/collections/awnings, https://vanlandstore.com/collections/bumpers-winches, https://vanlandstore.com/collections/cargo-carriers, https://vanlandstore.com/collections/flares, https://vanlandstore.com/collections/fuel-tanks and https://vanlandstore.com/collections/inflatable-couches and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://sellup.herokuapp.com/kartifyjs/launchtipcartdrawer.css' from origin 'https://vanla…”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 2,007 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.

Opening the homepage sets 14 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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.