Website review, no card needed

abovebeyondrs.com logo

abovebeyondrs.com website review

Visit site (opens in a new tab)Reviewed 16 November 202647 issues · 90 checks

This review found 47 issues worth fixing on abovebeyondrs.com, 20 of them high impact, across 90 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 abovebeyondrs.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abovebeyondrs.com at 0.4 s0.4 s
  2. abovebeyondrs.com at 0.8 s0.8 s
  3. abovebeyondrs.com at 1.1 s1.1 s
  4. abovebeyondrs.com at 1.5 s1.5 s
  5. abovebeyondrs.com at 1.9 s1.9 s
  6. abovebeyondrs.com at 2.3 s2.3 s
  7. abovebeyondrs.com at 2.7 s2.7 s
  8. abovebeyondrs.com at 3.1 s3.1 s

Speed

11 to fix52
  • Reduce unused JavaScript

    5.2 s · 1.1 MB

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

  • Improve image delivery

    4.7 s · 1.2 MB

    7 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.7 s faster on a phone.

  • Use efficient cache lifetimes

    2.9 s · 373 KiB

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

  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    1.4 s · 276 KiB

    About 276 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Maps, Google CDN and Other Google APIs/SDKs and others), adding 1.6 MB and 1.1 s of main-thread time.

  • Mobile performance score: 52

    52/100

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

  • Google Maps adds 338 ms

    338 ms

    Google Maps costs a phone 338 ms of main-thread work and 407 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 CDN adds 240 ms

    240 ms

    Google CDN costs a phone 240 ms of main-thread work and 357 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.

  • Main-thread work: 2.3 s

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

  • atm.gs adds 142 ms

    142 ms

    atm.gs costs a phone 142 ms of main-thread work and 413 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.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    130 ms · 8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • 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: 3 ms

    3 ms

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

Core Web Vitals

6 to fix60
  • Largest Contentful Paint: 22.1 s

    22.1 s

    Your largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Real Solutions for Real Estate We're here to simplify your …”.

  • Time to Interactive: 22.4 s

    22.4 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • Total Blocking Time: 285 ms

    285 ms

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

  • 12 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

5 to fix28
  • Page weight: 4.2 MB in 94 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 94 requests on a phone: images 2.4 MB (22), scripts 1.2 MB (36) and stylesheets 325 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    03c9f55e530f661b07be3fbd6315ad05cfdd430e.jpg weighs 655 KiB. On a phone connection a single image that size takes seconds.

  • 8 images in older formats

    8 images (1.7 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.

  • 4 images below the first screen load straight away

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

  • 1 image far larger than shown

    140 KiB

    1 image is downloaded at several times the size a phone draws it, for example Photoxpress_5165072.jpg at 1,500 px wide, shown at 370 px. Resized copies would save about 140 KiB.

  • About 1.2 g of CO₂ per visit

    1.18 g

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

Accessibility

9 to fixGoogle 8086
  • 75 text elements with low contrast

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

  • Links must have discernible text (8 elements)

    Links must have discernible text: 8 elements on the page fail this check, rated serious by axe-core.

  • Positive tabindex

    8 elements have a tabindex above 0, which scrambles the keyboard order.

  • 4 tap targets too small

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

  • 8 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 15 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

6 to fixGoogle 7773
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Real Solutions for Real Estate”, “Our goal is to impact as many lives in a positive…” and “Real Solutions for Real Estate”). One clear main headline is easier for people and search engines.

  • 8 links with vague text

    8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 100 internal links, 1 external

    The homepage links to 100 pages on abovebeyondrs.com and 1 external page.

5 checks passed
  • Title: 60 characters

    Your title is a healthy 60 characters: “Authority Site -v1- Home - Above and Beyond Realty Solutions”.

  • Canonical URL set

    The canonical URL is https://www.abovebeyondrs.com/.

  • Structured data in place

    Structured data found: WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at http://www.abovebeyondrs.com/sitemap.xml.gz.

AI search readiness

2 to fix53
  • robots.txt blocks 5 AI answer engine crawlers

    5 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (1,466 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.abovebeyondrs.com/buyer-1-home, https://www.abovebeyondrs.com/buyer-1-home/buyer-1-american-dream, https://www.abovebeyondrs.com/buyer-1-home/buyer-1-hidden-savings-secret, https://www.abovebeyondrs.com/buyer-1-home/buyer-1-a-true-win-win, https://www.abovebeyondrs.com/buyer-1-home/buyer-1-the-best-home-for-you and https://www.abovebeyondrs.com/buyer-1-home/buyer-1-creative-financing and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.abovebeyondrs.com/seller-home/seller-already-moved has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.abovebeyondrs.com/seller-home/seller-already-moved took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

2 to fixGoogle 7387
  • 10 small tap targets

    10 of 16 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 “You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors.”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 8-field form

    Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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,491 words of copy

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us Today!”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “BUY”, “WHY BUY…” and “- Request a Showing”.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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
  • 1 tracker load before any consent

    1

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

  • 2 cookies set on arrival

    2

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 abovebeyondrs.com, 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 47 issues on abovebeyondrs.com, including 17 speed issues, 6 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