door3.com website review

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

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

About 212 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and Google CDN and others), adding 2.7 MB and 1.3 s of main-thread time.

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

7 images could be 443 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

hsappstatic.net costs a phone 307 ms of main-thread work and 806 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.

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

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

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

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

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

Desktop scores 83 but mobile only 46. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Real visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 19.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Business transformation through AI automation, data, and ap…”.

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

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

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 147 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 4.4 MB in 128 requests on a phone: scripts 2.5 MB (49), images 1.1 MB (38) and other files 369 KiB (22). Under 2 MB keeps phones on slow connections fast.

5 images (456 KiB) 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.

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

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

The homepage links to 155 pages on door3.com and 5 external pages.

/d3-labs/ai-services and /d3-labs/ai-insurance use the same meta description. A description written for each page earns more clicks.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 of 9 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 “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

Chrome logged issues while loading the page (“Cookie”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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 1,026 words of visible text.

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

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 Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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