mosaicmfg.com website review

20 images could be 11.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

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

About 390 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and FontAwesome CDN and others), adding 1.3 MB and 899 ms of main-thread time.

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.

Google Tag Manager costs a phone 441 ms of main-thread work and 639 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 3.9 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

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

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 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Designing for Belt-Based 3D Printing: Guidelines and Best P…”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 103 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 16.8 MB in 122 requests on a phone: images 14.9 MB (64), scripts 1.5 MB (29) and fonts 189 KiB (4). Under 2 MB keeps phones on slow connections fast.

5 images weigh 10.8 MB together. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example Parts-on-Bed-1.jpg at 5,416 px wide, shown at 350 px. Resized copies would save about 9.7 MB.

31 images (14.7 MB) 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.

Copy-of-orion-17.png 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).

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

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

4 links inside paragraphs rely on colour alone to stand out.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Your meta description is only 49 characters: “Mosaic is expand your 3d printing horizons etc...”. 70 to 160 characters is enough to sell the click.

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

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

The homepage links to 162 pages on mosaicmfg.com and 9 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://mosaicmfg.com/use-cases-applications-orthotics, https://mosaicmfg.com/3d-printed-foam, https://mosaicmfg.com/use-cases-applications-spare-parts, https://mosaicmfg.com/jigs-fixtures, https://mosaicmfg.com/tooling and https://mosaicmfg.com/robotics and 9 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://mosaicmfg.com/use-cases-applications-orthotics, whose canonical is https://mosaicmfg.com/use-cases/applications/orthotics. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mosaicmfg.com/contract-manufacturing and https://mosaicmfg.com/education took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

There is no form on the homepage, so every lead has to click through to another page first.

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 1,325 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (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 10 cookies (measured from a US location before any click).

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