progressivedesk.ca website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.8 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and Shopify and others), adding 2.8 MB and 1.6 s of main-thread time.

Google Tag Manager costs a phone 900 ms of main-thread work and 1.3 MB 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 175 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.

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

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

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

Shopify costs a phone 135 ms of main-thread work and 360 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 43 KiB JavaScript that modern phones do not need.

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

9 KiB could be saved by minifying CSS.

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 could be saved by minifying JavaScript.

Your largest element takes 22.5 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 25.7 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 4.9 MB in 357 requests on a phone: scripts 3.0 MB (82), other files 1.0 MB (190) and images 597 KiB (43). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 167.7 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.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Your title is 76 characters, so Google will cut it off around 60: “Ergonomic Office Furniture & Workspace Solutions – Progressive Desk - Canada”.

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

The homepage links to 160 pages on progressivedesk.ca and 16 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://www.progressivedesk.ca/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.progressivedesk.ca/collections/all and https://www.progressivedesk.ca/policies/shipping-policy use the same meta description. A description written for each page earns more clicks.

https://www.progressivedesk.ca/collections/workspace-automation and https://www.progressivedesk.ca/collections/discounts have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://ipinfo.io/json' from origin 'https://www.progressivedesk.ca' has been blocked by CORS polic…”.

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: 3 testimonial or review blocks. 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 644 words of visible text.

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 3 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 33 cookies, 12 of them by other companies (measured from a US location before any click).

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