adamdocktor.com website review

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

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

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, GoDaddy and Facebook and others), adding 364 KiB and 262 ms of main-thread time.

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

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

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

6 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Fort Lauderdale Commercial Real Estate Agent Helping South …”.

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

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

The first text or image appears after 2.6 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 3.4 MB in 132 requests on a phone: images 2.3 MB (6), scripts 640 KiB (50) and stylesheets 216 KiB (61). Under 2 MB keeps phones on slow connections fast.

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

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

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

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.

1 visible link has no text or label, so screen readers cannot say where it goes.

The homepage links to 53 pages on adamdocktor.com and 6 external pages.

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

/south-florida-commercial-realtor 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 /south-florida-commercial-realtor all use the title “Fort Lauderdale Commercial Real Estate Broker | Adam Docktor”. Search engines can't tell which page to show for a search, so each competes with the others.

/commercial-real-estate-broker-fort-lauderdale, /warehouse-industrial-broker-fort-lauderdale, /tenant-representation-fort-lauderdale, /office-space-for-lease-fort-lauderdale, /commercial-real-estate-fort-lauderdale and /commercial-real-estate-pompano-beach and 3 others took over 3 s to send their HTML from our server.

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

1 link go through two or more redirects, for example https://facebook.com/adamdocktorRealestate.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

adamdocktor.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

adamdocktor.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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

DMARC is set to p=none, so mail pretending to be adamdocktor.com is still delivered. Reports are on, so moving to quarantine is the next step.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and 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 6 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.