richmondamerican.com website review

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

About 891 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, osano.com and Facebook and others), adding 1.7 MB and 2.1 s of main-thread time.

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

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

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

osano.com costs a phone 281 ms of main-thread work and 83 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.

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

Google CDN costs a phone 160 ms of main-thread work and 348 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.

18 KiB could be saved by minifying CSS.

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

8 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

Visually, the page fills in at 6.0 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-24, real Chrome visitors' tap response (inp) went from 136 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

hero_video_fallback.jpg weighs 1.1 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example hero_video_fallback.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 541 KiB.

Your homepage downloads 3.6 MB in 136 requests on a phone: scripts 2.1 MB (52), images 1.2 MB (18) and HTML 87 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image (1.1 MB) is 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.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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.

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

1 tap target is too small or too close together to hit reliably with a finger.

Your title is only 17 characters: “Richmond American”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“Come homefor the holidays!” and “Find your place.”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 37 pages on richmondamerican.com and 11 external pages.

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.

There is no https://www.richmondamerican.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://www.richmondamerican.com/home-design, https://www.richmondamerican.com/home-design/floor-plan-design, https://www.richmondamerican.com/home-design/design-studio, https://www.richmondamerican.com/home-design/quality-homes, https://www.richmondamerican.com/home-design/energy-efficient-homes and https://www.richmondamerican.com/home-design/new-construction-homes and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.richmondamerican.com/home-design, whose canonical is https://www.richmondamerican.com/why-richmond. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.richmondamerican.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “clickdimensions is not defined”.

Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

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

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