2100realty.com website review

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

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

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

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

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

4 third-party services load with your homepage (Google Fonts, propertypress.com and brivity.com and others), adding 5.0 MB and 0 ms of main-thread time.

brivity.com costs a phone 0 ms of main-thread work and 4.8 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.

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

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (45 KiB).

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.

Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Full Service For Thousands Less FIND A HOME SELL MY HOUSE S…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 6.4 MB in 164 requests on a phone: images 5.5 MB (105), fonts 420 KiB (7) and scripts 371 KiB (22). Under 2 MB keeps phones on slow connections fast.

1 image (78 KiB) 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.

1 image further down the page (78 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There are 3 <h1> headlines (“Full Service For Thousands Less”, “Featured Properties” and “Full Service Realty For Thousands Less”). One clear main headline is easier for people and search engines.

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

The homepage links to 19 pages on 2100realty.com and 3 external pages.

A phone browser shows 4,233 words, but the HTML your server sends has only 193. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://2100realty.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://2100realty.com/about and //about all use the title “About - 2100 Realty seller's choice, inc.”, 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://2100realty.com/areas has no meta description, so Google writes the search snippet from whatever text it finds.

https://2100realty.com/resources, https://2100realty.com/about, https://2100realty.com/contact, //featured-properties, //about and //contact use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example //featured-properties, whose canonical is https://2100realty.com/featured-properties. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://2100realty.com/resources, https://2100realty.com/contact, //featured-properties and //contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://2100realty.com/areas, https://2100realty.com/contact, //featured-properties and //contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 7 pages linked from your homepage 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: net::ERR_TUNNEL_CONNECTION_FAILED”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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 4,233 words of visible text.

Opening the homepage sets 1 cookie (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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.