robson.com website review

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

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

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

114 KiB could be saved by minifying CSS.

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

119 KiB could be saved by minifying JavaScript.

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

7 third-party services load with your homepage (Google Tag Manager, Google CDN and JSDelivr CDN and others), adding 264 KiB and 196 ms of main-thread time.

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

14 KiB JavaScript is shipped twice across bundles.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SBRAeriallPool-1920x1080”.

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

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

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

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

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

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

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

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

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

3 images (217 KiB) 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 further down the page (114 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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 on the page fails this check, rated moderate by axe-core.

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

Your title is 99 characters, so Google will cut it off around 60: “Luxury 55+ Retirement Communities - Robson Resort Communities - Luxury 55+ Active Adult C…”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 47 pages on robson.com and 24 external pages.

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

https://robson.com/communities/robson-ranch-arizona and https://robson.com/communities/robson-ranch-arizona/home-plans all use the title “Robson Ranch Arizona - Robson Resort Communities - Luxury 55+ Active …”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://robson.com/communities, https://robson.com/home-plans, https://robson.com/lifestyle, https://robson.com/about, https://robson.com/contact and https://robson.com/resources and 9 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://robson.com/communities/robson-ranch-arizona/home-plans, whose canonical is https://robson.com/communities/robson-ranch-arizona. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://robson.com/communities, https://robson.com/lifestyle, https://robson.com/about, https://robson.com/contact, https://robson.com/community-promotions and https://robson.com/communities/pebblecreek and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Your longest form asks for 9 fields (2 required). Every extra field lowers completion.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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

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.

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