kvsupply.com website review

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

6 third-party services load with your homepage (Signyfyd, Shopify and ThreatMetrix and others), adding 417 KiB and 967 ms of main-thread time.

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

Signyfyd costs a phone 863 ms of main-thread work and 264 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.

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

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

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

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

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

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

5 KiB JavaScript is shipped twice across bundles.

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

5 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Rider and Horse enjoying the sunset”.

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

The layout shifts by 0.106 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Topleft-800_e2128ab9-b278-4fb2-8eb0-50a69cf08acd.webp 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 0.26 g of CO₂e: 31.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 941 pages on kvsupply.com and 1 external page.

There is no https://www.kvsupply.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.

Your homepage links to https://www.kvsupply.com/pages/accessibility-statement, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.kvsupply.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) SecurityError: Failed to read a named property 'document' from 'Window': Sandbox access violation…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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.

The homepage carries about 309 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Ads (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 17 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.