mmidoor.com website review

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

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

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

2 third-party services load with your homepage (Cookiebot and Amazon Web Services), adding 27.8 MB and 152 ms of main-thread time.

Amazon Web Services costs a phone 0 ms of main-thread work and 27.6 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 159 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 63 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

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

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

24 KiB could be saved by minifying CSS.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

14 KiB could be saved by minifying JavaScript.

Desktop scores 94 but mobile only 63. 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.

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

4 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 28.7 MB in 183 requests on a phone: images 27.8 MB (148), scripts 478 KiB (20) and stylesheets 187 KiB (11). Under 2 MB keeps phones on slow connections fast.

10 images weigh 9.2 MB together. On a phone connection a single image that size takes seconds.

40 images (20.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.

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

1 dropdown has no label.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

3 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 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 8 characters: “MMI DOOR”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“” and “Test Drive Your Dream Door”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 215 characters; Google truncates after about 160, so the end of your pitch is cut.

There is no robots.txt at mmidoor.com/robots.txt, the first file search crawlers ask for.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 102 pages on mmidoor.com and 2 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.

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

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

10 of 44 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 “Connecting to 'https://consentcdn.cookiebot.com/consentconfig/896d43df-7e51-4516-a46a-611d33b65bfe/settings.json' viola…”.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Content security policy”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

The homepage carries about 346 words of visible text.

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

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