Website review, no card needed
fido.ca website review
Visit site (opens in a new tab)Reviewed 1 November 202632 issues · 84 checks
This review found 32 issues worth fixing on fido.ca, 11 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.2 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 334 ms |
| May 16, 2026 | 332 ms |
| May 23, 2026 | 329 ms |
| May 30, 2026 | 323 ms |
| Jun 6, 2026 | 321 ms |
| Jun 13, 2026 | 322 ms |
| Jun 20, 2026 | 324 ms |
| Jun 27, 2026 | 327 ms |
| Jul 4, 2026 | 332 ms |
| Jul 11, 2026 | 341 ms |
| Jul 18, 2026 | 347 ms |
| Jul 25, 2026 | 356 ms |
| Aug 1, 2026 | 363 ms |
| Aug 8, 2026 | 371 ms |
| Aug 15, 2026 | 382 ms |
| Aug 22, 2026 | 388 ms |
| Aug 29, 2026 | 388 ms |
| Sep 5, 2026 | 386 ms |
| Sep 12, 2026 | 380 ms |
| Sep 19, 2026 | 380 ms |
| Sep 26, 2026 | 386 ms |
| Oct 3, 2026 | 388 ms |
| Oct 10, 2026 | 395 ms |
| Oct 17, 2026 | 396 ms |
| Oct 24, 2026 | 399 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
11.9 s · 4.5 MBAbout 4.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.9 s faster on a phone.
Use efficient cache lifetimes
4.3 s · 1.6 MB44 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Main-thread work: 17.0 s
A phone's processor spends 17.0 s on main-thread work while loading, 11.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (pure.cloud, Google CDN and Dynatrace and others), adding 3.7 MB and 2.6 s of main-thread time.
pure.cloud adds 851 ms
851 mspure.cloud costs a phone 851 ms of main-thread work and 1.1 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 846 ms. During a long task the page ignores taps.
Google CDN adds 694 ms
694 msGoogle CDN costs a phone 694 ms of main-thread work and 1.4 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.
Render-blocking requests
650 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 650 ms.
Reduce unused CSS
430 ms · 100 KiBAbout 100 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 430 ms faster on a phone.
Dynatrace adds 365 ms
365 msDynatrace costs a phone 365 ms of main-thread work and 347 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 adds 254 ms
254 msFacebook costs a phone 254 ms of main-thread work and 280 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.
Improve image delivery
200 ms · 163 KiB6 images could be 163 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
200 ms · 51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify JavaScript
76 KiB76 KiB could be saved by minifying JavaScript.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 37 ms
37 msYour server sent the HTML in 37 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 27.0 s
27.0 sYour largest element takes 27.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sign in for exclusive offers! Check out amazing plan and ph…”.
Total Blocking Time: 6.3 s
6.3 sScripts block taps and scrolling for 6.3 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 57.1 s
57.1 sThe page becomes fully interactive after 57.1 s. Good is under 3.8 s.
Speed Index: 11.9 s
11.9 sVisually, the page fills in at 11.9 s (Speed Index). Good is under 3.4 s.
Real-user INP: 225 ms
225 msReal visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 334 ms to 399 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 492 ms
492 msReal visitors wait 492 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 10.1 MB in 279 requests
10.1 MBYour homepage downloads 10.1 MB in 279 requests on a phone: scripts 8.1 MB (90), other files 894 KiB (121) and fonts 406 KiB (16). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (61 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.
About 2.9 g of CO₂ per visit
2.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.86 g of CO₂e: 343.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (166 characters)
Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
14 internal links, 5 external
The homepage links to 14 pages on fido.ca and 5 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Get a new phone. The case is on us.”.
Title: 50 characters
Your title is a healthy 50 characters: “Shop Mobile Phones, Cellular Plans and More - Fido”.
Canonical URL set
The canonical URL is https://www.fido.ca/.
Structured data in place
Structured data found: Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.fido.ca/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.fido.ca/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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (463 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.fido.ca/myoffers has no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.fido.ca/consumer/get-email-updates, whose canonical is https://www.fido.ca/sign-up. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages without an H1
https://www.fido.ca/myoffers, https://www.fido.ca/phones, https://www.fido.ca/phones/bring-your-own-device, https://www.fido.ca/phones/apple-iphone-duo, https://www.fido.ca/phones/samsung-galaxy-s26 and https://www.fido.ca/phones/iphone-15-pro-cpo have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://www.fido.ca/myoffers, https://www.fido.ca/phones, https://www.fido.ca/phones/bring-your-own-device, https://www.fido.ca/phones/apple-iphone-duo, https://www.fido.ca/phones/samsung-galaxy-s26 and https://www.fido.ca/phones/iphone-15-pro-cpo and 1 other have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
22 of 26 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 515 words of copy
The homepage carries about 515 words of visible text.
1 checks passed
14 calls to action
The homepage has 14 calls to action, for example “Shop plans”, “Conditions apply” and “Shop phones”.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Tag Manager, Meta Pixel, Pinterest Tag, Reddit Pixel and Snap 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.
26 cookies set on arrival
26Opening the homepage sets 26 cookies (measured from a US location before any click).
No consent tool detected
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.
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at fido.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
- Hosting
- Azure
Company
- Founded
- 1996
- Headquarters
- Toronto
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on fido.ca, including 18 speed issues, 1 SEO issue and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.