Website review, no card needed

merixfinancial.com logo

merixfinancial.com website review

Visit site (opens in a new tab)Reviewed 21 October 202630 issues · 79 checks

This review found 30 issues worth fixing on merixfinancial.com, 7 of them high impact, across 79 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.5 s702 msMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 2026910 ms
May 9, 2026924 ms
May 16, 2026924 ms
May 23, 2026915 ms
May 30, 2026926 ms
Jun 6, 2026930 ms
Jun 13, 2026937 ms
Jun 20, 2026946 ms
Jun 27, 2026948 ms
Jul 4, 2026952 ms
Jul 11, 2026959 ms
Jul 18, 2026958 ms
Jul 25, 20261.1 s
Aug 1, 20261.4 s
Aug 8, 20261.7 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
68 ms62 msMay 2Oct 1766 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202663 ms
May 9, 202663 ms
May 16, 202664 ms
May 23, 202664 ms
May 30, 202664 ms
Jun 6, 202666 ms
Jun 13, 202665 ms
Jun 20, 202666 ms
Jun 27, 202666 ms
Jul 4, 202665 ms
Jul 11, 202665 ms
Jul 18, 202663 ms
Jul 25, 202664 ms
Aug 1, 202664 ms
Aug 8, 202665 ms
Aug 15, 202667 ms
Aug 22, 202667 ms
Aug 29, 202665 ms
Sep 5, 202666 ms
Sep 12, 202665 ms
Sep 19, 202664 ms
Sep 26, 202664 ms
Oct 3, 202663 ms
Oct 10, 202664 ms
Oct 17, 202666 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

Full-page screenshot of merixfinancial.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. merixfinancial.com at 0.4 s0.4 s
  2. merixfinancial.com at 0.8 s0.8 s
  3. merixfinancial.com at 1.1 s1.1 s
  4. merixfinancial.com at 1.5 s1.5 s
  5. merixfinancial.com at 1.9 s1.9 s
  6. merixfinancial.com at 2.3 s2.3 s
  7. merixfinancial.com at 2.6 s2.6 s
  8. merixfinancial.com at 3.0 s3.0 s

Speed

5 to fix63
  • Improve image delivery

    5.8 s · 2.2 MB

    5 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.8 s faster on a phone.

  • Render-blocking requests

    2.6 s

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

  • Mobile performance score: 63

    63/100

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

  • Reduce unused CSS

    450 ms · 26 KiB

    About 26 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.

  • Minify CSS

    300 ms · 4 KiB

    4 KiB could be saved by minifying CSS.

  • Reduce unused JavaScript

    150 ms · 23 KiB

    About 23 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 70 ms. During a long task the page ignores taps.

  • 1 third-party service on the page

    1 third-party service load with your homepage (JSDelivr CDN), adding 89 KiB and 45 ms of main-thread time.

  • Phones get a much slower page than desktops

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

  • Use efficient cache lifetimes

    6 KiB

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

  • 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 169 ms of it running JavaScript. That is comfortably low.

  • Server response: 60 ms

    60 ms

    Your server sent the HTML in 60 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 12.7 s

    12.7 s

    Your largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We value your privacy By clicking “Accept All”, you consent…”.

  • Time to Interactive: 13.0 s

    13.0 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Largest content (LCP) got 123% slower for real visitors

    +123%

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

  • Speed Index: 5.2 s

    5.2 s

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

  • 3 images without width and height

    3 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-17, real Chrome visitors' tap response (inp) went from 63 ms to 66 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 62 ms

    62 ms

    Real visitors wait 62 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 604 ms

    604 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix53
  • 1 image over 500 KB

    welcome-mat_34c77f4.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.8 MB in 80 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 80 requests on a phone: images 2.3 MB (17), scripts 221 KiB (21) and fonts 141 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (2.3 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 below the first screen load straight away

    1 image further down the page (1.2 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.79 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9494
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (14 elements)

    All page content should be contained by landmarks: 14 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.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 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

5 to fixGoogle 10079
  • 4 H1 headlines

    There are 4 <h1> headlines (“We value your privacy”, “Hey! Welcome to MERIX Financial” and “What’s next for your homeownership journey?”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • Structured data has 1 problem

    Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token 'E', ..." Error - Ge"... is not va)”.

  • No XML sitemap

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

  • No robots.txt

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 89 internal links, 6 external

    The homepage links to 89 pages on merixfinancial.com and 6 external pages.

3 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “MERIX Financial is a trusted Canadian residential mortgage company offering tailored financing solutions to help make h…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Canadian Residential Mortgage Company | MERIX Financial”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix88
  • 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://www.merixfinancial.com/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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (503 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 9691
  • 3 small tap targets

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. 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 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 258 words of copy

    The homepage carries about 258 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 1 other company contacted

    Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 merixfinancial.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on merixfinancial.com, including 11 speed issues, 5 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25