worldwidefloors.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and boostcommerce.io and others), adding 1.2 MB and 594 ms of main-thread time.

About 125 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 313 ms of main-thread work and 508 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 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “35 Years - Anniversary Celebration, Now Thru November 29”.

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

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

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

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

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

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

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

Your homepage downloads 8.6 MB in 185 requests on a phone: media 4.3 MB (1), images 2.1 MB (30) and scripts 1.3 MB (59). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is 103 characters, so Google will cut it off around 60: “WORLDWIDE FLOORING DESIGN CENTER - QUALITY FLOORING AND INSTALLATION – Worldwide Flooring…”.

There are 2 <h1> headlines (“Everything Home” and “Inspiration”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization, Store and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.worldwidefloors.com/cdn/shop/files/thumbnail_imag…”.

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

The homepage links to 132 pages on worldwidefloors.com and 19 external pages.

https://www.worldwidefloors.com/collections/vendors declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.worldwidefloors.com/collections/vendors all use the title “WORLDWIDE FLOORING DESIGN CENTER - QUALITY FLOORING AND INSTALLATION …”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.worldwidefloors.com/collections/soft-surface-1, https://www.worldwidefloors.com/pages/the-rug-corner, https://www.worldwidefloors.com/collections/stair-runners, https://www.worldwidefloors.com/collections/hardwood-floors, https://www.worldwidefloors.com/collections/hybrid-water-proof and https://www.worldwidefloors.com/collections/cabinets and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.worldwidefloors.com/collections/soft-surface-1, https://www.worldwidefloors.com/pages/the-rug-corner, https://www.worldwidefloors.com/collections/stair-runners, https://www.worldwidefloors.com/collections/hardwood-floors, https://www.worldwidefloors.com/collections/hybrid-water-proof and https://www.worldwidefloors.com/collections/cabinets and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.worldwidefloors.com/collections/hybrid-water-proof has 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 58 found) and read each the way a search engine does.

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: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel and Xandr (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 16 cookies, 12 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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.