masterpieceintl.com website review

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

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

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

9 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 190 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.

7 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Cloudflare and others), adding 1.0 MB and 280 ms of main-thread time.

Google CDN costs a phone 240 ms of main-thread work and 736 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 2.2 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

5 long tasks block the main thread while loading, the longest for 80 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).

11 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To provide the best experiences, we use technologies like c…”.

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

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

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

3 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 6.7 MB in 123 requests on a phone: images 4.4 MB (34), scripts 1.2 MB (38) and other files 411 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

7 images (461 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.91 g of CO₂e: 228.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 7 elements on the page fail this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

Elements must only use permitted ARIA attributes: 81 elements on the page fail this check, rated serious by axe-core.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

81 links have no real href, so search engines can't follow them.

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

21 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://masterpieceintl.com/wp-sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 88 pages on masterpieceintl.com and 20 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://masterpieceintl.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.

Your homepage links to https://masterpieceintl.com/news, https://masterpieceintl.com/request-a-consultation, https://masterpieceintl.com/fine-art/turtle-crates, https://masterpieceintl.com/fine-art/art-fairs and https://masterpieceintl.com/latest-news/press-release/magnate-worldwide-becomes-imperative-logistics-group, which answer with an error. Visitors hit a dead end and search engines drop them.

https://masterpieceintl.com/contact-us, https://masterpieceintl.com/location, https://masterpieceintl.com/technology-suite, https://masterpieceintl.com/atlas-by-masterpiece, https://masterpieceintl.com/artwise and https://masterpieceintl.com/fine-art/museums and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://masterpieceintl.com/location, https://masterpieceintl.com/atlas-by-masterpiece and https://masterpieceintl.com/artwise have no <h1> headline, so visitors and search engines get no clear main topic.

https://masterpieceintl.com/contact-us, https://masterpieceintl.com/location, https://masterpieceintl.com/technology-suite, https://masterpieceintl.com/atlas-by-masterpiece, https://masterpieceintl.com/artwise and https://masterpieceintl.com/fine-art/museums and 4 others took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://masterpieceintl.com/.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 780 words of visible text.

Opening the homepage sets 2 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.