Website review, no card needed
calumet.de website review
Visit site (opens in a new tab)Reviewed 20 November 202646 issues · 90 checks
This review found 46 issues worth fixing on calumet.de, 19 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
71C- #97,947 of 121,360 reviewed websitesbeats 17%
- #60,199 of 68,666 online storesbeats 10%
- #69 of 82 Shopware storesbeats 16%
Closest competitors among Shopware stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 179 ms |
| Jun 6, 2026 | 180 ms |
| Jun 13, 2026 | 183 ms |
| Jun 20, 2026 | 183 ms |
| Jun 27, 2026 | 184 ms |
| Jul 4, 2026 | 185 ms |
| Jul 11, 2026 | 185 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 186 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 192 ms |
| Aug 15, 2026 | 192 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 194 ms |
| Sep 5, 2026 | 193 ms |
| Sep 12, 2026 | 197 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 206 ms |
| Oct 10, 2026 | 207 ms |
| Oct 17, 2026 | 211 ms |
| Oct 24, 2026 | 208 ms |
| Oct 31, 2026 | 207 ms |
| Nov 7, 2026 | 204 ms |
| Nov 14, 2026 | 204 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
Speed
Use efficient cache lifetimes
6.0 s · 1.5 MB178 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Render-blocking requests
5.6 s103 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.6 s.
Reduce unused JavaScript
1.6 s · 305 KiBAbout 305 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
6,841 HTML elements
The page has 6,841 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Usercentrics CMP, trbo.com and Google Tag Manager and others), adding 1.7 MB and 989 ms of main-thread time.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Usercentrics CMP adds 586 ms
586 msUsercentrics CMP costs a phone 586 ms of main-thread work and 197 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.
Reduce unused CSS
450 ms · 149 KiBAbout 149 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.
Improve image delivery
376 KiB4 images could be 376 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
trbo.com adds 203 ms
203 mstrbo.com costs a phone 203 ms of main-thread work and 321 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.
storyblok.com adds 0 ms
0 msstoryblok.com costs a phone 0 ms of main-thread work and 882 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 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.
1 checks passed
Server response: 236 ms
236 msYour server sent the HTML in 236 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: 17.8 s
17.8 sYour largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Red Week bei Calumet”.
Time to Interactive: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 287 ms
287 msReal visitors wait 287 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 914 ms
914 msReal visitors wait 914 ms for your server to start answering (75th percentile). Good is under 800 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 179 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 76 ms
76 msScripts block the page for only 76 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 289 requests
3.1 MBYour homepage downloads 3.1 MB in 289 requests on a phone: scripts 1.1 MB (82), images 1.1 MB (93) and fonts 576 KiB (1). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
red-week-26_mp_m_1470x834.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
43 KiB1 image is downloaded at several times the size a phone draws it, for example red-week-26_mp_m_1470x834.webp at 1,470 px wide, shown at 358 px. Resized copies would save about 43 KiB.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
46 buttons without a name
46 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must be contained by particular parents (12 elements)
Certain ARIA roles must be contained by particular parents: 12 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
Orphan list items
Some list items are not inside a list.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 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.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
54 links without text
54 visible links have no text or label, so screen readers cannot say where they go.
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.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 14 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
285 internal links, 9 external
The homepage links to 285 pages on calumet.de and 9 external pages.
8 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Bestelle dein Foto- & Videoequipment jetzt online! ✓ Beratung vom Profi ✓ Riesige Auswahl ✓ Kostenlose Lieferung ab 39 …”.
One H1 headline
Your main headline reads: “Calumet Photo Video - dein Online-Shop für Kameras, Objektive und Zubehör”.
Title: 56 characters
Your title is a healthy 56 characters: “Calumet Photo Video » Kaufe Kameras, Objektive & Zubehör”.
Canonical URL set
The canonical URL is https://www.calumet.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.calumet.de/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.calumet.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.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,741 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.calumet.de/wishlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.calumet.de/kameras-und-objektive-verkaufen and https://www.calumet.de/stores all use the title “Calumet Photo Video”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.calumet.de/kameras-und-objektive-verkaufen and https://www.calumet.de/stores use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.calumet.de/stores and https://www.calumet.de/wishlist have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.calumet.de/category/kameras and https://www.calumet.de/category/video-drohnen took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 187 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 a meta description
All 15 pages that loaded have a meta description.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
24 small tap targets
24 of 91 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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 2,254 words of copy
The homepage carries about 2,254 words of visible text.
3 checks passed
44 short forms
44 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 475 testimonial or review blocks, 1 customer or partner logo and 6 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
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.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
16 other companies contacted
Loading the homepage contacts 16 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 calumet.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
- Tailwind CSS
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Hetzner
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on calumet.de, including 21 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.