lumacast.com website review

13 images could be 656 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 1.9 MB and 1.1 s of main-thread time.

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

About 547 KiB of JavaScript is downloaded but never used on this page.

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

Shopify costs a phone 272 ms of main-thread work and 1.0 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 block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

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

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

78 KiB JavaScript is shipped twice across bundles.

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

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

Polyfills for old browsers add 14 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.

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

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LUMACAST FIRE”.

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

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

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

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

Your homepage downloads 4.4 MB in 409 requests on a phone: scripts 1.7 MB (165), images 1.4 MB (47) and other files 868 KiB (144). Under 2 MB keeps phones on slow connections fast.

poster-strip-fire.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 is downloaded at several times the size a phone draws it, for example precast-ivory.jpg at 1,100 px wide, shown at 342 px. Resized copies would save about 22 KiB.

1 image further down the page (168 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

All page content should be contained by landmarks: 11 elements on the page fail 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.

Your title is 68 characters, so Google will cut it off around 60: “Lumacast | Modern Concrete Fire Features for Inspired Outdoor Living”.

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

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

The homepage links to 247 pages on lumacast.com and 18 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

There is no https://lumacast.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://lumacast.com/pages/2026-trade-program has no meta description, so Google writes the search snippet from whatever text it finds.

https://lumacast.com/collections/fire-features and https://lumacast.com/collections/made-to-order have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,110 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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