seqoutdoor.com website review

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

About 751 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 820 ms faster on a phone.

6 third-party services load with your homepage (zohocdn.com, Google Tag Manager and Usercentrics CMP and others), adding 1.8 MB and 1.1 s of main-thread time.

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

6 images could be 251 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

zohocdn.com costs a phone 441 ms of main-thread work and 1.1 MB 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.

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

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

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

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

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

7 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 5.5 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 5.1 s (Speed Index). Good is under 3.4 s.

2 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' largest content (lcp) went from 1.0 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 3.1 MB in 248 requests on a phone: scripts 1.5 MB (88), other files 731 KiB (89) and images 382 KiB (14). Under 2 MB keeps phones on slow connections fast.

SR-TBLHEX01-CWH_HPA.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).

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

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

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

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.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 15 characters: “Sequoia Outdoor”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Your <h1> is empty.

The homepage links to 64 pages on seqoutdoor.com and 7 external pages.

https://seqoutdoor.com/collections/benches, https://seqoutdoor.com/collections/swings, https://seqoutdoor.com/collections/hdps-products and https://seqoutdoor.com/collections/hdpe-products took over 3 s to send their HTML from our server.

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

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

Requests the geolocation permission on page load.

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

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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