Website review, no card needed
bofrost.de website review
Visit site (opens in a new tab)Reviewed 1 November 202647 issues · 93 checks
This review found 47 issues worth fixing on bofrost.de, 25 of them high impact, across 93 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 160 ms |
| May 16, 2026 | 159 ms |
| May 23, 2026 | 159 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 165 ms |
| Jun 20, 2026 | 168 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 176 ms |
| Jul 18, 2026 | 177 ms |
| Jul 25, 2026 | 176 ms |
| Aug 1, 2026 | 179 ms |
| Aug 8, 2026 | 182 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 190 ms |
| Aug 29, 2026 | 191 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 185 ms |
| Sep 19, 2026 | 183 ms |
| Sep 26, 2026 | 181 ms |
| Oct 3, 2026 | 183 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 173 ms |
| Oct 24, 2026 | 163 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
How it loaded on a phone
1.7 s
3.5 s
5.2 s
6.9 s
8.7 s
10.4 s
12.1 s
13.9 s
Speed
Improve image delivery
2.8 s · 1.5 MB53 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.
Render-blocking requests
1.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 21
21/100Your mobile performance score is 21. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,732 HTML elements
The page has 7,732 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce initial server response time
858 msReduce initial server response time. Google estimates savings of 858 ms on a phone.
Document request latency
850 msThe HTML itself could arrive about 850 ms sooner: redirects, a slow server response or missing compression delay everything after it.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 567 ms. During a long task the page ignores taps.
Reduce unused CSS
450 ms · 109 KiBAbout 109 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 291 KiB65 files are served with short cache lifetimes, so returning visitors download them again (291 KiB).
Reduce unused JavaScript
380 KiBAbout 380 KiB of JavaScript is downloaded but never used on this page.
Server response: 958 ms
958 msYour server takes 958 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Usercentrics CMP and Azure Web Services and others), adding 671 KiB and 311 ms of main-thread time.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need.
Minify JavaScript
20 KiB20 KiB could be saved by minifying JavaScript.
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
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.35
0.35For real visitors the layout shifts by 0.35 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Produkte für den Aifryer”.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.57
0.57The layout shifts by 0.57 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 12.5 s
12.5 sThe page becomes fully interactive after 12.5 s. Good is under 3.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
30 images without width and height
30 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 160 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 188 ms
188 msReal visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 536 ms
536 msReal visitors wait 536 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 31% faster for real visitors
-31%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 4.5 MB in 191 requests
4.5 MBYour homepage downloads 4.5 MB in 191 requests on a phone: images 3.1 MB (123), scripts 996 KiB (38) and fonts 147 KiB (5). Under 2 MB keeps phones on slow connections fast.
11 images far larger than shown
813 KiB11 images are downloaded at several times the size a phone draws them, for example bofr-Schnitzel-StrohPommes-Brand-Banner-1600x600px.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 813 KiB.
34 images below the first screen load straight away
34 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images in older formats
6 images (397 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.
About 1.3 g of CO₂ per visit
1.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 154.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (6 elements)
Certain ARIA roles must contain particular children: 6 elements on the page fail this check, rated critical by axe-core.
Required ARIA attributes must be provided (3 elements)
Required ARIA attributes must be provided: 3 elements on the page fail this check, rated critical by axe-core.
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must be contained by particular parents (1 element)
Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.
Positive tabindex
50 elements have a tabindex above 0, which scrambles the keyboard order.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Orphan list items
Some list items are not inside a list.
35 images without alt text
35 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (38 elements)
All page content should be contained by landmarks: 38 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
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
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 65 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 13 failed. 7 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
177 internal links, 8 external
The homepage links to 177 pages on bofrost.de and 8 external pages.
8 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Tiefkühlkost von bofrost* macht Dein Leben leichter und sorgt für Genuss im Handumdrehen. Lass Dir Frische & Genuss dir…”.
One H1 headline
Your main headline reads: “Tiefkühlkost von bofrost* – Frische & Genuss direkt ins Haus”.
Title: 49 characters
Your title is a healthy 49 characters: “Frische Tiefkühlkost direkt ins Haus | bofrost.de”.
Canonical URL set
The canonical URL is https://www.bofrost.de/.
Structured data in place
Structured data found: Organization.
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.bofrost.at/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
No llms.txt
There is no https://www.bofrost.de/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 (1,423 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.bofrost.de/gutscheinbedingungen.html and https://www.bofrost.de/fryzza.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages without a meta description
https://www.bofrost.de/magazin, https://www.bofrost.de/rezeptwelt/rezepte, https://www.bofrost.de/shop/fuer-die-heissluftfritteuse_213000 and https://www.bofrost.de/shop/bestseller_164000 have no meta description, so Google writes the search snippet from whatever text it finds.
8 links to non-canonical URLs
Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.bofrost.de/shop, whose canonical is https://www.bofrost.de/shop?categoryCode=SHOP-ROOT-CATEGORY. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.bofrost.de/fryzza.html and https://www.bofrost.de/shop/angebote_37977/aktion-stroh-pommes.html 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 91 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
57 small tap targets
57 of 222 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://sw-assets.ekomiapps.de/static_resources/widget.css' from origin 'https://www.bofro…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 2,179 words of copy
The homepage carries about 2,179 words of visible text.
3 checks passed
77 short forms
77 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
1 tracker load before any consent
1Before 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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 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 bofrost.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Azure
Company
- Founded
- 1966
- Headquarters
- Straelen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on bofrost.de, including 20 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.