sterlinghardware.ca website review

23 images could be 9.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 27.9 s faster on a phone.

245 files are served with short cache lifetimes, so returning visitors download them again (8.0 MB).

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.

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

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

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

About 338 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Facebook and Cloudflare and others), adding 775 KiB and 480 ms of main-thread time.

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

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

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.

Your largest element takes 37.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FRAMELESS SHOWER<br> HARDWARE”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 12.2 MB in 275 requests on a phone: images 9.9 MB (34), scripts 1.2 MB (207) and fonts 920 KiB (7). Under 2 MB keeps phones on slow connections fast.

5 images weigh 8.2 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example Sterling_Glass_Hardware_-_Edmonton_Alberta.png at 1,600 px wide, shown at 360 px. Resized copies would save about 4.8 MB.

18 images (9.5 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

4 images further down the page (5.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

Sterling_Glass_Hardware_-_happy_Diwali_Slider.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).

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

Elements must only use permitted ARIA attributes: 8 elements on the page fail this check, rated serious by axe-core.

3 elements hidden from screen readers can still receive keyboard focus.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 2 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.

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

Your title is 101 characters, so Google will cut it off around 60: “Glass & Glazing Hardware - Frameless Shower Glass Railing Hardware Supplier – Sterling Gl…”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No Open Graph image (also missing: og:title, og:description), 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 323 pages on sterlinghardware.ca and 5 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

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

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

2 errors were logged to the browser console while the page loaded, for example “Sending form data to 'https://www.facebook.com/tr/' violates the following report-only Content Security Policy directiv…”.

5 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Content security policy”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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 723 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 16 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.