inglasco.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, rebuyengine.com and ContentSquare and others), adding 1.7 MB and 825 ms of main-thread time.

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

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

About 95 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

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

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 10.0 MB in 463 requests on a phone: images 6.9 MB (199), scripts 1.7 MB (98) and other files 845 KiB (128). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example NBA---BOSTON-CELTICS_1000x1000_f201baf8-ff85-40cc-b5ed-2ab9d at 1,000 px wide, shown at 22 px. Resized copies would save about 120 KiB.

2 images further down the page (120 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 2.83 g of CO₂e: 339.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

4 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 469 pages on inglasco.com and 43 external pages.

There is no https://us.inglasco.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://us.inglasco.com/collections/nhl, https://us.inglasco.com/collections/anaheim-ducks, https://us.inglasco.com/collections/boston-bruins, https://us.inglasco.com/collections/buffalo-sabres, https://us.inglasco.com/collections/calgary-flames and https://us.inglasco.com/collections/colorado-avalanche and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://us.inglasco.com/collections/nhl, https://us.inglasco.com/collections/anaheim-ducks, https://us.inglasco.com/collections/boston-bruins, https://us.inglasco.com/collections/buffalo-sabres, https://us.inglasco.com/collections/calgary-flames and https://us.inglasco.com/collections/colorado-avalanche and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://us.inglasco.com/collections/colorado-avalanche, https://us.inglasco.com/collections/columbus-blue-jackets, https://us.inglasco.com/collections/detroit-red-wings, https://us.inglasco.com/collections/florida-panthers and https://us.inglasco.com/collections/los-angeles-kings took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Context: Failed to fetch a matching recipe AbortError: signal is aborted without reason”.

Large scripts ship without source maps.

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Hotjar and Klaviyo (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 12 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.