verbero.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, tidio.co and Shopify and others), adding 1.3 MB and 479 ms of main-thread time.

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

Google Tag Manager costs a phone 219 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.

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

tidio.co costs a phone 81 ms of main-thread work and 515 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 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

7 images could be 61 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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 JavaScript is shipped twice across bundles.

3 KiB could be saved by minifying JavaScript.

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

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

Visually, the page fills in at 8.1 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 79 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 17.5 MB in 300 requests on a phone: media 14.0 MB (3), scripts 1.3 MB (68) and images 990 KiB (74). Under 2 MB keeps phones on slow connections fast.

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

3 images further down the page (80 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

17 images have 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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Your title is 69 characters, so Google will cut it off around 60: “Shop Verbero Hockey - Your Premier Online Ice Hockey Store – Verbero™”.

There are 3 <h1> headlines (“”, “Personalized Team Gear,” and “Uniforms & Team Stores”). One clear main headline is easier for people and search engines.

The homepage links to 138 pages on verbero.com and 10 external pages.

https://www.verbero.com/pages/customizer, https://www.verbero.com/collections/all, https://www.verbero.com/pages/leadership, https://www.verbero.com/pages/careers, https://www.verbero.com/pages/why-verbero and https://www.verbero.com/pages/video-gallery and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.verbero.com/american-airlines-demo, whose canonical is https://www.verbero.com/pages/team-store-v2/american-airlines-demo-team-store. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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 1,038 words of visible text.

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