mastergraphics.com website review

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

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

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

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 2.3 MB and 1.1 s of main-thread time.

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

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

YouTube costs a phone 496 ms of main-thread work and 978 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 Tag Manager costs a phone 254 ms of main-thread work and 325 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.

Vimeo costs a phone 53 ms of main-thread work and 551 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.

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

Polyfills for old browsers add 47 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.

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

Your largest element takes 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WELCOME TO M5D, FORMERLY MASTERGRAPHICS & CIMQUEST We are e…”.

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

The layout shifts by 0.24 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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 4.3 MB in 168 requests on a phone: scripts 2.4 MB (48), images 1.0 MB (43) and fonts 441 KiB (8). Under 2 MB keeps phones on slow connections fast.

[email protected] 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).

4 images (209 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.

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

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

8 elements hidden from screen readers can still receive keyboard focus.

1 tap target is too small or too close together to hit reliably with a finger.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 8 characters: “M5D Home”. 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 6 <h1> headlines (“Fuse X1”, “” and “HEY!Are you”). One clear main headline is easier for people and search engines.

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 92 pages on mastergraphics.com and 28 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 /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.

/formlabs-3d-printers, /formlabs-form-4l and /formlabs-fuse-1-30w use the same meta description. A description written for each page earns more clicks.

/hp-mjf-1200, /hp-if600ht-3d-printer and /formlabs-fuse-x1 have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

8 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

Large scripts ship without source maps.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://mastergraphicsinc.sharepoint.com/intranet/Pages/default.aspx.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

m5d.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

m5d.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 12 customer or partner logos. 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 523 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 14 cookies, 3 of them by other companies (measured from a US location before any click).

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