teamford.ca website review

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

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

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

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

8 third-party services load with your homepage (Facebook, Google Tag Manager and TikTok and others), adding 1.2 MB and 998 ms of main-thread time.

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

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

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

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

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

17 KiB could be saved by minifying JavaScript.

3 KiB JavaScript is shipped twice across bundles.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “0% financing available on three trucks displayed in mountai…”.

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

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

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

Real visitors wait 253 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.7 MB in 137 requests on a phone: scripts 3.1 MB (51), images 1.1 MB (29) and other files 321 KiB (50). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 1280x740 at 1,280 px wide, shown at 390 px. Resized copies would save about 55 KiB.

1 image (337 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.

2 images further down the page (59 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

3 dropdowns have no label.

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

All page content should be contained by landmarks: 7 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: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Structured data found (AutoDealer, BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

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

The homepage links to 56 pages on teamford.ca and 16 external pages.

https://www.teamford.ca/vehicles and https://www.teamford.ca/city-employee-deals have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.teamford.ca/sell-trade took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187188838&Ver=2&mid=a6e034cf-f9ab-4248-b4ae-133a6cff4034&bo=1&sid=8e9013c0d7c211f18243fdb202bedaa0&vid=8e903e40d7c211f1aed40b6abc104552&vids=1&msclkid=N&pi=918639831&l.

3 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: jQuery is not defined”.

Large scripts ship without source maps.

Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 251 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 5 mores (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 27 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.