Programmable

Website review, no card needed

247sales.ca logo

247sales.ca website review

Visit site (opens in a new tab)Reviewed 12 November 202632 issues · 83 checks

This review found 32 issues worth fixing on 247sales.ca, 8 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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

Site score

81B

Closest competitors among SaaS websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.3 s1.9 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20263.0 s
Jun 13, 20262.9 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.7 s
Jul 11, 20262.8 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20262.7 s
Aug 22, 20262.3 s
Aug 29, 20262.4 s
Sep 5, 20262.1 s
Sep 12, 20262.2 s
Sep 19, 20262.7 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.9 s
Oct 24, 20262.5 s
Oct 31, 20262.9 s
Nov 7, 20262.2 s

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

www.ixactcontact.com (opens in a new tab)
Full-page screenshot of 247sales.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix53

  • Reduce unused JavaScript

    5.5 s · 806 KiB

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

  • Use efficient cache lifetimes

    2.4 s · 326 KiB

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

  • Render-blocking requests

    2.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 1.8 MB and 982 ms of main-thread time.

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    670 ms · 98 KiB

    About 98 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 670 ms faster on a phone.

  • Improve image delivery

    400 ms · 108 KiB

    5 images could be 108 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • Google CDN adds 392 ms

    392 ms

    Google CDN costs a phone 392 ms of main-thread work and 774 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.

  • Google Tag Manager adds 293 ms

    293 ms

    Google Tag Manager costs a phone 293 ms of main-thread work and 556 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.6 s

    A phone's processor spends 2.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Facebook adds 178 ms

    178 ms

    Facebook costs a phone 178 ms of main-thread work and 349 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.

  • 14 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • Minify JavaScript

    6 KiB

    6 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: 2 ms

    2 ms

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

Core Web Vitals

6 to fix100

  • First Contentful Paint: 7.6 s

    7.6 s

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

  • Largest Contentful Paint: 15.8 s

    15.8 s

    Your largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 15.9 s

    15.9 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Total Blocking Time: 230 ms

    230 ms

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

6 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.3 s

    2.3 s

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

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

    1.0 s

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

  • Real-user TTFB: 656 ms

    656 ms

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

2 to fix75

  • Page weight: 2.7 MB in 73 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 73 requests on a phone: scripts 1.8 MB (24), other files 364 KiB (16) and fonts 225 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    38 KiB

    1 image is downloaded at several times the size a phone draws it, for example backgroundMobile.png at 800 px wide, shown at 130 px. Resized copies would save about 38 KiB.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

2 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 9791

  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Contentinfo landmark should not be contained in another landmark (3 elements)

    Contentinfo landmark should not be contained in another landmark: 3 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 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.

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 63 images in the HTML carry an alt attribute.

  • 44 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: 44 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9291

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization, Product and WebPage) but with 1 problem, for example “Product: no offers (price) block”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • 86 internal links, 11 external

    The homepage links to 86 pages on 247sales.ca and 11 external pages.

6 checks passed

  • Meta description: 125 characters

    Your meta description is 125 characters: “All-in-One Real Estate CRM and Marketing Automation System. Incredible Value. Explore the Best CRM for Realtors. Try It…”.

  • One H1 headline

    Your main headline reads: “Real Estate CRM Software”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Best Real Estate CRM & Marketing Automation | IXACT Contact”.

  • Canonical URL set

    The canonical URL is https://www.ixactcontact.com/.

  • 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.ixactcontact.com/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

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

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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,100 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 29 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 14 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 14 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

    37 of 37 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100

  • No form on the homepage

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

  • About 1,033 words of copy

    The homepage carries about 1,033 words of visible text.

6 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “PRICING” and “Contact Us”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “IXACT Contact”, “Free Trial” and “Pricing”.

  • Social proof on the page

    Social proof on the homepage: 26 testimonial or review blocks, 3 customer or partner logos, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, Hotjar and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 3 email links.

  • 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 to fix

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 1 more (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (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.

  • 20 other companies contacted

    Loading the homepage contacts 20 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 247sales.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 Analytics | Hotjar
Hosting
AWS

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 247sales.ca, including 17 speed issues and 3 SEO issues. 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