Website review, no card needed

crescentheights.com logo

crescentheights.com website review

Visit site (opens in a new tab)Reviewed 17 November 202626 issues · 79 checks

This review found 26 issues worth fixing on crescentheights.com, 9 of them high impact, across 79 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
4.8 s3.2 sMay 30Nov 144.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.3 s
Jun 6, 20264.3 s
Jun 13, 20264.3 s
Jun 20, 20263.7 s
Jun 27, 20263.8 s
Jul 4, 20263.8 s
Jul 11, 20263.8 s
Jul 18, 20264.3 s
Jul 25, 20264.6 s
Aug 1, 20264.2 s
Aug 8, 20264.1 s
Aug 15, 20263.7 s
Aug 22, 20263.4 s
Aug 29, 20263.8 s
Sep 5, 20264.1 s
Sep 12, 20264.4 s
Sep 19, 20264.6 s
Sep 26, 20264.3 s
Oct 3, 20263.9 s
Oct 10, 20263.7 s
Oct 17, 20263.9 s
Oct 24, 20264.0 s
Oct 31, 20264.0 s
Nov 7, 20264.0 s
Nov 14, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
82 ms56 msMay 30Nov 1472 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202663 ms
Jun 6, 202664 ms
Jun 13, 202671 ms
Jun 20, 202666 ms
Jun 27, 202667 ms
Jul 4, 202662 ms
Jul 11, 202659 ms
Jul 18, 202669 ms
Jul 25, 202670 ms
Aug 1, 202670 ms
Aug 8, 202679 ms
Aug 15, 202678 ms
Aug 22, 202672 ms
Aug 29, 202679 ms
Sep 5, 202678 ms
Sep 12, 202670 ms
Oct 3, 202662 ms
Oct 24, 202664 ms
Oct 31, 202670 ms
Nov 7, 202671 ms
Nov 14, 202672 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 crescentheights.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crescentheights.com at 1.1 s1.1 s
  2. crescentheights.com at 2.2 s2.2 s
  3. crescentheights.com at 3.4 s3.4 s
  4. crescentheights.com at 4.5 s4.5 s
  5. crescentheights.com at 5.6 s5.6 s
  6. crescentheights.com at 6.7 s6.7 s
  7. crescentheights.com at 7.8 s7.8 s
  8. crescentheights.com at 9.0 s9.0 s

Speed

4 to fix78
  • Use efficient cache lifetimes

    2.1 s · 384 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (cloudfront.net), adding 11.6 MB and 0 ms of main-thread time.

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 11.6 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.

  • Mobile performance score: 78

    78/100

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

  • Improve image delivery

    150 ms · 38 KiB

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

  • Reduce unused CSS

    150 ms · 11 KiB

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

  • 6 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 418 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

8 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.7 s

    3.7 s

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

  • Real-user TTFB: 3.5 s

    3.5 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • Largest Contentful Paint: 3.9 s

    3.9 s

    Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ch Fallback”. Most of its time is resource load delay (7.7 s).

  • Time to Interactive: 3.9 s

    3.9 s

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

  • 1 image without width and height

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

  • Tap response (INP) got 13% slower for real visitors

    +13%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

5 checks passed
  • Real-user INP: 72 ms

    72 ms

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

  • Total Blocking Time: 65 ms

    65 ms

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

  • Cumulative Layout Shift: 0.016

    0.016

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix70
  • Page weight: 12.0 MB in 28 requests

    12.0 MB

    Your homepage downloads 12.0 MB in 28 requests on a phone: media 11.6 MB (2), fonts 188 KiB (9) and images 96 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 3.4 g of CO₂ per visit

    3.41 g

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

2 to fixGoogle 9797
  • 6 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

5 to fixGoogle 9280
  • Title is short (23 characters)

    Your title is only 23 characters: “Crescent Heights | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, LocalBusiness, Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

  • No social preview image

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

  • No robots.txt

    There is no robots.txt at crescentheights.com/robots.txt, the first file search crawlers ask for.

  • 6 links with vague text

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

  • 109 internal links, 6 external

    The homepage links to 109 pages on crescentheights.com and 6 external pages.

4 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Crescent Heights is the nation's leading urban real estate firm, specializing in the development, ownership, and operat…”.

  • One H1 headline

    Your main headline reads: “AMERICA'S PREMIER URBAN REAL ESTATE DEVELOPER”.

  • Canonical URL set

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.crescentheights.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix93
  • 14 pages share a meta description

    https://www.crescentheights.com/about/track-record, https://www.crescentheights.com/about/ch-overview, https://www.crescentheights.com/about/our-approach, https://www.crescentheights.com/about/leadership, https://www.crescentheights.com/about/awards and https://www.crescentheights.com/about/press and 4 others use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.crescentheights.com/portfolio/residential, https://www.crescentheights.com/portfolio/office and https://www.crescentheights.com/portfolio/historic-preservation have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://www.crescentheights.com/about/track-record, https://www.crescentheights.com/about/ch-overview, https://www.crescentheights.com/about/our-approach, https://www.crescentheights.com/about/leadership, https://www.crescentheights.com/portfolio/residential and https://www.crescentheights.com/portfolio/retail and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    14 pages of 15 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 14 pages that loaded have a meta description.

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 954 words of visible text.

6 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “LEARN MORE” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 16 testimonial or review blocks and 1 customer or partner logo.

  • Direct contact links

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

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

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 1 other company contacted

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

1 checks passed
  • 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 crescentheights.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
AWS

Company

Founded
1996
Headquarters
Miami Beach

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on crescentheights.com, including 12 speed issues, 5 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