anbl.com website review

Not measured in this review.

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

  +12%

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

• Largest content (LCP) held steady for real visitors

  +1%

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

• Page weight: 10.4 MB

  10.4 MB

  Your homepage downloads 10.4 MB on a phone, 8.1 MB of it images (78%). Under 2 MB keeps phones on slow connections fast.

• 5 images over 500 KB

  5 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.

  Elements (5)

• 7 images far larger than shown

  3.6 MB

  7 images are downloaded at several times the size a phone draws them, for example signup-footer_en.png at 2,258 px wide, shown at 296 px. Resized copies would save about 3.6 MB.

  Elements (5)

• 16 images in older formats

  16 images (6.2 MB) 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 (5)

• 6 images below the first screen load straight away

  6 images further down the page (2.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• About 2.9 g of CO₂ per visit

  2.94 g

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

• 1 button without a name

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

  Elements (1)

• 2 text elements with low contrast

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

  Elements (2)

• Malformed lists

  Some lists contain elements other than list items, which screen readers announce wrongly.

  Elements (2)

• 6 images without alt text

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

  View sourceElements (3)

• Page should contain a level-one heading (1 element)

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

  Elements (1)

• 11 links without text

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

  Elements (3)

• 2 form fields without a label

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

  View source

• robots.txt blocks all crawlers

  Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

• No H1 headline

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

• Title is short (4 characters)

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

  View source

• No structured data

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

• Meta description is short (8 characters)

  Your meta description is only 8 characters: “Homepage”. 70 to 160 characters is enough to sell the click.

  View source

• No canonical URL

  No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

• No social preview image

  No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

• No XML sitemap

  No XML sitemap at https://www.anbl.com/sitemap.xml, so Google discovers your pages only by following links.

• No X (Twitter) card tag

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

• 191 internal links, 10 external

  The homepage links to 191 pages on anbl.com and 10 external pages.

• robots.txt blocks 6 AI answer engine crawlers

  6 of 6

  Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

• No Organization structured data

  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.

• No llms.txt

  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.

• Opted out of AI training for 5 crawlers

  robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

• 2 pages share a title

  / and /fr all use the title “ANBL”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (2)

• 12 pages without a meta description

  /stores, /flyer, /hot-deals, /discover, /new and /gifts and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 5 pages without an H1

  /flyer, /fr, /hot-deals, /discover and /depot have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 17 small tap targets

  17 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://anbl-2.azureedge.net/content/cssinclude.bdl?id=243' from origin 'https://www.anbl.…”.

• No X-Content-Type-Options

  X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

• 2 links through redirect chains

  2 links go through two or more redirects, for example https://www.anbl.com/japanese-lagers.

• No Referrer-Policy

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

• No Permissions-Policy

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

• No security.txt

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

• No CAA record

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

• DNSSEC is off

  anbl.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 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 direct contact details

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

• Only about 158 words

  The homepage has only about 158 words of visible text; thin pages give Google and first-time buyers little to go on.

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

• Email authentication score: 90/100

  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.

• 8 trackers load before any consent

  8

  Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 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.

• 12 cookies set on arrival

  12

  Opening the homepage sets 12 cookies (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.

• 31 other companies contacted

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