Website review, no card needed

revive.realestate logo

revive.realestate website review

Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 95 checks

This review found 32 issues worth fixing on revive.realestate, 14 of them high impact, across 95 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

Real-visitor load time (LCP)75th percentile, phones
4.4 s1.1 sMay 9Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20263.9 s
May 23, 20263.6 s
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.6 s
Jul 4, 20263.6 s
Jul 11, 20263.7 s
Jul 18, 20263.7 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.3 s
Aug 15, 20263.2 s
Aug 22, 20263.4 s
Aug 29, 20263.1 s
Sep 5, 20262.9 s
Sep 12, 20262.3 s
Sep 19, 20261.7 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.6 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
403 ms102 msMay 9Oct 17183 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026322 ms
May 16, 2026341 ms
May 23, 2026343 ms
May 30, 2026340 ms
Jun 6, 2026340 ms
Jun 13, 2026368 ms
Jun 20, 2026321 ms
Jun 27, 2026342 ms
Jul 4, 2026338 ms
Jul 11, 2026273 ms
Jul 18, 2026252 ms
Jul 25, 2026222 ms
Aug 1, 2026235 ms
Aug 8, 2026250 ms
Aug 15, 2026261 ms
Aug 22, 2026277 ms
Aug 29, 2026270 ms
Sep 5, 2026197 ms
Sep 12, 2026162 ms
Sep 19, 2026137 ms
Sep 26, 2026137 ms
Oct 3, 2026148 ms
Oct 10, 2026161 ms
Oct 17, 2026183 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 revive.realestate (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. revive.realestate at 1.2 s1.2 s
  2. revive.realestate at 2.4 s2.4 s
  3. revive.realestate at 3.6 s3.6 s
  4. revive.realestate at 4.8 s4.8 s
  5. revive.realestate at 6.0 s6.0 s
  6. revive.realestate at 7.3 s7.3 s
  7. revive.realestate at 8.5 s8.5 s
  8. revive.realestate at 9.7 s9.7 s

Speed

11 to fix26
  • Reduce unused JavaScript

    2.9 s · 1.6 MB

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

  • Render-blocking requests

    3.8 s

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

  • Main-thread work: 12.2 s

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

  • Mobile performance score: 26

    26/100

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

  • Use efficient cache lifetimes

    450 ms · 2.8 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (hsappstatic.net, website-files.com and Google Tag Manager and others), adding 5.2 MB and 2.2 s of main-thread time.

  • website-files.com adds 547 ms

    547 ms

    website-files.com costs a phone 547 ms of main-thread work and 3.5 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.

  • hsappstatic.net adds 741 ms

    741 ms

    hsappstatic.net costs a phone 741 ms of main-thread work and 781 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.

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 266 ms

    266 ms

    Google Tag Manager costs a phone 266 ms of main-thread work and 379 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,755 HTML elements

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

  • Reduce unused CSS

    150 ms · 124 KiB

    About 124 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.

  • Legacy JavaScript

    150 ms · 114 KiB

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

  • Improve image delivery

    157 KiB

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

  • Minify JavaScript

    21 KiB

    21 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 60 but mobile only 26. 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.

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

    4 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 12.2 s

    12.2 s

    Your largest element takes 12.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: 37.8 s

    37.8 s

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

  • Total Blocking Time: 2.8 s

    2.8 s

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

  • Speed Index: 11.7 s

    11.7 s

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

  • 47 images without width and height

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

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.9 s

    1.9 s

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

  • Real-user INP: 179 ms

    179 ms

    Real visitors wait 179 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.7 s

    1.7 s

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

  • Real-user TTFB: 559 ms

    559 ms

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

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

    -48%

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

  • Largest content (LCP) got 56% faster for real visitors

    -56%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 7.1 MB in 234 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 234 requests on a phone: scripts 3.7 MB (77), media 1.9 MB (2) and fonts 630 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    2.02 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.02 g of CO₂e: 242.8 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

6 to fixGoogle 8893
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 3 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 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 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h6, h4 → h6 and h1 → 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. (1 element).

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • 3 H1 headlines

    There are 3 <h1> headlines (“Find the potential in your home”, “Champion homeowners, always” and “The future starts at home.”). One clear main headline is easier for people and search engines.

  • 102 internal links, 14 external

    The homepage links to 102 pages on revive.realestate and 14 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Transform your home with Revive's expert remodeling services. Enjoy no upfront costs, professional guidance, and a stre…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Home Remodeling Services That Help Maximize Home Value”.

  • Canonical URL set

    The canonical URL is https://www.revive.realestate/.

  • Structured data in place

    Structured data found: HomeAndConstructionBusiness and WebSite.

  • 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.revive.realestate/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

1 to fix98
  • 4 pages share a meta description

    https://www.revive.realestate/solutions/sell-360 and https://www.revive.realestate/solutions/flip-360 use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 72 found) and read each the way a search engine does.

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

5 to fixGoogle 3173
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187265037&tm=gtm002&Ver=2&mid=07e8f02a-4e5a-486c-a364-5c473d31da12&bo=1&sid=bbe7b980cd5011f1989c7b121713d7e8&vid=bbe7d640cd5011f1bd7d338340d1cfd2&vids=1&msclkid=N&gtm_.

  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

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

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    11 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • 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.

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

    The homepage carries about 877 words of visible text.

9 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Learn more with an intro call” and “Schedule intro call”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

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

  • 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

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, HubSpot, LinkedIn Insight and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies, 2 of them by other companies (measured from a US location before any click).

  • 68 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 revive.realestate, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Framework
Tailwind CSS
Analytics
Google Tag Manager

Hiring

Hiring
1 open role
Teams
Engineering (1)
Job board
ashby

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on revive.realestate, including 17 speed issues, 1 SEO issue 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