Website review, no card needed
quadlockcase.eu website review
Visit site (opens in a new tab)Reviewed 4 November 202633 issues · 84 checks
This review found 33 issues worth fixing on quadlockcase.eu, 11 of them high impact, across 84 checks. The most urgent: page weight: 20.7 MB in 295 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
80B- #46,128 of 117,121 reviewed websitesbeats 55%
- #30,840 of 66,867 online storesbeats 47%
- #29,677 of 60,987 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 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 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 137 ms |
| May 23, 2026 | 135 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 142 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 148 ms |
| Jul 4, 2026 | 152 ms |
| Jul 11, 2026 | 151 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 150 ms |
| Aug 1, 2026 | 151 ms |
| Aug 8, 2026 | 152 ms |
| Aug 15, 2026 | 151 ms |
| Aug 22, 2026 | 152 ms |
| Aug 29, 2026 | 151 ms |
| Sep 5, 2026 | 151 ms |
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 152 ms |
| Sep 26, 2026 | 153 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 153 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 161 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
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 576 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Wunderkind and Clarity and others), adding 16.5 MB and 1.7 s of main-thread time.
Shopify adds 117 ms
117 msShopify costs a phone 117 ms of main-thread work and 15.6 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.
Reduce unused JavaScript
900 ms · 300 KiBAbout 300 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 465 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
300 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
1,617 HTML elements
The page has 1,617 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 42 KiB20 files are served with short cache lifetimes, so returning visitors download them again (42 KiB).
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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.4 s
14.4 sYour largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to ensure you get the best experi…”.
Time to Interactive: 19.2 s
19.2 sThe page becomes fully interactive after 19.2 s. Good is under 3.8 s.
Total Blocking Time: 928 ms
928 msScripts block taps and scrolling for 928 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
45 images without width and height
45 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 137 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 472 ms
472 msReal visitors wait 472 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 20.7 MB in 295 requests
20.7 MBYour homepage downloads 20.7 MB in 295 requests on a phone: media 17.5 MB (2), scripts 1.3 MB (70) and other files 1.2 MB (166). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
91 KiB1 image is downloaded at several times the size a phone draws it, for example QL-WEB-0186_HomePageHype-Brand_Introduction_Reel_16x9_v2.00_ at 1,920 px wide, shown at 390 px. Resized copies would save about 91 KiB.
About 5.9 g of CO₂ per visit
5.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.88 g of CO₂e: 705.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Headings skip levels
Headings skip levels (h4 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 63 images in the HTML carry an alt attribute.
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 0 failed. 3 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.
Meta description is long (208 characters)
Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
220 internal links, 27 external
The homepage links to 220 pages on quadlockcase.eu and 27 external pages.
6 checks passed
Title: 34 characters
Your title is a healthy 34 characters: “Quad Lock Europe® - Official Store”.
Canonical URL set
The canonical URL is https://www.quadlockcase.eu/.
Structured data in place
Structured data found: Organization, Store 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://www.quadlockcase.eu/sitemap.xml.
AI search readiness
4 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, description and contact details; logo and sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,426 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.quadlockcase.eu/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.quadlockcase.eu/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.quadlockcase.eu/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.quadlockcase.eu/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://www.quadlockcase.eu/customer_authentication/redirect, https://www.quadlockcase.eu/products/cases-airpods, https://www.quadlockcase.eu/products/iphone-colored-cases, https://www.quadlockcase.eu/de, https://www.quadlockcase.eu/es and https://www.quadlockcase.eu/fr and 3 others 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 164 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Best practices
3 broken images
3 images failed to load on a phone, for example https://cdn.sanity.io/images/3azemr64/production/24fbd340450bc0b4fb400cfbd03327104794272d-540x960.jpg?auto=format&w=540&h=960&crop=center&fit=crop.
15 small tap targets
15 of 63 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,060 words of copy
The homepage carries about 1,060 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “1 SIGN UP” and “Sign up”.
11 calls to action
The homepage has 11 calls to action, for example “AIRPODS 5 CASES | Shop Now”, “Contact Us” and “NEW AIRPODS 5 CASEAVAILABLE NOW BUY NOW”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 36 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Plausible and TikTok Pixel.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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, Google Tag Manager, Klaviyo and Microsoft Ads 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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 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.
42 other companies contacted
Loading the homepage contacts 42 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 quadlockcase.eu, 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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Wunderkind · Elevar Conversion Tracking · Ab Tasty · Gdpr Backpack · Polar Analytics
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
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Plausible
- Hosting
- Shopify
Hiring
- Hiring
- 2 open roles
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on quadlockcase.eu, including 16 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.