wsdisplay.com website review

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 3.5 s.

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

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

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

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

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

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

2 third-party services load with your homepage (Google Tag Manager and Cookiebot), adding 351 KiB and 449 ms of main-thread time.

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

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need.

3 images could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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.

For real visitors the layout shifts by 0.51 (75th percentile). Good is under 0.1.

Your largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

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

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

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

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

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

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

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

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

Your homepage downloads 2.3 MB in 47 requests on a phone: scripts 1.1 MB (12), images 450 KiB (16) and fonts 421 KiB (5). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 78.4 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”.

238 images have no alt text, which hurts accessibility and image search.

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

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

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

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

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

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

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 423 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.

No XML sitemap at https://www.wsdisplay.com/sitemap.xml, so Google discovers your pages only by following links.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 371 pages on wsdisplay.com and 6 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 https://www.wsdisplay.com/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.

https://www.wsdisplay.com/One-Choice-Products/one-choice-canopy-tents/one-choice-canopy-backwall-sidewall, https://www.wsdisplay.com/ONE-CHOICE-Roll-Up-Banner-Stand, https://www.wsdisplay.com/ONE-CHOICE-Clear-Retractable-Banners, https://www.wsdisplay.com/OneChoice-Xstand-FivePack-Graphic-Package, https://www.wsdisplay.com/One-Choice-Products/one-choice-indoor-banner and https://www.wsdisplay.com/ONE-CHOICE-8-x-3-ft.-Custom-Banner and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wsdisplay.com/One-Choice-Products/one-choice-canopy-tents/width-feet/5, https://www.wsdisplay.com/One-Choice-Products/one-choice-canopy-tents/width-feet/10, https://www.wsdisplay.com/One-Choice-Products/one-choice-canopy-tents/width-feet/15 and https://www.wsdisplay.com/One-Choice-Products/one-choice-canopy-tents/width-feet/20 use the same meta description. A description written for each page earns more clicks.

https://www.wsdisplay.com/custitem_item_brand/One-Choice-Displays has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.wsdisplay.com/custitem_item_brand/One-Choice-Displays took over 3 s to send its HTML from our server.

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

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

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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 414 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 7 cookies (measured from a US location before any click).

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