collins.co website review

FontAwesome CDN costs a phone 2.5 s of main-thread work and 192 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

35 images could be 1,018 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 22. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (FontAwesome CDN, hsappstatic.net and POWr and others), adding 2.3 MB and 4.2 s of main-thread time.

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

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

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

hsappstatic.net costs a phone 518 ms of main-thread work and 842 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.

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

POWr costs a phone 386 ms of main-thread work and 13 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.

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

Hubspot costs a phone 254 ms of main-thread work and 334 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.

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

11 KiB JavaScript is shipped twice across bundles.

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 20.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 38.2 s. Good is under 3.8 s.

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

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

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

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

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

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

Your homepage downloads 8.1 MB in 527 requests on a phone: images 3.9 MB (228), scripts 2.6 MB (145) and other files 883 KiB (118). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example essentialshero1_1920x993.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 297 KiB.

1 image (103 KiB) is 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.

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

1 dropdown has no label.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Headings skip levels (h3 → h5 and 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 meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 783 pages on collins.co and 12 external pages.

https://collins.co/collections/free-standing-stations and https://collins.co/collections/free-standing-stations/Double-Sided all use the title “Free-Standing Stations | Collins”. Search engines can't tell which page to show for a search, so each competes with the others.

https://collins.co/pages/chairs, https://collins.co/collections/styling-chairs, https://collins.co/collections/all-purpose-chairs, https://collins.co/collections/unisex-chairs, https://collins.co/collections/shampoo-chairs and https://collins.co/collections/dryer-chairs and 8 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://collins.co/collections/free-standing-stations/Double-Sided, whose canonical is https://collins.co/collections/free-standing-stations/double-sided. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://collins.co/pages/salon, https://collins.co/pages/chairs and https://collins.co/pages/salon-stations have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

Chrome logged issues while loading the page (“Cookie”).

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 5 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 27 cookies, 5 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.