remaxcentral.ab.ca website review

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

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

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

7 third-party services load with your homepage (myrealpage.com, Mapbox and JSDelivr CDN and others), adding 2.7 MB and 336 ms of main-thread time.

myrealpage.com costs a phone 215 ms of main-thread work and 1.9 MB 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.

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

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

unsplash.com costs a phone 0 ms of main-thread work and 317 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.

About 247 KiB of JavaScript is downloaded but never used on this page.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

36 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Calgary Real Estate Agents & Neighbourhood Experts Verified…”. Most of its time is resource load delay (8.6 s).

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

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

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

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

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

favicon_for_gssi_fa.png weighs 1,014 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example favicon_for_gssi_fa.png at 1,024 px wide, shown at 60 px. Resized copies would save about 1.3 MB.

Your homepage downloads 2.8 MB in 103 requests on a phone: images 1.9 MB (62), scripts 484 KiB (20) and fonts 317 KiB (5). Under 2 MB keeps phones on slow connections fast.

3 images (1.4 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 further down the page (353 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

4 links inside paragraphs rely on colour alone to stand out.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 80 characters, so Google will cut it off around 60: “Calgary REALTORS® Directory | Verified REALTOR® Referral & Neighbourhood Experts”.

There are 2 <h1> headlines (“Calgary Real Estate Agents& Neighbourhood Experts” and “Calgary REALTORS® – Neighbourhood Experts”). One clear main headline is easier for people and search engines.

Your meta description is 203 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 69 pages on remaxcentral.ab.ca and 9 external pages.

robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.real-estate-homes.ca/builders took over 3 s to send its HTML from our server.

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

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

8 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Bootstrap's JavaScript requires jQuery”.

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

Chrome logged issues while loading the page (“Cookie”).

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.