Website review, no card needed
ab-condos.ca website review
Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 72 checks
This review found 36 issues worth fixing on ab-condos.ca, 14 of them high impact, across 72 checks. The most urgent: improve image delivery. 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
62DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
2.8 s
5.6 s
8.4 s
11.1 s
13.9 s
16.7 s
19.5 s
22.3 s
Speed
Improve image delivery
3.7 s · 1.0 MB8 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.7 s faster on a phone.
Reduce unused JavaScript
3.2 s · 868 KiBAbout 868 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.
Render-blocking requests
1.9 s29 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Use efficient cache lifetimes
1.4 s · 233 KiB5 files are served with short cache lifetimes, so returning visitors download them again (233 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and PageSense and others), adding 1.2 MB and 1.1 s of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 838 ms
838 msGoogle Tag Manager costs a phone 838 ms of main-thread work and 829 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.
Reduce unused CSS
450 ms · 94 KiBAbout 94 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.
Legacy JavaScript
450 ms · 37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 269 ms. During a long task the page ignores taps.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
150 ms · 15 KiB15 KiB could be saved by minifying JavaScript.
Minify CSS
19 KiB19 KiB could be saved by minifying CSS.
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 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.7 s
16.7 sYour largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (11.0 s).
Speed Index: 23.7 s
23.7 sVisually, the page fills in at 23.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 21.6 s
21.6 sThe page becomes fully interactive after 21.6 s. Good is under 3.8 s.
Total Blocking Time: 540 ms
540 msScripts block taps and scrolling for 540 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 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.
2 checks passed
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.2 MB in 149 requests
4.2 MBYour homepage downloads 4.2 MB in 149 requests on a phone: images 2.2 MB (47), scripts 1.6 MB (45) and fonts 228 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 143.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
3 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 6 WCAG 2.2 A/AA and best-practice rules on the phone render: 3 passed and 3 failed. 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 long (116 characters)
Your title is 116 characters, so Google will cut it off around 60: “Ali Bahramikia, Century 21 Atria Realty Inc., Brokerage* | Richmond Hill Real Estate Agen…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (229 characters)
Your meta description is 229 characters; Google truncates after about 160, so the end of your pitch is cut.
17 links with vague text
17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
8 internal links, 1 external
The homepage links to 8 pages on ab-condos.ca and 1 external page.
4 checks passed
Canonical URL set
The canonical URL is https://www.ab-condos.ca/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.ab-condos.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://www.ab-condos.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.
1 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.
Other pages
1 page without a meta description
https://www.ab-condos.ca/terms-of-service has no meta description, so Google writes the search snippet from whatever text it finds.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 4 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 3 pages that loaded have a <title>.
Best practices
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look 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
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 20-field form
Your longest form asks for 20 fields (4 required). Every extra field lowers completion.
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 508 words of copy
The homepage carries about 508 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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 ab-condos.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on ab-condos.ca, including 16 speed issues, 6 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.