mogo.ca website review

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

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

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

Your mobile performance score is 59 (desktop: 84). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, website-files.com and cloudfront.net and others), adding 1.7 MB and 654 ms of main-thread time.

Google Tag Manager costs a phone 484 ms of main-thread work and 529 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 images could be 421 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

website-files.com costs a phone 73 ms of main-thread work and 978 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.

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

31 KiB could be saved by minifying JavaScript.

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

Desktop scores 84 but mobile only 59. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying CSS.

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 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ONLINE PERSONAL LOANS FOR CANADIANS”.

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

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

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

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

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

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

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

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

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.mogo.ca/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at mogo.ca/robots.txt, the first file search crawlers ask for.

The homepage links to 13 pages on mogo.ca and 18 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.

There is no https://www.mogo.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.

https://www.mogo.ca/careers has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mogo.ca/terms-and-conditions and https://www.mogo.ca/contact-mogo use the same meta description. A description written for each page earns more clicks.

https://www.mogo.ca/contact-mogo has 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.

We fetched 4 pages linked from your homepage and read each the way a search engine does.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 20 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

The homepage carries about 892 words of visible text.

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