prodiadental.com website review

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

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

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

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

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

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

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

Google Tag Manager costs a phone 518 ms of main-thread work and 534 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 428 ms of main-thread work and 1.1 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 images could be 386 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.

zbcdn.net costs a phone 293 ms of main-thread work and 260 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.

Shopify costs a phone 206 ms of main-thread work and 1.0 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.

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

zotabox.com costs a phone 175 ms of main-thread work and 550 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.

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

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

19 KiB could be saved by minifying JavaScript.

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

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.

3 KiB could be saved by minifying CSS.

2 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

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

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

Your homepage downloads 7.0 MB in 436 requests on a phone: scripts 3.8 MB (153), other files 1.2 MB (163) and images 1.2 MB (75). Under 2 MB keeps phones on slow connections fast.

Banner-1-1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

10 images further down the page (442 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example packs2.jpg at 1,381 px wide, shown at 366 px. Resized copies would save about 82 KiB.

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

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

39 images have no alt text, which hurts accessibility and image search.

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

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

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

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

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

Your title is 70 characters, so Google will cut it off around 60: “Prodia Dental | Premium Diamond Instruments Direct from the Manufactur”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 82 pages on prodiadental.com and 15 external pages.

https://prodiadental.com/collections/z-series-polishers, https://prodiadental.com/collections/procedure-systems and https://prodiadental.com/pages/trade-shows have no meta description, so Google writes the search snippet from whatever text it finds.

https://prodiadental.com/pages/trade-shows has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.

8 images are served at too low a resolution for sharp phone screens.

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 885 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 1 more (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 18 cookies, 1 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.