motifworks.com website review

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Hubspot and hubspotusercontent-na1.net and others), adding 1.0 MB and 692 ms of main-thread time.

Google Tag Manager costs a phone 336 ms of main-thread work and 487 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.

Hubspot costs a phone 333 ms of main-thread work and 513 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.

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

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

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

8 KiB could be saved by minifying CSS.

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 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

ISO 27001 & 27701.png weighs 2.0 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example ISO 27001 & 27701.png at 15,000 px wide, shown at 65 px. Resized copies would save about 2.0 MB.

Your homepage downloads 3.5 MB in 59 requests on a phone: images 2.1 MB (18), scripts 1.2 MB (21) and HTML 91 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image (2.0 MB) is 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 (2.0 MB) 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 0.99 g of CO₂e: 118.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

[role]s do not have all required [aria-*] attributes (7 elements).

Elements with visible text labels do not have matching accessible names. (4 elements).

The robots meta tag says “noindex, follow”: Google is told not to list this page at all.

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.

Your title is only 11 characters: “We're Moved”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 366 pages on motifworks.com and 29 external pages.

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

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 199 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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