abilityatwork.com website review

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

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

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

8 third-party services load with your homepage (zotabox.com, Cloudflare CDN and Google Tag Manager and others), adding 1.3 MB and 1.0 s of main-thread time.

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

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

zotabox.com costs a phone 401 ms of main-thread work and 654 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.

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

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

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

About 98 KiB of CSS is downloaded but never applied on this page.

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

10 KiB could be saved by minifying JavaScript.

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 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ErgoCentric tCentric Multi-Tilt Series Hybrid Mesh Back, Fo…”.

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

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

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

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

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

1 image 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 2.6 MB in 177 requests on a phone: scripts 1.4 MB (66), other files 722 KiB (84) and images 263 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

10 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.

Your title is 69 characters, so Google will cut it off around 60: “Ergonomic Office Chairs, Electric Height Adjustable Desks | ErgoEquip”.

There are 5 <h1> headlines (“ErgoEquip”, “Reviews” and “Newsletter”). One clear main headline is easier for people and search engines.

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

Structured data found (untyped) but with 4 problems, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.

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

The homepage links to 78 pages on abilityatwork.com and 6 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.

/collections/ergocentric, /collections/medical-seating and /collections/ergonomic-mice have no meta description, so Google writes the search snippet from whatever text it finds.

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

5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://ergoequip.ca/cdn/shop/t/16/assets/fonts.scss.css?v=3535' because its MIME type ('t…”.

1 link to other sites is dead, for example http://empy.re/r/shopify (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://ergoequip.ca/checkout.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ergoequip.ca is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

ergoequip.ca has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

ergoequip.ca's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

abilityatwork.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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