safecourtkitchen.com website review

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

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

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

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

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

7 third-party services load with your homepage (shgcdn3.com, Shopify and Klaviyo and others), adding 100 KiB and 60 ms of main-thread time.

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 images have no width and height attributes, so the layout jumps as each one loads.

ea-kerst-hero-cadeaudoos-mobiel.webp 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).

3 images (294 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 0.47 g of CO₂e: 56.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is only 17 characters: “Safecourt Kitchen”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 285 pages on safecourtkitchen.com and 90 external pages.

Your Organization JSON-LD is missing 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.

/collections/bestsellers-kopie, /pages/onze-materialen, /pages/onze-standaard, /pages/verkooppunten, /pages/contact and /collections/bundel and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/over-ons, /pages/onze-materialen, /pages/contact, /collections/koffie-thee, /collections/keukenapparaten and /collections/potten-pannen have no <h1> headline, so visitors and search engines get no clear main topic.

/products/melkopschuimer-glazen-kan-zwart, /collections/keukenapparaten and /collections/potten-pannen took over 3 s to send their HTML from our server.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://safecourtkitchen.com/account.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

safecourtkitchen.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

safecourtkitchen.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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