agilityauto.ca website review

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

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

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

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

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

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

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

8 third-party services load with your homepage (Key CDN, Shopify and popt.in and others), adding 648 KiB and 235 ms of main-thread time.

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

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

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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.

2 KiB could be saved by minifying CSS.

Your largest element takes 8.3 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 7.3 s (Speed Index). Good is under 3.4 s.

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

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

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.5 MB in 173 requests on a phone: images 865 KiB (9), scripts 785 KiB (49) and other files 736 KiB (88). Under 2 MB keeps phones on slow connections fast.

agility-155_c8f326ae-fa1b-4a5f-ac02-c1e07516a648.jpg 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 0.72 g of CO₂e: 86.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

The homepage links to 129 pages on agilityauto.ca and 11 external pages.

https://agilityauto.ca/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://agilityauto.ca/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, https://agilityauto.ca/blogs/news, https://agilityauto.ca/collections, https://agilityauto.ca/collections/fuel-system-products, https://agilityauto.ca/collections/fuel-pump-hanger-assembly and https://agilityauto.ca/collections/fuel-pump-and-sender-assembly and 9 others all use the title “American Express”. Search engines can't tell which page to show for a search, so each competes with the others.

https://agilityauto.ca/blogs/news, https://agilityauto.ca/customer_authentication/redirect, https://agilityauto.ca/collections, https://agilityauto.ca/collections/fuel-system-products, https://agilityauto.ca/collections/fuel-pump-hanger-assembly and https://agilityauto.ca/collections/fuel-pump-and-sender-assembly and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://agilityauto.ca/blogs/news, https://agilityauto.ca/customer_authentication/redirect and https://agilityauto.ca/collections have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 652 words of visible text.

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