waterfireplaces.com website review

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

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

Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (odoo.com, loox.io and Shopify and others), adding 1.5 MB and 723 ms of main-thread time.

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

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

odoo.com costs a phone 508 ms of main-thread work and 986 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.

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

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

loox.io costs a phone 162 ms of main-thread work and 360 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 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

8 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.

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

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

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

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 5.1 MB in 215 requests on a phone: images 2.7 MB (80), scripts 1.3 MB (37) and other files 678 KiB (83). Under 2 MB keeps phones on slow connections fast.

11 images are downloaded at several times the size a phone draws them, for example 11_800x.jpg at 800 px wide, shown at 179 px. Resized copies would save about 579 KiB.

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

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is 87 characters, so Google will cut it off around 60: “Water Vapor Electric Fireplaces - Most Realistic Electric Fireplaces – Water Fireplaces”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 107 pages on waterfireplaces.com and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

The HTML your server sends has 644 of the 1,116 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://waterfireplaces.com/pages/contact, https://waterfireplaces.com/collections/all and https://waterfireplaces.com/collections/20-wide-water-vapor-electric-fireplaces have no meta description, so Google writes the search snippet from whatever text it finds.

https://waterfireplaces.com/pages/about-us and https://waterfireplaces.com/pages/why-buy-from-us use the same meta description. A description written for each page earns more clicks.

https://waterfireplaces.com/blogs/water-vapor-fireplaces-education-blog, https://waterfireplaces.com/collections/all, https://waterfireplaces.com/collections/linear-style-water-vapor-electric-fireplaces, https://waterfireplaces.com/collections/firebox-style-water-vapor-electric-fireplaces, https://waterfireplaces.com/collections/cartridge-cassette-water-electric-firepalces and https://waterfireplaces.com/collections/incased-water-electric-fireplaces and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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