tradeshowbooth.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 6.2 s faster on a phone.

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

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

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

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

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

144 KiB could be saved by minifying JavaScript.

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

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

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

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

Shopify costs a phone 266 ms of main-thread work and 638 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.

Facebook costs a phone 179 ms of main-thread work and 297 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.

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

Hubspot costs a phone 133 ms of main-thread work and 315 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 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 27.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your homepage downloads 6.0 MB in 416 requests on a phone: scripts 2.9 MB (99), images 1.7 MB (106) and other files 960 KiB (177). Under 2 MB keeps phones on slow connections fast.

1 image (98 KiB) 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 204.8 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: 2 elements on the page fail this check, rated critical by axe-core.

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

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

Some list items are not inside a list.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

ARIA treeitem nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 10 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.

4 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 (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 70 characters, so Google will cut it off around 60: “Best Trade Show Displays | High Quality Trade Show Booth | Premier Pro”.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 128 pages on tradeshowbooth.com and 12 external pages.

https://tradeshowbooth.com/pages/trade-show-rewards-program-dashboard, https://tradeshowbooth.com/pages/file-upload, https://tradeshowbooth.com/pages/type and https://tradeshowbooth.com/pages/size have no meta description, so Google writes the search snippet from whatever text it finds.

https://tradeshowbooth.com/pages/trade-show-rewards-program-dashboard, https://tradeshowbooth.com/collections/pop-up-portable-trade-show-displays, https://tradeshowbooth.com/collections/quick-zip-up-trade-show-booths, https://tradeshowbooth.com/collections/led-lightbox-tradeshow-displays, https://tradeshowbooth.com/collections/modular-multi-panel-trade-show-displays and https://tradeshowbooth.com/collections/multi-media-tv-trade-show-displays and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://tradeshowbooth.com/collections/pop-up-portable-trade-show-displays, https://tradeshowbooth.com/collections/quick-zip-up-trade-show-booths, https://tradeshowbooth.com/collections/modular-multi-panel-trade-show-displays, https://tradeshowbooth.com/collections/multi-media-tv-trade-show-displays, https://tradeshowbooth.com/collections/merchandising-trade-show-displays-shelving-solutions and https://tradeshowbooth.com/collections/8ft-portable-trade-show-displays-tradeshow-booth-backdrops and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

10 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/Product/286644597/212418783/square.jpg?1649970679.

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

2 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 ()”.

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.

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

The homepage carries about 771 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (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 45 cookies, 10 of them by other companies (measured from a US location before any click).

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