Website review, no card needed
mosquets.de website review
Visit site (opens in a new tab)Reviewed 12 November 202634 issues · 78 checks
This review found 34 issues worth fixing on mosquets.de, 13 of them high impact, across 78 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
73C- #78,058 of 104,906 reviewed websitesbeats 22%
- #48,265 of 58,835 online storesbeats 15%
- #45,202 of 53,594 Shopify storesbeats 13%
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.0 s |
| Jun 6, 2026 | 991 ms |
| Jun 13, 2026 | 937 ms |
| Jun 20, 2026 | 928 ms |
| Jun 27, 2026 | 970 ms |
| Jul 4, 2026 | 991 ms |
| Jul 11, 2026 | 995 ms |
| Jul 18, 2026 | 954 ms |
| Jul 25, 2026 | 939 ms |
| Aug 1, 2026 | 934 ms |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 86 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 81 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 91 ms |
| Jul 11, 2026 | 91 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 89 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 98 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 90 ms |
| Sep 12, 2026 | 91 ms |
| Sep 19, 2026 | 93 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 100 ms |
| Oct 10, 2026 | 110 ms |
| Oct 17, 2026 | 118 ms |
| Oct 24, 2026 | 121 ms |
| Oct 31, 2026 | 105 ms |
| Nov 7, 2026 | 96 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
Improve image delivery
12.9 s · 6.3 MB46 images could be 6.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.9 s faster on a phone.
Use efficient cache lifetimes
3.8 s · 454 KiB29 files are served with short cache lifetimes, so returning visitors download them again (454 KiB).
Reduce unused JavaScript
1.8 s · 300 KiBAbout 300 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, omnisnippet1.com and sizekick.io and others), adding 663 KiB and 806 ms of main-thread time.
Reduce unused CSS
510 ms · 56 KiBAbout 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 510 ms faster on a phone.
Render-blocking requests
300 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
1,652 HTML elements
The page has 1,652 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 199 ms. During a long task the page ignores taps.
Minify CSS
50 ms · 3 KiB3 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.
Legacy JavaScript
5 KiBPolyfills for old browsers add 5 KiB JavaScript that modern phones do not need.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 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: 45.8 s
45.8 sYour largest element takes 45.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 47.6 s
47.6 sThe page becomes fully interactive after 47.6 s. Good is under 3.8 s.
Speed Index: 13.6 s
13.6 sVisually, the page fills in at 13.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 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.
Largest content (LCP) got 59% slower for real visitors
+59%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 273 ms
273 msScripts block taps and scrolling for 273 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 86 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 113 ms
113 msReal visitors wait 113 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 TTFB: 388 ms
388 msReal visitors wait 388 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 12.0 MB in 336 requests
12.0 MBYour homepage downloads 12.0 MB in 336 requests on a phone: images 9.9 MB (90), other files 1,005 KiB (165) and scripts 837 KiB (66). Under 2 MB keeps phones on slow connections fast.
About 3.4 g of CO₂ per visit
3.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.40 g of CO₂e: 407.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
96 images without alt text
96 images have no alt text, which hurts accessibility and image search.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
4 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 4 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Mosquets Clothing”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (51 characters)
Your meta description is only 51 characters: “Ready-To-Wear Luxury Garments. Designed in Germany.”. 70 to 160 characters is enough to sell the click.
207 internal links, 2 external
The homepage links to 207 pages on mosquets.de and 2 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Mosquets”.
Canonical URL set
The canonical URL is https://mosquets.de/.
Structured data in place
Structured data found: BreadcrumbList, 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://mosquets.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://mosquets.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without a meta description
https://mosquets.de/collections/new-collection, https://mosquets.de/collections/all-tops, https://mosquets.de/collections/sweaters, https://mosquets.de/collections/shirts, https://mosquets.de/collections/pants and https://mosquets.de/collections/long-pants and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://mosquets.de/collections/hoodies, https://mosquets.de/collections/jackets and https://mosquets.de/collections/t-shirts use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://mosquets.de/collections/new-collection, https://mosquets.de/collections/hoodies, https://mosquets.de/collections/all-tops, https://mosquets.de/collections/jackets, https://mosquets.de/collections/t-shirts and https://mosquets.de/collections/sweaters and 9 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 55 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.
Titles are unique
Every page we checked has its own title.
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
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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.
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 668 words of copy
The homepage carries about 668 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “SHOP” and “Shop Now”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 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.
7 other companies contacted
Loading the homepage contacts 7 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 mosquets.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Omnisend · Countdown Timer · Bestpush · privy.com · chimpstatic.com · weglot.com · amazonaws.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
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on mosquets.de, including 18 speed issues, 2 SEO issues and 5 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.