vigoindustries.com website review

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

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

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

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

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

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

Google Tag Manager costs a phone 297 ms of main-thread work and 676 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.

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

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

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

LiveChat costs a phone 95 ms of main-thread work and 367 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.

Klaviyo costs a phone 92 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.

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

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

About 37 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.

9 KiB could be saved by minifying JavaScript.

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

4 KiB JavaScript is shipped twice across bundles.

Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Modern luxury kitchen and bathroom fixtures by VIGO Industr…”.

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

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

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

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

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

Your homepage downloads 11.7 MB in 378 requests on a phone: media 7.4 MB (3), scripts 2.6 MB (140) and other files 1.1 MB (168). Under 2 MB keeps phones on slow connections fast.

VG6101MBCL6074-1-ENV-1-V1.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 3.32 g of CO₂e: 398.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn'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.

1 image has no alt text, which hurts accessibility and image search.

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

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

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

1 link inside paragraphs relies on colour alone to stand out.

Your title is 69 characters, so Google will cut it off around 60: “VIGO Industries | Showers, Faucets, Sinks for Your Bathroom & Kitchen”.

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

Structured data found (ItemList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//vigoindustries.com/cdn/shop/files/Logo_d812d4e1-0207-…”.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 477 pages on vigoindustries.com and 6 external pages.

https://vigoindustries.com/collections/shower-screen-sets has no meta description, so Google writes the search snippet from whatever text it finds.

https://vigoindustries.com/collections/all-products, https://vigoindustries.com/pages/track-order, https://vigoindustries.com/pages/register-warranty-form, https://vigoindustries.com/collections/shower-doors, https://vigoindustries.com/collections/sliding-shower-doors and https://vigoindustries.com/collections/shower-door-sets and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://vigoindustries.com/collections/fixed-shower-screens, https://vigoindustries.com/collections/hinged-shower-doors, https://vigoindustries.com/collections/shower-door-sets, https://vigoindustries.com/collections/shower-screen-sets, https://vigoindustries.com/collections/tub-doors and https://vigoindustries.com/collections/hinged-tub-doors took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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