flamesa.nl website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user INP: 246 ms

  246 ms

  Real visitors wait 246 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

• Tap response (INP) got 66% slower for real visitors

  +66%

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

• Page weight: 5.1 MB

  5.1 MB

  Your homepage downloads 5.1 MB on a phone, 937 KiB of it images (18%). Under 2 MB keeps phones on slow connections fast.

• 1 image far larger than shown

  55 KiB

  1 image is downloaded at several times the size a phone draws it, for example flamesa-flare-verrijdbare-pelletkachel-buiten-vuur.webp at 1,646 px wide, shown at 77 px. Resized copies would save about 55 KiB.

  Elements (1)

• 2 images in older formats

  2 images (163 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.

  Elements (2)

• 1 image below the first screen load straight away

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

  Elements (1)

• About 1.4 g of CO₂ per visit

  1.43 g

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

• 92 text elements with low contrast

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

  Elements (3)

• All page content should be contained by landmarks (7 elements)

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

  Elements (3)

• 55 form fields without a label

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

  View source

• Title is long (71 characters)

  Your title is 71 characters, so Google will cut it off around 60: “Pelletkachel voor Buiten | Luxe Terrasverwarming | Flamesa – Flamesa.nl”.

  View source

• 177 internal links, 29 external

  The homepage links to 177 pages on flamesa.nl and 29 external pages.

• 1 page without a title

  https://flamesa.nl/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  Elements (1)

• 1 linked page hidden from search

  https://flamesa.nl/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 1 page without a meta description

  https://flamesa.nl/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 2 pages without an H1

  https://flamesa.nl/collections/flamesa-pelletkachel-bundels and https://flamesa.nl/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

• 1 page slow to respond

  https://flamesa.nl/customer_authentication/redirect took over 3 s to send its HTML from our server.

• 15 internal pages checked

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

• 1 broken image

  1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97224105&Ver=2&mid=d98456a3-b2f5-4535-9913-fcfd655adc74&bo=3&sid=172dcb80df1811f1acacb7c90a496c19&vid=172e30f0df1811f19183c96482967e6d&vids=0&msclkid=N&pi=918639831&lg.

• 5 JavaScript errors while loading

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

• No call to action on the first screen

  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 phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• No analytics detected

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

• No direct contact details

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

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• No risk reducer

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

• About 2,425 words of copy

  The homepage carries about 2,425 words of visible text.

• 9 trackers load before any consent

  9

  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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

• 33 cookies set on arrival

  33

  Opening the homepage sets 33 cookies, 2 of them by other companies (measured from a US location before any click).

• No consent tool detected

  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.

• 53 other companies contacted

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