nomadicdisplay.com website review

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

LinkedIn Ads costs a phone 3.6 s of main-thread work and 3.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

protechts.net costs a phone 2.9 s of main-thread work and 421 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 28.0 s on main-thread work while loading, 15.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google CDN costs a phone 2.1 s of main-thread work and 2.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (LinkedIn Ads, protechts.net and Google CDN and others), adding 10.7 MB and 10.0 s of main-thread time.

About 3.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

px-cloud.net costs a phone 769 ms of main-thread work and 754 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.

Other Google APIs/SDKs costs a phone 322 ms of main-thread work and 123 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.

36 KiB could be saved by minifying JavaScript.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

Desktop scores 54 but mobile only 28. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 53.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

38 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 30.0 MB in 439 requests on a phone: images 12.2 MB (105), media 7.4 MB (1) and scripts 7.0 MB (118). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example AvernaPhoto2.jpg at 1,500 px wide, shown at 350 px. Resized copies would save about 165 KiB.

2 images further down the page (283 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 8.50 g of CO₂e: 1019.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

1 link inside paragraphs relies on colour alone to stand out.

1 image has no alt text, which hurts accessibility and image search.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails 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.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

Your title is 70 characters, so Google will cut it off around 60: “Nomadic Display the leader in modular and portable trade show displays”.

Your meta description is 254 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 201 pages on nomadicdisplay.com and 7 external pages.

The HTML your server sends has 1,052 of the 3,009 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://www.nomadicdisplay.com/pages/nomadic-projects has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nomadicdisplay.com/pages/contact-us, https://www.nomadicdisplay.com/pages/design-quote, https://www.nomadicdisplay.com/blogs/nomadictradeshowblog, https://www.nomadicdisplay.com/collections/instand-pop-up-designs, https://www.nomadicdisplay.com/collections/fablite-tension-fabric-displays and https://www.nomadicdisplay.com/collections/lightwall-backlit-displays and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 3,009 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 10 cookies, 3 of them by other companies (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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.