Website review, no card needed
hometrust.ca website review
Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 87 checks
This review found 42 issues worth fixing on hometrust.ca, 16 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 108 ms |
| May 16, 2026 | 105 ms |
| May 23, 2026 | 101 ms |
| May 30, 2026 | 100 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 100 ms |
| Jul 4, 2026 | 102 ms |
| Jul 11, 2026 | 98 ms |
| Jul 18, 2026 | 102 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 102 ms |
| Aug 8, 2026 | 102 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 97 ms |
| Aug 29, 2026 | 99 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 91 ms |
| Sep 19, 2026 | 93 ms |
| Sep 26, 2026 | 95 ms |
| Oct 3, 2026 | 95 ms |
| Oct 10, 2026 | 98 ms |
| Oct 17, 2026 | 100 ms |
| Oct 24, 2026 | 106 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
Use efficient cache lifetimes
13.1 s · 2.6 MB109 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Render-blocking requests
7.7 s54 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.7 s.
Reduce unused JavaScript
4.5 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Reduce unused CSS
1.4 s · 275 KiBAbout 275 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 40). 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 (Google CDN, Google Tag Manager and Hotjar and others), adding 1.5 MB and 1.0 s of main-thread time.
Minify JavaScript
450 ms · 87 KiB87 KiB could be saved by minifying JavaScript.
Google CDN adds 344 ms
344 msGoogle CDN costs a phone 344 ms of main-thread work and 734 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.
Minify CSS
300 ms · 30 KiB30 KiB could be saved by minifying CSS.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 252 ms
252 msGoogle Tag Manager costs a phone 252 ms of main-thread work and 352 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.
Legacy JavaScript
200 ms · 55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 222 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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.
First Contentful Paint: 7.7 s
7.7 sThe first text or image appears after 7.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 17.5 s
17.5 sYour largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By clicking “Accept All”, you agree to the storing of cooki…”.
Time to Interactive: 25.5 s
25.5 sThe page becomes fully interactive after 25.5 s. Good is under 3.8 s.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 410 ms
410 msScripts block taps and scrolling for 410 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 108 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 107 ms
107 msReal visitors wait 107 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.066
0.066The layout barely moves while loading (CLS 0.066, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 152 requests
4.5 MBYour homepage downloads 4.5 MB in 152 requests on a phone: scripts 2.8 MB (66), images 710 KiB (20) and other files 398 KiB (19). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
home-image.png weighs 594 KiB. On a phone connection a single image that size takes seconds.
2 images in older formats
2 images (635 KiB) 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.
About 1.3 g of CO₂ per visit
1.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 151.6 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
Unlabelled dropdowns
1 dropdown has no label.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (17 characters)
Your title is only 17 characters: “Home - Home Trust”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 2 problems
Structured data found (BreadcrumbList, ImageObject, WebPage and WebSite) but with 2 problems, for example “ImageObject: url is not an absolute URL ("https://hometrust.ca/wp-content/uploads/2018/06/slider-1-update.jpg")”.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
63 internal links, 11 external
The homepage links to 63 pages on hometrust.ca and 11 external pages.
4 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “Home Trust Company: Canada’s One Stop Mortgage Lender offering Mortgage, Visa card, and Deposit products.”.
Canonical URL set
The canonical URL is https://www.hometrust.ca/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://hometrust.ca/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://hometrust.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (279 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages share a title
https://hometrust.ca/brokerlogin, https://hometrust.ca/fr-ca, https://hometrust.ca/mortgages, https://hometrust.ca/mortgages/purchases, https://hometrust.ca/mortgages/refinances and https://hometrust.ca/mortgages/renewing-your-mortgage and 9 others all use the title “Radware Captcha Page”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://hometrust.ca/brokerlogin, https://hometrust.ca/fr-ca, https://hometrust.ca/mortgages, https://hometrust.ca/mortgages/purchases, https://hometrust.ca/mortgages/refinances and https://hometrust.ca/mortgages/renewing-your-mortgage and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages with very little text
https://hometrust.ca/brokerlogin, https://hometrust.ca/fr-ca, https://hometrust.ca/mortgages, https://hometrust.ca/mortgages/purchases, https://hometrust.ca/mortgages/refinances and https://hometrust.ca/mortgages/renewing-your-mortgage and 9 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
30 small tap targets
30 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “googletagmanager is not defined”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
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.
Local business without LocalBusiness data
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.
Thin social proof
Social proof on the homepage: 7 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 187 words
The homepage has only about 187 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
5 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us” and “Contact”.
2 short forms
2 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Hotjar and Umami.
Phone number on the homepage
Your phone number is on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
33 cookies set on arrival
33Opening the homepage sets 33 cookies (measured from a US location before any click).
25 other companies contacted
Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 hometrust.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Radware Cloud Services
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on hometrust.ca, including 21 speed issues, 4 SEO issues 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.