canadacomputers.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1,006 KiB and 850 ms of main-thread time.

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

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

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

Google Tag Manager costs a phone 444 ms of main-thread work and 565 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.

Facebook costs a phone 232 ms of main-thread work and 317 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.

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

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

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

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.

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 30.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Seagate 20261030”.

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

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

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

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 8.9 MB in 99 requests on a phone: images 7.0 MB (40), scripts 1.3 MB (22) and fonts 490 KiB (3). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

18 images (6.6 MB) are 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.

1 image is downloaded at several times the size a phone draws it, for example ee3fb6bb14b47d03e9eee7f2ea5b71df.jpg at 1,110 px wide, shown at 360 px. Resized copies would save about 9 KiB.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

11 form fields have 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 (h2 → h5), which makes the page harder to scan with a screen reader.

Your title is 92 characters, so Google will cut it off around 60: “Canada Computers & Electronics: Your one-stop computer shop - Canada Computers & Electron…”.

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

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

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 565 pages on canadacomputers.com and 18 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/en/content/8/online-shopping-faq is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/en/ccflyer has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /en/openbox, whose canonical is /en/2/root. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en/ccflyer, /en/bundle, /en/openbox, /en/clearance, /en/pc-configurator and /en/services and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

/en/brands-list took over 3 s to send its HTML from our server.

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

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

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

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Opening https://canadacomputers.com goes through 2 redirects before the homepage loads.

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 “0; 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.

canadacomputers.com 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.

canadacomputers.com'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.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 209 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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, Meta Pixel and Microsoft Clarity (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 14 cookies, 1 of them by other companies (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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.