Website review, no card needed

hofer.at logo

hofer.at website review

Visit site (opens in a new tab)Reviewed 27 October 202631 issues · 79 checks

This review found 31 issues worth fixing on hofer.at, 11 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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.4 s1.9 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
179 ms107 msMay 9Oct 24160 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026115 ms
May 16, 2026117 ms
May 23, 2026117 ms
May 30, 2026119 ms
Jun 6, 2026121 ms
Jun 13, 2026122 ms
Jun 20, 2026124 ms
Jun 27, 2026126 ms
Jul 4, 2026127 ms
Jul 11, 2026129 ms
Jul 18, 2026134 ms
Jul 25, 2026142 ms
Aug 1, 2026157 ms
Aug 8, 2026169 ms
Aug 15, 2026171 ms
Aug 22, 2026170 ms
Aug 29, 2026164 ms
Sep 5, 2026159 ms
Sep 12, 2026154 ms
Sep 19, 2026151 ms
Sep 26, 2026153 ms
Oct 3, 2026154 ms
Oct 10, 2026156 ms
Oct 17, 2026159 ms
Oct 24, 2026160 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 hofer.at (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hofer.at at 0.4 s0.4 s
  2. hofer.at at 0.8 s0.8 s
  3. hofer.at at 1.1 s1.1 s
  4. hofer.at at 1.5 s1.5 s
  5. hofer.at at 1.9 s1.9 s
  6. hofer.at at 2.3 s2.3 s
  7. hofer.at at 2.6 s2.6 s
  8. hofer.at at 3.0 s3.0 s

Speed

10 to fix59
  • Reduce unused JavaScript

    1.5 s · 354 KiB

    About 354 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Use efficient cache lifetimes

    1.1 s · 653 KiB

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

  • Improve image delivery

    300 ms · 710 KiB

    19 images could be 710 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Mobile performance score: 59

    59/100

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

  • Render-blocking requests

    950 ms

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

  • 6 long tasks on the main thread

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Adobe Tag Manager, Optanon and aldi.cx and others), adding 1.6 MB and 126 ms of main-thread time.

  • Main-thread work: 2.6 s

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

  • 1,956 HTML elements

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

  • aldi.cx adds 0 ms

    0 ms

    aldi.cx costs a phone 0 ms of main-thread work and 1.2 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.

  • Reduce unused CSS

    33 KiB

    About 33 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    17 KiB

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

  • Phones get a much slower page than desktops

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

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

1 checks passed
  • Server response: 240 ms

    240 ms

    Your server sent the HTML in 240 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 10.6 s

    10.6 s

    Your largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir setzen Cookies und ähnliche Technologien ein, um unsere…”.

  • Time to Interactive: 10.8 s

    10.8 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Speed Index: 6.4 s

    6.4 s

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

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

    +38%

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

  • 1 image without width and height

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 155 ms

    155 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 693 ms

    693 ms

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

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Total Blocking Time: 194 ms

    194 ms

    Scripts block the page for only 194 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

2 to fix78
  • Page weight: 2.6 MB in 203 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 203 requests on a phone: images 1.3 MB (62), scripts 953 KiB (82) and other files 97 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 11 images below the first screen load straight away

    11 images further down the page (783 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.73 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9595
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 2 images without alt text

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

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

  • No X (Twitter) card tag

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

  • 126 internal links, 21 external

    The homepage links to 126 pages on hofer.at and 21 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “HOFER heißt Qualität zum günstigen Preis ✓ Wöchentlich neue Angebote ✓ Großes Produktsortiment in über 530 Filialen ➤ J…”.

  • One H1 headline

    Your main headline reads: “Startseite”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Da bin ich mir sicher - Lebensmittel zum HOFER Preis | HOFER”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList and Organization.

  • 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.hofer.at/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.hofer.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.

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

3 to fix80
  • 7 linked pages hidden from search

    https://www.hofer.at/angebote/2026-10-20, https://www.hofer.at/angebote/2026-10-22, https://www.hofer.at/angebote/2026-10-23, https://www.hofer.at/angebote/2026-10-27, https://www.hofer.at/angebote/2026-10-29 and https://www.hofer.at/angebote/2026-10-30 and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 7 pages share a title

    https://www.hofer.at/angebote/2026-10-20, https://www.hofer.at/angebote/2026-10-22, https://www.hofer.at/angebote/2026-10-23, https://www.hofer.at/angebote/2026-10-27, https://www.hofer.at/angebote/2026-10-29 and https://www.hofer.at/angebote/2026-10-30 and 1 other all use the title “Aktuelle Angebote | HOFER”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://www.hofer.at/tools/features/angebote, https://www.hofer.at/angebote/2026-10-20, https://www.hofer.at/angebote/2026-10-22, https://www.hofer.at/angebote/2026-10-23, https://www.hofer.at/angebote/2026-10-27 and https://www.hofer.at/angebote/2026-10-29 and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages slow to respond

    https://www.hofer.at/angebote/2026-10-29, https://www.hofer.at/angebote/2026-10-30, https://www.hofer.at/angebote/2026-11-02 and https://www.hofer.at/flugblatt took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 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.”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    80 of 81 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix20
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 756 words of visible text.

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 4 other companies contacted

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

2 checks passed
  • Consent tool: OneTrust

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

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 hofer.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
Hosting
Akamai

Company

Founded
1962
Headquarters
Sattledt

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on hofer.at, including 16 speed issues, 1 SEO issue and 5 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