Website review, no card needed
onelove-shop.de website review
Visit site (opens in a new tab)Reviewed 8 November 202627 issues · 83 checks
This review found 27 issues worth fixing on onelove-shop.de, 8 of them high impact, across 83 checks. The most urgent: 10,808 HTML elements. 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
87B- #8,452 of 123,197 reviewed websitesbeats 90%
- #4,856 of 69,453 online storesbeats 90%
- #4,705 of 63,227 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 113 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 108 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 92 ms |
| Jun 20, 2026 | 89 ms |
| Jun 27, 2026 | 90 ms |
| Jul 4, 2026 | 91 ms |
| Jul 11, 2026 | 93 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 97 ms |
| Aug 8, 2026 | 97 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 98 ms |
| Aug 29, 2026 | 101 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 102 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 107 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.6 s
1.3 s
1.9 s
2.5 s
3.1 s
3.8 s
4.4 s
5.0 s
Speed
10,808 HTML elements
The page has 10,808 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 63
63/100Your mobile performance score is 63. 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 (Shopify, Clarity and Klaviyo and others), adding 959 KiB and 584 ms of main-thread time.
Render-blocking requests
650 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Improve image delivery
501 KiB16 images could be 501 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 250 ms
250 msShopify costs a phone 250 ms of main-thread work and 584 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 237 ms. During a long task the page ignores taps.
Reduce unused JavaScript
173 KiBAbout 173 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
28 KiB5 files are served with short cache lifetimes, so returning visitors download them again (28 KiB).
Reduce unused CSS
21 KiBAbout 21 KiB of CSS is downloaded but never applied on this page.
Duplicated JavaScript
7 KiB7 KiB JavaScript is shipped twice across bundles.
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 29 ms
29 msYour server sent the HTML in 29 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.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 10.2 s
10.2 sThe page becomes fully interactive after 10.2 s. Good is under 3.8 s.
Largest content (LCP) got 66% slower for real visitors
+66%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Unbenannt_-_30”.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 113 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user TTFB: 577 ms
577 msReal visitors wait 577 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.046
0.046The layout barely moves while loading (CLS 0.046, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 239 requests
2.8 MBYour homepage downloads 2.8 MB in 239 requests on a phone: images 934 KiB (21), other files 858 KiB (91) and scripts 801 KiB (97). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 95.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 335 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 4 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.
197 internal links, 2 external
The homepage links to 197 pages on onelove-shop.de and 2 external pages.
7 checks passed
Meta description: 96 characters
Your meta description is 96 characters: “Entdecke unseren maritimen Shop für alle Meer-Liebhaber. Für klein & groß, designt in Rostock ⚓︎”.
Title: 43 characters
Your title is a healthy 43 characters: “ONELOVE - aus Liebe zum Meer – ONELOVE SHOP”.
Canonical URL set
The canonical URL is https://onelove-shop.de/.
Structured data in place
Structured data found: 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://onelove-shop.de/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
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.
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.
llms.txt published
The site publishes https://onelove-shop.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://onelove-shop.de/collections/bestseller, https://onelove-shop.de/collections/mysteryboxen, https://onelove-shop.de/collections/frauen, https://onelove-shop.de/collections/t-shirts-fur-frauen, https://onelove-shop.de/collections/sweater-fur-frauen and https://onelove-shop.de/collections/hoodies-fur-frauen and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://onelove-shop.de/collections/bestseller, https://onelove-shop.de/collections/frauen, https://onelove-shop.de/collections/t-shirts-fur-frauen, https://onelove-shop.de/collections/hoodies-fur-frauen, https://onelove-shop.de/collections/manner and https://onelove-shop.de/collections/t-shirts-fur-manner and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://onelove-shop.de/collections/hoodies-fur-frauen, https://onelove-shop.de/collections/premium-stickereien, https://onelove-shop.de/collections/hoodies-fur-manner and https://onelove-shop.de/collections/kids-baby 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.
4 pages slow to respond
https://onelove-shop.de/collections/t-shirts-fur-frauen, https://onelove-shop.de/collections/premium-stickereien, https://onelove-shop.de/collections/manner and https://onelove-shop.de/collections/t-shirts-fur-manner took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 91 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
29 small tap targets
29 of 61 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 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,978 words of copy
The homepage carries about 2,978 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ONELOVE SHOP”.
1 short form
A short form (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 76 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
18 other companies contacted
Loading the homepage contacts 18 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 onelove-shop.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on onelove-shop.de, including 14 speed issues, 1 SEO issue 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.