1sthometeam.com website review

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

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

9 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

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

8 third-party services load with your homepage (brivity.com, Google CDN and brivityidx.com and others), adding 6.3 MB and 1.0 s of main-thread time.

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

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

brivityidx.com costs a phone 152 ms of main-thread work and 3.0 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.

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

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

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

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

Google Maps costs a phone 117 ms of main-thread work and 422 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.

JSDelivr CDN costs a phone 80 ms of main-thread work and 498 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.

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

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

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

Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (4.7 s).

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

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

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

The layout shifts by 0.132 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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 7.1 MB in 82 requests on a phone: images 3.4 MB (20), scripts 2.5 MB (26) and other files 599 KiB (16). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.

9 images (2.2 MB) 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 (560 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example promo-slide-5v2.png at 1,324 px wide, shown at 314 px. Resized copies would save about 257 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

1 dropdown has no label.

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

ARIA progressbar nodes must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 30 pages on 1sthometeam.com and 3 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.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

Your homepage links to https://www.1sthometeam.com/search&mlsId=445|234|218|453&multi_search=Belmar,%20NJ&multi_cat=CityState&status=1|3&q_sort=createdAt-&q_offset=0, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.1sthometeam.com/index declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.1sthometeam.com/index all use the title “Century 21 Sylvia Geist Agency | Robert Geist”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.1sthometeam.com/myportal/collections, https://www.1sthometeam.com/myportal/searches, https://www.1sthometeam.com/myportal/reports and https://www.1sthometeam.com/sitemap have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.1sthometeam.com/myportal/collections, https://www.1sthometeam.com/myportal/searches, https://www.1sthometeam.com/myportal/reports, https://www.1sthometeam.com/buying, https://www.1sthometeam.com/selling and https://www.1sthometeam.com/financing and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.1sthometeam.com/tos has 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.

https://www.1sthometeam.com/myportal/searches took over 3 s to send its HTML from our server.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn1.brivityidx.com/idx-sites/1/3/4/13491/site_custom.css?v=1793656015' from origi…”.

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 8 fields (4 required). Every extra field lowers completion.

The homepage has only about 245 words of visible text; thin pages give Google and first-time buyers little to go on.

Before a visitor clicks anything, the page loads Meta Pixel (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 3 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.