Website review, no card needed

utahrealestate.com logo

utahrealestate.com website review

Visit site (opens in a new tab)Reviewed 11 October 202631 issues · 84 checks

This review found 31 issues worth fixing on utahrealestate.com, 10 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
1.3 s1.2 sApr 18Oct 31.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.3 s
Apr 25, 20261.3 s
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
222 ms136 msApr 18Oct 3156 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026212 ms
Apr 25, 2026211 ms
May 2, 2026204 ms
May 9, 2026204 ms
May 16, 2026200 ms
May 23, 2026197 ms
May 30, 2026199 ms
Jun 6, 2026195 ms
Jun 13, 2026195 ms
Jun 20, 2026188 ms
Jun 27, 2026178 ms
Jul 4, 2026173 ms
Jul 11, 2026163 ms
Jul 18, 2026155 ms
Jul 25, 2026149 ms
Aug 1, 2026146 ms
Aug 8, 2026150 ms
Aug 15, 2026158 ms
Aug 22, 2026166 ms
Aug 29, 2026170 ms
Sep 5, 2026171 ms
Sep 12, 2026161 ms
Sep 19, 2026161 ms
Sep 26, 2026160 ms
Oct 3, 2026156 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

Full-page screenshot of utahrealestate.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. utahrealestate.com at 0.4 s0.4 s
  2. utahrealestate.com at 0.8 s0.8 s
  3. utahrealestate.com at 1.2 s1.2 s
  4. utahrealestate.com at 1.6 s1.6 s
  5. utahrealestate.com at 2.0 s2.0 s
  6. utahrealestate.com at 2.4 s2.4 s
  7. utahrealestate.com at 2.8 s2.8 s
  8. utahrealestate.com at 3.2 s3.2 s

Speed

7 to fix65
  • Use efficient cache lifetimes

    1.5 s · 3.0 MB

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

  • Render-blocking requests

    2.6 s

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

  • Improve image delivery

    750 ms · 2.7 MB

    2 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    950 ms · 151 KiB

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 96). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    790 ms · 138 KiB

    About 138 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 790 ms faster on a phone.

  • Legacy JavaScript

    300 ms · 16 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 139 ms. During a long task the page ignores taps.

  • Font display

    100 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Bootstrap CDN, Cloudflare CDN and Google Fonts and others), adding 266 KiB and 5 ms of main-thread time.

  • Phones get a much slower page than desktops

    Desktop scores 96 but mobile only 65. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 80 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 7.1 s

    7.1 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • Time to Interactive: 7.2 s

    7.2 s

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 139 ms

    139 ms

    Real visitors wait 139 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 565 ms

    565 ms

    Real visitors wait 565 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 25% faster for real visitors

    -25%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 212 ms to 156 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.004

    0.004

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix50
  • 1 image over 500 KB

    marquee-13.webp weighs 2.7 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    2.3 MB

    1 image is downloaded at several times the size a phone draws it, for example marquee-13.webp at 5,824 px wide, shown at 767 px. Resized copies would save about 2.3 MB.

  • Page weight: 3.5 MB in 38 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 38 requests on a phone: images 2.9 MB (13), scripts 225 KiB (10) and fonts 207 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.00 g

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

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

Accessibility

6 to fixGoogle 7591
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 5 text elements with low contrast

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 75 tap targets too small

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

  • No main landmark

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 8591
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 101 internal links, 14 external

    The homepage links to 101 pages on utahrealestate.com and 14 external pages.

6 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Discover your dream home with UtahRealEstate.com. We offer the most up-to-date information on homes & REALTORS® in Utah…”.

  • One H1 headline

    Your main headline reads: “Utah Real Estate”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Utah Homes For Sale - MLS Listings | UtahRealEstate.com”.

  • Canonical URL set

    The canonical URL is https://www.utahrealestate.com/index/public.index.

  • 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.utahrealestate.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://utahrealestate.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 (420 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    https://utahrealestate.com/index/public.index and https://utahrealestate.com/index/public.index/type/1 all use the title “Utah Homes For Sale - MLS Listings | UtahRealEstate.com”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://utahrealestate.com/index/public.index/type/1, whose canonical is https://utahrealestate.com/index/public.index. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 7791
  • 9 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • About 480 words of copy

    The homepage carries about 480 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: “Join”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Join” and “Learn More”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • 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

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • 7 other companies contacted

    Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed
  • Consent tool: Ketch

    A consent management tool (Ketch) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 utahrealestate.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
Bootstrap
Analytics
Google Analytics | Google Tag Manager

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 utahrealestate.com, including 12 speed issues, 3 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

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