Website review, no card needed
albstoffe.de website review
Visit site (opens in a new tab)Reviewed 9 November 202627 issues · 71 checks
This review found 27 issues worth fixing on albstoffe.de, 12 of them high impact, across 71 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
79C- #54,171 of 120,620 reviewed websitesbeats 50%
- #35,786 of 68,290 online storesbeats 42%
- #34,313 of 62,230 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 103 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 109 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 106 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 110 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 116 ms |
| Oct 3, 2026 | 118 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 113 ms |
| Oct 24, 2026 | 113 ms |
| Oct 31, 2026 | 116 ms |
| Nov 7, 2026 | 113 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
2.0 s
4.0 s
6.0 s
8.1 s
10.1 s
12.1 s
14.1 s
16.1 s
Speed
Improve image delivery
3.8 s · 1.3 MB15 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.
Reduce unused JavaScript
1.2 s · 217 KiBAbout 217 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 96 KiB12 files are served with short cache lifetimes, so returning visitors download them again (96 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Adroll and others), adding 525 KiB and 507 ms of main-thread time.
Google Tag Manager adds 257 ms
257 msGoogle Tag Manager costs a phone 257 ms of main-thread work and 317 KiB 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 908 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,545 HTML elements
The page has 1,545 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 212 ms. During a long task the page ignores taps.
Duplicated JavaScript
150 ms · 6 KiB6 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 43 ms
43 msYour server sent the HTML in 43 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 18.7 s
18.7 sYour largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DIE WEIHNACHTSSENSATION 2026 Sie ist wieder da - aber nur f…”.
Time to Interactive: 20.2 s
20.2 sThe page becomes fully interactive after 20.2 s. Good is under 3.8 s.
Speed Index: 11.6 s
11.6 sVisually, the page fills in at 11.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 103 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
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: 381 ms
381 msReal visitors wait 381 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 137 ms
137 msScripts block the page for only 137 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 18.2 MB in 300 requests
18.2 MBYour homepage downloads 18.2 MB in 300 requests on a phone: media 12.9 MB (1), images 3.4 MB (41) and other files 1.0 MB (193). Under 2 MB keeps phones on slow connections fast.
About 5.1 g of CO₂ per visit
5.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.15 g of CO₂e: 617.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
[aria-*] attributes do not have valid values
[aria-*] attributes do not have valid values (1 element).
9 links without text
9 links have no text or label, so screen readers cannot say where they go.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
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.
195 internal links, 13 external
The homepage links to 195 pages on albstoffe.de and 13 external pages.
7 checks passed
One H1 headline
Your main headline reads: “MADE IN GERMANY”.
Title: 43 characters
Your title is a healthy 43 characters: “Albstoffe - ENTDECKE DIE WELT VON ALBSTOFFE”.
Canonical URL set
The canonical URL is https://albstoffe.de/.
Structured data in place
Structured data found: Organization and WebSite.
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://albstoffe.de/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://albstoffe.de/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.
7 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 a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
6 console errors
6 errors were logged to the browser console during Google's test (“[OptinMonster] This account is not currently active. It is either expired, paused, archived, cancel…”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 1,197 words of copy
The homepage carries about 1,197 words of visible text.
3 checks passed
4 short forms
4 short forms (6 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: 0 phone links and 1 email link.
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 albstoffe.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
weglot.com · nfcube.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
- The footer still says © 2021.
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on albstoffe.de, including 14 speed issues, 4 SEO issues and 2 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.