Website review, no card needed
berq-shop.de website review
Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 74 checks
This review found 29 issues worth fixing on berq-shop.de, 9 of them high impact, across 74 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
82B- #35,083 of 125,829 reviewed websitesbeats 67%
- #23,059 of 70,272 online storesbeats 61%
- #22,258 of 63,832 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 68 ms |
| May 23, 2026 | 72 ms |
| May 30, 2026 | 72 ms |
| Jun 6, 2026 | 67 ms |
| Jun 13, 2026 | 67 ms |
| Jun 20, 2026 | 70 ms |
| Jun 27, 2026 | 70 ms |
| Jul 4, 2026 | 70 ms |
| Jul 11, 2026 | 73 ms |
| Jul 18, 2026 | 108 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 133 ms |
| Aug 29, 2026 | 131 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 125 ms |
| Oct 3, 2026 | 126 ms |
| Oct 10, 2026 | 127 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 123 ms |
| Oct 31, 2026 | 119 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
7.2 s · 1.7 MB50 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Improve image delivery
1.8 s · 672 KiB2 images could be 672 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.9 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
770 ms · 101 KiBAbout 101 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 770 ms faster on a phone.
Font display
800 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.
3 third-party services on the page
3 third-party services load with your homepage (Cookie-Script.com, JSPM and Google Fonts), adding 40 KiB and 61 ms of main-thread time.
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.
Legacy JavaScript
5 KiBPolyfills for old browsers add 5 KiB JavaScript that modern phones do not need.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 164 ms of it running JavaScript. That is comfortably low.
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “0 berq berq”.
Time to Interactive: 10.1 s
10.1 sThe page becomes fully interactive after 10.1 s. Good is under 3.8 s.
Tap response (INP) got 73% slower for real visitors
+73%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 68 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 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.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: 566 ms
566 msReal visitors wait 566 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Total Blocking Time: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.1 MB in 54 requests
2.1 MBYour homepage downloads 2.1 MB in 54 requests on a phone: images 1.2 MB (5), fonts 605 KiB (5) and scripts 137 KiB (40). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
228 KiB1 image is downloaded at several times the size a phone draws it, for example Berq_Merch_+warm-06022.jpg at 1,500 px wide, shown at 301 px. Resized copies would save about 228 KiB.
2 images in older formats
2 images (415 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 0.6 g of CO₂ per visit
0.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 70.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 1 failed. 2 mores 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 canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
21 internal links, 6 external
The homepage links to 21 pages on berq-shop.de and 6 external pages.
5 checks passed
Meta description: 76 characters
Your meta description is 76 characters: “Berq – Jetzt Tickets & Merchandise im offiziellen Shop des Künstlers kaufen!”.
Title: 55 characters
Your title is a healthy 55 characters: “Berq – Tickets & Merchandise im offiziellen Shop kaufen”.
Structured data in place
Structured data found: Organization and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.berq-shop.de/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
11%A phone browser shows 679 words, but the HTML your server sends has only 77. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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.berq-shop.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.
1 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.
Other pages
1 linked page hidden from search
https://www.berq-shop.de/socialticket is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
7 pages share a title
https://www.berq-shop.de/home, https://www.berq-shop.de/tickets, https://www.berq-shop.de/products, /, https://www.berq-shop.de/tnc and https://www.berq-shop.de/imprint and 1 other all use the title “Berq – Tickets & Merchandise im offiziellen Shop kaufen”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://www.berq-shop.de/tickets, https://www.berq-shop.de/products, /, https://www.berq-shop.de/tnc, https://www.berq-shop.de/imprint and https://www.berq-shop.de/privacy use the same meta description. A description written for each page earns more clicks.
4 pages without an H1
https://www.berq-shop.de/tickets, https://www.berq-shop.de/products, / and https://www.berq-shop.de/socialticket have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.berq-shop.de/tickets, https://www.berq-shop.de/products and / 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.
7 internal pages checked
We fetched 7 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 7 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 7 pages that loaded have a meta description.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 25 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 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 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 679 words of copy
The homepage carries about 679 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “berq-shop.de/socialticket”.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
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 berq-shop.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
- E-commerce
- 10 Shopify Products;Shopify;Shopify Plus
- Hosting
- Plus.line AG
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on berq-shop.de, including 13 speed issues, 3 SEO 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.