Website review, no card needed

1keyrealty.com logo

1keyrealty.com website review

Visit site (opens in a new tab)Reviewed 18 November 202647 issues · 89 checks

This review found 47 issues worth fixing on 1keyrealty.com, 19 of them high impact, across 89 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

Full-page screenshot of 1keyrealty.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

12 to fix39
  • Reduce unused JavaScript

    5.9 s · 1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.

  • Google CDN adds 1.2 s

    1.2 s

    Google CDN costs a phone 1.2 s of main-thread work and 2.6 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: 39

    39/100

    Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.9 s

    A phone's processor spends 5.9 s on main-thread work while loading, 3.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 CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 4.4 MB and 2.2 s of main-thread time.

  • Reduce unused CSS

    750 ms · 296 KiB

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

  • Render-blocking requests

    750 ms

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Use efficient cache lifetimes

    150 ms · 525 KiB

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

  • Google Tag Manager adds 387 ms

    387 ms

    Google Tag Manager costs a phone 387 ms of main-thread work and 467 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 Maps adds 192 ms

    192 ms

    Google Maps costs a phone 192 ms of main-thread work and 464 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,931 HTML elements

    The page has 1,931 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • real-estate-website.net adds 147 ms

    147 ms

    real-estate-website.net costs a phone 147 ms of main-thread work and 402 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

    195 KiB

    4 images could be 195 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 20 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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.

1 checks passed
  • Server response: 66 ms

    66 ms

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

Core Web Vitals

5 to fix49
  • First Contentful Paint: 11.2 s

    11.2 s

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

  • Largest Contentful Paint: 11.2 s

    11.2 s

    Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “>> condos for sale and rent >> homes for sale and rent >> r…”.

  • Time to Interactive: 36.7 s

    36.7 s

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

  • Speed Index: 13.0 s

    13.0 s

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

  • Total Blocking Time: 641 ms

    641 ms

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

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix50
  • Page weight: 7.8 MB in 261 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 261 requests on a phone: scripts 3.9 MB (160), images 1.8 MB (45) and other files 1.0 MB (11). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (589 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.

  • 2 images far larger than shown

    163 KiB

    2 images are downloaded at several times the size a phone draws them, for example 12_25_12.webp at 1,200 px wide, shown at 50 px. Resized copies would save about 163 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (229 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.22 g

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

Accessibility

13 to fixGoogle 7383
  • Certain ARIA roles must be contained by particular parents (8 elements)

    Certain ARIA roles must be contained by particular parents: 8 elements on the page fail this check, rated critical by axe-core.

  • Unlabelled dropdowns

    5 dropdowns have no label.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 32 text elements with low contrast

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

  • 18 tap targets too small

    18 tap targets are too small or too close together to hit reliably with a finger.

  • Links look like plain text

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

  • Frames without titles

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

  • 10 images without alt text

    10 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 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.

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

  • 26 form fields without a label

    26 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 13 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9285
  • 3 H1 headlines

    There are 3 <h1> headlines (“Leonardo Barnetche 7 Group Realty”, “Featured South Florida new developments” and “Newest offers – LISTED TODAY!”). One clear main headline is easier for people and search engines.

  • Meta description is long (388 characters)

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

  • No social preview image

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

  • 2 links crawlers can't follow

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

  • 74 internal links, 28 external

    The homepage links to 74 pages on 1keyrealty.com and 28 external pages.

5 checks passed
  • Title: 41 characters

    Your title is a healthy 41 characters: “Home - Leonardo Barnetche, 7 Group Realty”.

  • Canonical URL set

    The canonical URL is http://www.7grouprealty.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at http://www.7grouprealty.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

2 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,928 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://www.7grouprealty.com/homes, https://www.7grouprealty.com/author/intre, https://www.7grouprealty.com/monaco-yacht-club-residences, https://www.7grouprealty.com/26-edgewater-miami, https://www.7grouprealty.com/trump-royale-18201-collins-avenue-sunny-isles-beach and https://www.7grouprealty.com/the-fairchild-coconut-grove-miami and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.7grouprealty.com/market-report-all-cities-page, https://www.7grouprealty.com/new-developments, https://www.7grouprealty.com/condos, https://www.7grouprealty.com/homes, https://www.7grouprealty.com/blog and https://www.7grouprealty.com/advanced_search and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 38 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.

  • 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

3 to fixGoogle 6785
  • 28 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to set referrer policy: The value '' is not one of 'no-referrer', 'no-referrer-when-downgrade', 'origin', 'origi…”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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.

  • Thin social proof

    Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 1,010 words of copy

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

6 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “CONTACT US”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 2 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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 1keyrealty.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2020.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Foxcloud Foxcloud Llp

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on 1keyrealty.com, including 17 speed issues, 4 SEO issues 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

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