Website review, no card needed

billa.at logo

billa.at website review

Visit site (opens in a new tab)Reviewed 26 October 202638 issues · 85 checks

This review found 38 issues worth fixing on billa.at, 11 of them high impact, across 85 checks. The most urgent: mobile performance score: 30. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s2.1 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
137 ms118 msMay 9Oct 24135 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026120 ms
May 16, 2026120 ms
May 23, 2026121 ms
May 30, 2026121 ms
Jun 6, 2026121 ms
Jun 13, 2026122 ms
Jun 20, 2026122 ms
Jun 27, 2026123 ms
Jul 4, 2026124 ms
Jul 11, 2026125 ms
Jul 18, 2026125 ms
Jul 25, 2026125 ms
Aug 1, 2026126 ms
Aug 8, 2026128 ms
Aug 15, 2026129 ms
Aug 22, 2026130 ms
Aug 29, 2026131 ms
Sep 5, 2026131 ms
Sep 12, 2026132 ms
Sep 19, 2026130 ms
Sep 26, 2026124 ms
Oct 3, 2026121 ms
Oct 10, 2026122 ms
Oct 17, 2026126 ms
Oct 24, 2026135 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of billa.at (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. billa.at at 0.6 s0.6 s
  2. billa.at at 1.1 s1.1 s
  3. billa.at at 1.7 s1.7 s
  4. billa.at at 2.2 s2.2 s
  5. billa.at at 2.8 s2.8 s
  6. billa.at at 3.3 s3.3 s
  7. billa.at at 3.9 s3.9 s
  8. billa.at at 4.5 s4.5 s

Speed

11 to fix30
  • Mobile performance score: 30

    30/100

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

  • Document request latency

    750 ms · 808 KiB

    The HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    773 ms

    Reduce initial server response time. Google estimates savings of 773 ms on a phone.

  • Improve image delivery

    746 KiB

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

  • Render-blocking requests

    650 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Usercentrics CMP and Adobe Tag Manager and others), adding 1.7 MB and 366 ms of main-thread time.

  • Reduce unused JavaScript

    310 ms · 227 KiB

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

  • Main-thread work: 3.9 s

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

  • Font display

    350 ms

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

  • kc-usercontent.com adds 0 ms

    0 ms

    kc-usercontent.com costs a phone 0 ms of main-thread work and 1.3 MB 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.

  • Server response: 873 ms

    873 ms

    Your server takes 873 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Reduce unused CSS

    190 ms · 111 KiB

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

  • Use efficient cache lifetimes

    233 KiB

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    50 KiB

    50 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 74 but mobile only 30. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 0.78

    0.78

    For real visitors the layout shifts by 0.78 (75th percentile). Good is under 0.1.

  • First Contentful Paint: 8.9 s

    8.9 s

    The first text or image appears after 8.9 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 9.8 s

    9.8 s

    Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 15.0 s

    15.0 s

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

  • Speed Index: 8.9 s

    8.9 s

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

  • Cumulative Layout Shift: 0.266

    0.266

    The layout shifts by 0.266 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 525 ms

    525 ms

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

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

4 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 151 ms

    151 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 449 ms

    449 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 276 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 276 requests on a phone: images 1.2 MB (31), HTML 1.2 MB (2) and scripts 829 KiB (175). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (122 KiB) is 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.

  • About 1.0 g of CO₂ per visit

    0.98 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9796
  • Scrollable region must have keyboard access (1 element)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h5, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9282
  • Title is short (16 characters)

    Your title is only 16 characters: “BILLA.at | BILLA”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (162 characters)

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

  • Structured data has 1 problem

    Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected end of JSON input)”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 26 internal links, 32 external

    The homepage links to 26 pages on billa.at and 32 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Produkte zum IMMER CLEVER PREIS*”.

  • Canonical URL set

    The canonical URL is https://www.billa.at/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.billa.at/sitemap.xml.

AI search readiness

1 to fix88
  • 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 https://www.billa.at/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (559 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix57
  • 1 linked page is broken

    Your homepage links to https://www.billa.at/sortiment-und-eigenmarken/eigenmarken, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://www.billa.at/unsere-aktionen%2Fflugblatt and https://www.billa.at/unsere-aktionen/flugblatt all use the title “BILLA Flugblatt | BILLA”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.billa.at/frischgekocht/rezept has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.billa.at/unsere-aktionen%2Fflugblatt and https://www.billa.at/unsere-aktionen/flugblatt use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://www.billa.at/unsere-aktionen%2Fflugblatt, https://www.billa.at/unsere-aktionen/flugblatt, https://www.billa.at/unsere-maerkte/services-in-den-maerkten/pfand, https://www.billa.at/sortiment-und-eigenmarken/trends-bei-billa and https://www.billa.at/einfachmitreden 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 21 found) and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Hydration completed but contains mismatches.”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    18 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 35 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 396 words of copy

    The homepage carries about 396 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “ONLINE SHOP”, “Zum Online Shop” and “Foto Shop”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 7 other companies contacted

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

1 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at billa.at, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Analytics
Google Tag Manager
Hosting
Google Cloud

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on billa.at, including 20 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25