firepitsdirect.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and SearchSpring and others), adding 1.2 MB and 375 ms of main-thread time.

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

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

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

Klaviyo costs a phone 130 ms of main-thread work and 312 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.

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

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

43 KiB JavaScript is shipped twice across bundles.

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

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.

4 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

Your homepage downloads 18.6 MB in 473 requests on a phone: media 14.3 MB (3), scripts 1.6 MB (136) and other files 1.4 MB (273). Under 2 MB keeps phones on slow connections fast.

3 images (266 KiB) are 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 5.28 g of CO₂e: 633.8 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.

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

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

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

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

The homepage links to 207 pages on firepitsdirect.com and 7 external pages.

https://firepitsdirect.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://firepitsdirect.com/policies/shipping-policy, https://firepitsdirect.com/collections/outdoor-fire-features, https://firepitsdirect.com/collections/gas-fire-pits, https://firepitsdirect.com/collections/gas-fire-tables, https://firepitsdirect.com/collections/gas-fire-bowls and https://firepitsdirect.com/collections/fire-water-features and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Klaviyo, Meta Pixel and Microsoft Ads and 1 more (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 24 cookies (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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.