Website review, no card needed
kwcapitalproperties.com website review
Visit site (opens in a new tab)Reviewed 26 October 202631 issues · 88 checks
This review found 31 issues worth fixing on kwcapitalproperties.com, 8 of them high impact, across 88 checks. The most urgent: fails Core Web Vitals for real visitors. 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 112 ms |
| May 16, 2026 | 128 ms |
| May 23, 2026 | 214 ms |
| May 30, 2026 | 213 ms |
| Jun 6, 2026 | 212 ms |
| Jun 13, 2026 | 212 ms |
| Jun 20, 2026 | 117 ms |
| Jun 27, 2026 | 115 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 115 ms |
| Jul 18, 2026 | 115 ms |
| Jul 25, 2026 | 117 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 174 ms |
| Aug 15, 2026 | 226 ms |
| Aug 22, 2026 | 226 ms |
| Aug 29, 2026 | 184 ms |
| Sep 5, 2026 | 130 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 119 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 107 ms |
| Oct 10, 2026 | 107 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 107 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
150 ms · 1.1 MB24 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Mobile performance score: 70
70/100Your mobile performance score is 70 (desktop: 73). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, luxurypresence.com and Other Google APIs/SDKs and others), adding 1.3 MB and 559 ms of main-thread time.
Reduce unused JavaScript
555 KiBAbout 555 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 264 ms
264 msGoogle Tag Manager costs a phone 264 ms of main-thread work and 422 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 111 ms
111 msluxurypresence.com costs a phone 111 ms of main-thread work and 509 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.
Improve image delivery
242 KiB4 images could be 242 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 156 ms. During a long task the page ignores taps.
Legacy JavaScript
42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need.
Reduce unused CSS
36 KiBAbout 36 KiB of CSS is downloaded but never applied on this page.
Duplicated JavaScript
26 KiB26 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
7 KiB7 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 607 ms of it running JavaScript. That is comfortably low.
Server response: 70 ms
70 msYour server sent the HTML in 70 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.
Time to Interactive: 14.2 s
14.2 sThe page becomes fully interactive after 14.2 s. Good is under 3.8 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HOME OF IMPACT-DRIVEN ENTREPRENEURS”.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user TTFB: 906 ms
906 msReal visitors wait 906 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 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
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 107 ms
107 msReal visitors wait 107 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.04
0.04The layout barely moves while loading (CLS 0.04, good is under 0.1).
Total Blocking Time: 85 ms
85 msScripts block the page for only 85 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.1 MB in 79 requests
3.1 MBYour homepage downloads 3.1 MB in 79 requests on a phone: images 1.6 MB (23), scripts 1.3 MB (29) and HTML 132 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 22 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
74 internal links, 15 external
The homepage links to 74 pages on kwcapitalproperties.com and 15 external pages.
7 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Looking for top-notch Maryland Real Estate services? Visit Keller Williams Capital Properties' homepage for expert real…”.
One H1 headline
Your main headline reads: “Home of impact-driven entrepreneurs”.
Title: 58 characters
Your title is a healthy 58 characters: “Keller Williams Capital Properties | Real Estate Brokerage”.
Canonical URL set
The canonical URL is https://kwcapitalproperties.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://kwcapitalproperties.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 (822 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://kwcapitalproperties.com/llms.txt (193 KiB, 962 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://kwcapitalproperties.com/blog is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without an H1
https://kwcapitalproperties.com/home-valuation has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://kwcapitalproperties.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.
5 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 a title
All 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
2 checks passed
Tap targets are thumb-sized
12 of 12 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.
A 8-field form
Your longest form asks for 8 fields (6 required). Every extra field lowers completion.
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 598 words of copy
The homepage carries about 598 words of visible text.
5 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Join KWCP”, “Contact Us” and “Join Us”.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Umami and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 10 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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
19 other companies contacted
Loading the homepage contacts 19 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 kwcapitalproperties.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
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on kwcapitalproperties.com, including 14 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.