Website review, no card needed
assomption.ca website review
Visit site (opens in a new tab)Reviewed 29 October 202634 issues · 80 checks
This review found 34 issues worth fixing on assomption.ca, 13 of them high impact, across 80 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
7.3 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.3 s.
Use efficient cache lifetimes
4.8 s · 1,003 KiB40 files are served with short cache lifetimes, so returning visitors download them again (1,003 KiB).
Reduce unused CSS
3.1 s · 609 KiBAbout 609 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Reduce unused JavaScript
1.6 s · 291 KiBAbout 291 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Minify CSS
1.1 s · 183 KiB183 KiB could be saved by minifying CSS.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (jQuery CDN, Didomi and Google Tag Manager and others), adding 453 KiB and 727 ms of main-thread time.
jQuery CDN adds 369 ms
369 msjQuery CDN costs a phone 369 ms of main-thread work and 33 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.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
200 ms · 231 KiB4 images could be 231 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 220 ms. During a long task the page ignores taps.
Minify JavaScript
160 ms · 41 KiB41 KiB could be saved by minifying JavaScript.
Document request latency
34 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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: 46 ms
46 msYour server sent the HTML in 46 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 7.6 s
7.6 sThe first text or image appears after 7.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 21.0 s
21.0 sYour largest element takes 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “With your agreement, we and our 5 partners use cookies or s…”.
Time to Interactive: 21.1 s
21.1 sThe page becomes fully interactive after 21.1 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 291 ms
291 msScripts block taps and scrolling for 291 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 70 requests
3.7 MBYour homepage downloads 3.7 MB in 70 requests on a phone: images 2.3 MB (24), scripts 657 KiB (24) and stylesheets 657 KiB (14). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
65 KiB1 image is downloaded at several times the size a phone draws it, for example Certifications-EN.png at 2,284 px wide, shown at 333 px. Resized copies would save about 65 KiB.
3 images in older formats
3 images (279 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.
2 images below the first screen load straight away
2 images further down the page (235 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 125.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Input buttons must have discernible text (1 element)
Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.
Unlabelled dropdowns
1 dropdown has no label.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
82 internal links, 6 external
The homepage links to 82 pages on assomption.ca and 6 external pages.
5 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “Access your online account to view your statements and account details. Not registered yet? Get access to your online a…”.
One H1 headline
Your main headline reads: “What We Offer”.
Title: 51 characters
Your title is a healthy 51 characters: “Assumption Life - For Individuals - Assumption Life”.
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.assomption.ca/sitemap.
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://assomption.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 (782 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages share a title
https://assomption.ca/en/home, https://assomption.ca/en/individuals, https://assomption.ca/en/individuals/insurance-coverage, https://assomption.ca/en/individuals/insurance-coverage/determining-your-needs, https://assomption.ca/en/individuals/insurance-coverage/term-life-insurance and https://assomption.ca/en/individuals/insurance-coverage/permanent-life-insurance and 6 others all use the title “Assumption Life - For Individuals - Assumption Life”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://assomption.ca/en/businesses-groups, https://assomption.ca/en/advisor-corner, https://assomption.ca/fr/home, https://assomption.ca/en/individuals, https://assomption.ca/en/individuals/insurance-coverage and https://assomption.ca/en/individuals/insurance-coverage/determining-your-needs and 9 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
6 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 a meta description
All 15 pages that loaded have a meta description.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
19 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 463 words of copy
The homepage carries about 463 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More →”.
7 calls to action
The homepage has 7 calls to action, for example “Contact Us” and “Learn more”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Didomi
A consent management tool (Didomi) 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 assomption.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
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Gtt Backbone Gtt
Company
- Founded
- 1903
- Headquarters
- Moncton
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on assomption.ca, including 15 speed issues, 4 SEO issues and 2 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.