Website review, no card needed
155burgessrd.com website review
Visit site (opens in a new tab)Reviewed 21 November 202642 issues · 93 checks
This review found 42 issues worth fixing on 155burgessrd.com, 16 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.8 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 120 ms |
| Jul 4, 2026 | 125 ms |
| Jul 11, 2026 | 127 ms |
| Aug 1, 2026 | 142 ms |
| Aug 8, 2026 | 158 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 143 ms |
| Aug 29, 2026 | 161 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 160 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 187 ms |
| Oct 10, 2026 | 205 ms |
| Oct 17, 2026 | 211 ms |
| Oct 24, 2026 | 204 ms |
| Oct 31, 2026 | 191 ms |
| Nov 7, 2026 | 169 ms |
| Nov 14, 2026 | 185 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
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.2 s
4.9 s
5.6 s
Speed
Reduce unused JavaScript
1.8 s · 966 KiBAbout 966 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 1.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 36
36/100Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and cloudflare.com and others), adding 2.6 MB and 1.9 s of main-thread time.
Use efficient cache lifetimes
300 ms · 1.5 MB28 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Improve image delivery
150 ms · 422 KiB4 images could be 422 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
350 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 341 ms. During a long task the page ignores taps.
Facebook adds 261 ms
261 msFacebook costs a phone 261 ms of main-thread work and 274 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.
luxurypresence.com adds 156 ms
156 msluxurypresence.com costs a phone 156 ms of main-thread work and 524 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.
1,872 HTML elements
The page has 1,872 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
150 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Reduce unused CSS
70 KiBAbout 70 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
53 KiBPolyfills for old browsers add 53 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 61 ms
61 msYour server sent the HTML in 61 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 17.0 s
17.0 sYour largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PENTHOUSE QUEEN & LUXURY PROPERTIES”.
Time to Interactive: 32.8 s
32.8 sThe page becomes fully interactive after 32.8 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 791 ms
791 msScripts block taps and scrolling for 791 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 44% slower for real visitors
+44%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 120 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 941 ms
941 msReal visitors wait 941 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.169
0.169The layout shifts by 0.169 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 193 ms
193 msReal visitors wait 193 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 8.7 MB in 135 requests
8.7 MBYour homepage downloads 8.7 MB in 135 requests on a phone: HTML 3.1 MB (17), images 3.0 MB (45) and scripts 2.5 MB (37). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (790 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.
1 image far larger than shown
96 KiB1 image is downloaded at several times the size a phone draws it, for example claudinemontano_penthousequeen2v2 at 1,500 px wide, shown at 325 px. Resized copies would save about 96 KiB.
1 image below the first screen load straight away
1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.48 g of CO₂e: 297.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 31 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
42 links with vague text
42 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
81 internal links, 28 external
The homepage links to 81 pages on 155burgessrd.com and 28 external pages.
7 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Penthouse Queen provides Toronto’s Finest Penthouses and Luxury Properties delivered with Concierge & expertise-built o…”.
One H1 headline
Your main headline reads: “Top Ranked Toronto Real Estate Broker”.
Title: 37 characters
Your title is a healthy 37 characters: “Penthouse Queen | Toronto Real Estate”.
Canonical URL set
The canonical URL is https://penthousequeen.com/.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://penthousequeen.com/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,618 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://penthousequeen.com/llms.txt (195 KiB, 656 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://penthousequeen.com/home-valuation has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://penthousequeen.com/home-search/listings has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 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.
Titles are unique
Every page we checked has its own title.
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
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 2,271 words of copy
The homepage carries about 2,271 words of visible text.
6 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Join Us”, “Shop the Collection” and “Contact Us”.
2 short forms
2 short forms (7 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 21 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Umami and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
24 other companies contacted
Loading the homepage contacts 24 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 155burgessrd.com, 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 Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on 155burgessrd.com, including 22 speed issues, 2 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.