gall.nl website review

Your mobile performance score is 63 (desktop: 68). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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

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

About 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

3 third-party services load with your homepage (Salesforce Commerce Cloud, Google Tag Manager and Google/Doubleclick Ads), adding 23 KiB and 72 ms of main-thread time.

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

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

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Podium pakkers! Meer dan 400 wijnen bekroond door de grote …”.

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

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Week43-44_HomeLarge1_Mobiel_PP_v1.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).

By the Sustainable Web Design model, a visit to your homepage emits about 0.45 g of CO₂e: 54.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: 7 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: 3 elements on the page fail this check, rated moderate by axe-core.

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

47 visible links have no text or label, so screen readers cannot say where they go.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 508 pages on gall.nl and 9 external pages.

There is no /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.

/nieuwe-producten/wijn is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

1 error was logged to the browser console while the page loaded, for example “ReferenceError: _etmc is not defined”.

Large scripts ship without source maps.

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

Your security.txt expired on 2025-05-31, so researchers may not trust its contact details.

gall.nl 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.

gall.nl'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.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

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

The homepage shows no opening hours. If customers visit or call, show when.

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 390 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 Google Ads and Google Tag Manager (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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.