Website review, no card needed

406mtproperty.com logo

406mtproperty.com website review

Visit site (opens in a new tab)Reviewed 17 November 202645 issues · 91 checks

This review found 45 issues worth fixing on 406mtproperty.com, 18 of them high impact, across 91 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 406mtproperty.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 406mtproperty.com at 0.8 s0.8 s
  2. 406mtproperty.com at 1.5 s1.5 s
  3. 406mtproperty.com at 2.3 s2.3 s
  4. 406mtproperty.com at 3.1 s3.1 s
  5. 406mtproperty.com at 3.8 s3.8 s
  6. 406mtproperty.com at 4.6 s4.6 s
  7. 406mtproperty.com at 5.3 s5.3 s
  8. 406mtproperty.com at 6.1 s6.1 s

Speed

13 to fix47
  • Reduce unused JavaScript

    7.7 s · 1.4 MB

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

  • Use efficient cache lifetimes

    5.5 s · 1.2 MB

    48 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 47

    47/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, datafloat.com and Google Maps and others), adding 5.6 MB and 1.5 s of main-thread time.

  • Improve image delivery

    400 ms · 887 KiB

    30 images could be 887 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • datafloat.com adds 321 ms

    321 ms

    datafloat.com costs a phone 321 ms of main-thread work and 3.2 MB 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 Tag Manager adds 439 ms

    439 ms

    Google Tag Manager costs a phone 439 ms of main-thread work and 630 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.

  • Legacy JavaScript

    450 ms · 18 KiB

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

  • Google Maps adds 258 ms

    258 ms

    Google Maps costs a phone 258 ms of main-thread work and 803 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.9 s

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

  • 2,586 HTML elements

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

  • Google CDN adds 90 ms

    90 ms

    Google CDN costs a phone 90 ms of main-thread work and 358 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

    150 ms · 64 KiB

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

  • 14 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 5 KiB

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

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

    25 ms

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

Core Web Vitals

6 to fix54
  • Largest Contentful Paint: 28.2 s

    28.2 s

    Your largest element takes 28.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 35.2 s

    35.2 s

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

  • Speed Index: 12.8 s

    12.8 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Total Blocking Time: 450 ms

    450 ms

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

  • 6 images without width and height

    6 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

    0

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

Images and page weight

4 to fix35
  • Page weight: 6.3 MB in 177 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 177 requests on a phone: images 3.1 MB (60), scripts 2.6 MB (36) and fonts 258 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    0727202619150054211.jpg weighs 551 KiB. On a phone connection a single image that size takes seconds.

  • 4 images in older formats

    4 images (1.0 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.

  • 2 images far larger than shown

    311 KiB

    2 images are downloaded at several times the size a phone draws them, for example 0727202619145537651.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 311 KiB.

  • About 1.8 g of CO₂ per visit

    1.79 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

10 to fixGoogle 7684
  • 14 text elements with low contrast

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

  • Interactive controls must not be nested (12 elements)

    Interactive controls must not be nested: 12 elements on the page fail this check, rated serious by axe-core.

  • autocomplete attribute must be used correctly (2 elements)

    autocomplete attribute must be used correctly: 2 elements on the page fail this check, rated serious by axe-core.

  • Positive tabindex

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 form fields without a label

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • 86 links crawlers can't follow

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Cortney Andersen” and “Find Your Dream Home”). One clear main headline is easier for people and search engines.

  • Meta description is long (216 characters)

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

  • Structured data has 1 problem

    Structured data found (RealEstateAgent) but with 1 problem, for example “RealEstateAgent: image is not an absolute URL ("https://cdn.datafloat.com/ROG_PUBLIC/image_cache/AG…”.

  • No X (Twitter) card tag

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

  • 32 internal links, 4 external

    The homepage links to 32 pages on 406mtproperty.com and 4 external pages.

5 checks passed
  • Title: 59 characters

    Your title is a healthy 59 characters: “Cortney Andersen, Real Estate Agent | Realty ONE Group Peak”.

  • Canonical URL set

    The canonical URL is https://www.406mtproperty.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://www.406mtproperty.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 description. 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.406mtproperty.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 (500 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 5 linked pages hidden from search

    https://www.406mtproperty.com/property-search-map/sale/status-active;pending/type-single%20family;condo!townhouse;land;Multi_Family;farm;mobile!manufactured/dsort-n, https://www.406mtproperty.com/mortgage-calculator, https://www.406mtproperty.com/communities, https://www.406mtproperty.com/accessibility-policy and https://www.406mtproperty.com/dmca-notice are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a meta description

    https://www.406mtproperty.com/mortgage-calculator, https://www.406mtproperty.com/accessibility-policy and https://www.406mtproperty.com/dmca-notice use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://www.406mtproperty.com/my-home-value 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.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    10 pages of 11 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 17 small tap targets

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

  • 2 JavaScript errors while loading

    2 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.”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • A 8-field form

    Your longest form asks for 8 fields (3 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 818 words of copy

    The homepage carries about 818 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SIGN IN / SIGN UP” and “CONTACT”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Sign In / Sign Up”, “CONTACT” and “Subscribe to our Market Reports”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.

  • 14 cookies set on arrival

    14

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 406mtproperty.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
NTT Managed Services Americas, LLC

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on 406mtproperty.com, including 19 speed issues, 4 SEO issues and 1 conversion gap. 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