1azsold.com website review

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

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.

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

4 images could be 752 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

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

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

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

Google CDN costs a phone 587 ms of main-thread work and 1.5 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 308 ms of main-thread work and 1.3 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.

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

brivityidx.com costs a phone 214 ms of main-thread work and 1.2 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 Maps costs a phone 127 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 98 ms of main-thread work and 514 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.

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

7 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 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

3 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 6.4 MB in 98 requests on a phone: scripts 3.2 MB (35), images 1.4 MB (15) and other files 1,019 KiB (21). Under 2 MB keeps phones on slow connections fast.

0.jpg weighs 1.4 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 0.jpg at 3,000 px wide, shown at 330 px. Resized copies would save about 1.2 MB.

4 images (1.8 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.

1 image further down the page (194 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.82 g of CO₂e: 218.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

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

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

ARIA progressbar nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 47 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.

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

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

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

There are 11 <h1> headlines (“Let's Find Home.”, “"I would absolutely trust him for any and all rea…” and “"Mike gets a grade of 100 from us. I would highly…”). One clear main headline is easier for people and search engines.

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 set, so this is minor.

The homepage links to 40 pages on 1azsold.com and 8 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.

https://www.1azsold.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.1azsold.com/index all use the title “Mike Tart, Realtor | Precision Real Estate, Inc.”. Search engines can't tell which page to show for a search, so each competes with the others.

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

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

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

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/5/5/15529/site_custom.css?v=1793653670' from origi…”.

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.

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

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 298 words of visible text.

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.