Website review, no card needed
stoertebekker.com website review
Visit site (opens in a new tab)Reviewed 20 November 202643 issues · 89 checks
This review found 43 issues worth fixing on stoertebekker.com, 16 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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- #55,319 of 123,808 reviewed websitesbeats 50%
- #36,385 of 69,682 online storesbeats 42%
- #34,860 of 63,392 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.9 s |
| Nov 14, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 147 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 152 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 161 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 194 ms |
| Sep 26, 2026 | 214 ms |
| Oct 3, 2026 | 234 ms |
| Oct 10, 2026 | 244 ms |
| Oct 17, 2026 | 249 ms |
| Oct 24, 2026 | 250 ms |
| Oct 31, 2026 | 246 ms |
| Nov 7, 2026 | 241 ms |
| Nov 14, 2026 | 236 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.4 s
4.7 s
7.1 s
9.4 s
11.8 s
14.1 s
16.5 s
18.8 s
Speed
Render-blocking requests
1.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
5,654 HTML elements
The page has 5,654 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
50 ms · 4.0 MB43 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Use efficient cache lifetimes
900 ms · 831 KiB42 files are served with short cache lifetimes, so returning visitors download them again (831 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Reviews.io and baqend.com and others), adding 3.8 MB and 1.1 s of main-thread time.
Reduce unused JavaScript
600 ms · 865 KiBAbout 865 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Shopify adds 380 ms
380 msShopify costs a phone 380 ms of main-thread work and 2.9 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.
Reviews.io adds 348 ms
348 msReviews.io costs a phone 348 ms of main-thread work and 736 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.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
Reduce unused CSS
150 ms · 50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
Minify JavaScript
78 KiB78 KiB could be saved by minifying JavaScript.
Legacy JavaScript
60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 91 ms
91 msYour server sent the HTML in 91 ms, well inside Google's 600 ms guideline.
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.
Largest Contentful Paint: 12.6 s
12.6 sYour largest element takes 12.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Störtebekker”.
Time to Interactive: 37.9 s
37.9 sThe page becomes fully interactive after 37.9 s. Good is under 3.8 s.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user INP: 234 ms
234 msReal visitors wait 234 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 66% slower for real visitors
+66%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 142 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
52 images without width and height
52 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 224 ms
224 msScripts block taps and scrolling for 224 ms in total while the page loads. Good is under 200 ms.
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 570 ms
570 msReal visitors wait 570 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.5 MB in 544 requests
9.5 MBYour homepage downloads 9.5 MB in 544 requests on a phone: images 5.1 MB (101), scripts 2.3 MB (118) and other files 1.5 MB (298). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
team-bild-office_9f6a797d-f7b8-4d2d-aabb-637e6c02b76a.jpg weighs 1.6 MB. On a phone connection a single image that size takes seconds.
19 images far larger than shown
856 KiB19 images are downloaded at several times the size a phone draws them, for example team-bild-office_9f6a797d-f7b8-4d2d-aabb-637e6c02b76a.jpg at 1,274 px wide, shown at 360 px. Resized copies would save about 856 KiB.
28 images below the first screen load straight away
28 images further down the page (4.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
10 images in older formats
10 images (1.7 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.
About 2.7 g of CO₂ per visit
2.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.70 g of CO₂e: 323.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (8 elements)
Elements must only use permitted ARIA attributes: 8 elements on the page fail this check, rated serious by axe-core.
76 images without alt text
76 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (141 elements)
All page content should be contained by landmarks: 141 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (24 elements).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
150 internal links, 5 external
The homepage links to 150 pages on stoertebekker.com and 5 external pages.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “High-quality men's grooming products for the face, hair, and body—For Men Who Care! Safety razors, shampoos, skincare, …”.
Title: 55 characters
Your title is a healthy 55 characters: “Störtebekker - Premium Men's Skincare for Face and Body”.
Canonical URL set
The canonical URL is https://stoertebekker.com/en-in.
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://stoertebekker.com/sitemap.xml.
AI search readiness
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.
Some text only appears after JavaScript runs
50%The HTML your server sends has 982 of the 1,971 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://stoertebekker.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages share 2 titles
https://stoertebekker.com/en-in/collections/haare-kopfhaut, https://stoertebekker.com/en-in/collections/festes-shampoo, https://stoertebekker.com/en-in/collections/produkte-gegen-schuppen, https://stoertebekker.com/en-in/collections/fettige-kopfhaut and https://stoertebekker.com/en-in/collections/produkte-fur-empflindliche-kopfhaut all use the title “Solid shampoo - sustainable and ideal for travelling”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://stoertebekker.com/en-in/collections/haare-kopfhaut, https://stoertebekker.com/en-in/collections/festes-shampoo, https://stoertebekker.com/en-in/collections/produkte-gegen-schuppen, https://stoertebekker.com/en-in/collections/fettige-kopfhaut and https://stoertebekker.com/en-in/collections/produkte-fur-empflindliche-kopfhaut use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://stoertebekker.com/en-in/collections/sets, https://stoertebekker.com/en-in/collections/haare-kopfhaut, https://stoertebekker.com/en-in/collections/festes-shampoo, https://stoertebekker.com/en-in/collections/haar-booster, https://stoertebekker.com/en-in/collections/pomade and https://stoertebekker.com/en-in/products/sea-salt-spray-sandelholz and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://stoertebekker.com/en-in/collections/haar-booster, https://stoertebekker.com/en-in/collections/pomade, https://stoertebekker.com/en-in/products/sea-salt-spray-sandelholz, https://stoertebekker.com/en-in/products/hair-body-wash, https://stoertebekker.com/en-in/collections/deo and https://stoertebekker.com/en-in/products/handseife-sandelholz-100g and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 90 found) and read each the way a search engine does.
5 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 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “ablyftTools is not defined”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
32 of 34 tappable elements near the top are at least 24 px.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 1,971 words of copy
The homepage carries about 1,971 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Help & Contact”.
13 short forms
13 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 3 trust badges.
Analytics in place
Analytics detected: Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Klaviyo, Meta Pixel and Outbrain and 1 more (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.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 3 of them by other companies (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.
39 other companies contacted
Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 stoertebekker.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on stoertebekker.com, including 20 speed issues, 3 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.