mdfinstruments.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Convert Insights and Attentive and others), adding 2.4 MB and 1.2 s of main-thread time.

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

Shopify costs a phone 448 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.

10 images could be 373 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

Attentive costs a phone 143 ms of main-thread work and 442 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.

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

10 long tasks block the main thread while loading, the longest for 218 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 22 KiB JavaScript that modern phones do not need.

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.

Your largest element takes 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Stethoscope Sale MDF Instruments Save Up to $80 on ProCardi…”.

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

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

Real visitors wait 3.2 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-31, real Chrome visitors' tap response (inp) went from 142 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 5.0 MB in 392 requests on a phone: scripts 2.0 MB (147), images 1.5 MB (24) and other files 1,022 KiB (182). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

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

Your title is 68 characters, so Google will cut it off around 60: “MDF Instruments - Stethoscopes, Sphygmomanometers and Reflex Hammers”.

The homepage links to 402 pages on mdfinstruments.com and 7 external pages.

https://mdfinstruments.com/collections/silver-stethoscopes has no meta description, so Google writes the search snippet from whatever text it finds.

https://mdfinstruments.com/collections/deals has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0434/5292/4069/files/stethoscope-sale-up-to-_80-off-cardiology-stethoscopes-mdf-instruments-procardial-desktop_5a2cd2ea-39cd-4ff2-b948-835715bd8a83.jpg?v=1793652601.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) SecurityError: Failed to read a named property 'document' from 'Window': Sandbox access violation…”.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 1,182 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 4 mores (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 38 cookies, 2 of them by other companies (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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.