outdoorrooms.com website review

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

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

10 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, LiveChat and Klaviyo and others), adding 1.8 MB and 1.3 s of main-thread time.

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

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

LiveChat costs a phone 229 ms of main-thread work and 364 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 2,034 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

14 KiB could be saved by minifying JavaScript.

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

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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 15.7 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 21.0 s. Good is under 3.8 s.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 117 ms to 128 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 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.0 MB in 387 requests on a phone: images 4.8 MB (44), scripts 1.9 MB (137) and other files 982 KiB (171). Under 2 MB keeps phones on slow connections fast.

CIR-42-FSBR-K_Flame_WEB.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Document should not have more than one banner 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.

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

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

Your title is 86 characters, so Google will cut it off around 60: “One Stop for Outdoor Fire Pits & Fireplaces: Outdoor GreatRoom Co – Outdoor GreatRooms”.

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

The homepage links to 186 pages on outdoorrooms.com and 10 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://outdoorrooms.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

https://outdoorrooms.com/pages/company-and-shipping-updates has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343023570&tm=gtm002&Ver=2&mid=547fea96-e57a-4949-b295-56045671f3dc&bo=1&sid=b83ce6c0dd3011f190e139ee360305a6&vid=b83cf920dd3011f1b8651523c0843804&vids=1&msclkid=N&pi=9.

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

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

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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