madewithdiamonds.com website review

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

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

8 third-party services load with your homepage (negate.io, TikTok and Google Tag Manager and others), adding 1.0 MB and 1.2 s of main-thread time.

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

About 657 KiB of JavaScript is downloaded but never used on this page.

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

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

negate.io costs a phone 321 ms of main-thread work and 40 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 2,047 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

About 46 KiB of CSS is downloaded but never applied on this page.

17 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

3 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' tap response (inp) went from 137 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.1 MB in 266 requests on a phone: images 3.1 MB (46), scripts 1.8 MB (81) and other files 1,019 KiB (129). Under 2 MB keeps phones on slow connections fast.

21 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

20 images are downloaded at several times the size a phone draws them, for example Buyer_show_08.jpg at 500 px wide, shown at 150 px. Resized copies would save about 286 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

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

Alternative text of images should not be repeated as text: 16 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 181 pages on madewithdiamonds.com and 14 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.

https://madewithdiamonds.com/apps/parcelpanel has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56382844&Ver=2&mid=57007088-d738-43f9-8f7a-bded7e98618a&bo=1&sid=274098e0dcc111f183e57912198ffd9a&vid=27407500dcc111f19962057110c7d838&vids=1&msclkid=N&pi=918639831&lg.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

3 errors were logged to the browser console while the page loaded, for example “Elevar Data Layer: Config element not found”.

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

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

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