Website review, no card needed
nevernot.com website review
Visit site (opens in a new tab)Reviewed 9 November 202637 issues · 85 checks
This review found 37 issues worth fixing on nevernot.com, 13 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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
74C- #81,734 of 116,071 reviewed websitesbeats 26%
- #52,305 of 66,737 online storesbeats 18%
- #49,270 of 60,921 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 151 ms |
| May 30, 2026 | 152 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 160 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 158 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 165 ms |
| Aug 15, 2026 | 169 ms |
| Aug 22, 2026 | 178 ms |
| Aug 29, 2026 | 181 ms |
| Sep 5, 2026 | 183 ms |
| Sep 12, 2026 | 185 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 180 ms |
| Oct 10, 2026 | 180 ms |
| Oct 17, 2026 | 179 ms |
| Oct 24, 2026 | 179 ms |
| Oct 31, 2026 | 173 ms |
| Nov 7, 2026 | 171 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
Reduce unused JavaScript
1.4 s · 272 KiBAbout 272 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Sentry adds 1.4 s
1.4 sSentry costs a phone 1.4 s of main-thread work and 79 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.
Main-thread work: 12.9 s
A phone's processor spends 12.9 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Sentry, Cookiebot and Shopify and others), adding 1.0 MB and 2.5 s of main-thread time.
Improve image delivery
730 KiB14 images could be 730 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 621 ms. During a long task the page ignores taps.
Cookiebot adds 517 ms
517 msCookiebot costs a phone 517 ms of main-thread work and 41 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.
Use efficient cache lifetimes
350 ms · 137 KiB29 files are served with short cache lifetimes, so returning visitors download them again (137 KiB).
Shopify adds 233 ms
233 msShopify costs a phone 233 ms of main-thread work and 510 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.
2,518 HTML elements
The page has 2,518 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
250 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
Reduce unused CSS
170 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
26 KiB26 KiB could be saved by minifying JavaScript.
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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.2 s
14.2 sYour largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “261030_mobil_banner_snf_minis_sterne”.
Speed Index: 14.5 s
14.5 sVisually, the page fills in at 14.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 23.6 s
23.6 sThe page becomes fully interactive after 23.6 s. Good is under 3.8 s.
Total Blocking Time: 835 ms
835 msScripts block taps and scrolling for 835 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.136
0.136The layout shifts by 0.136 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 151 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.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: 186 ms
186 msReal visitors wait 186 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 FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 553 ms
553 msReal visitors wait 553 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.0 MB in 325 requests
4.0 MBYour homepage downloads 4.0 MB in 325 requests on a phone: images 1.7 MB (141), scripts 1.3 MB (112) and other files 566 KiB (55). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
261030_mobil_banner_snf_minis_sterne.png 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).
About 1.1 g of CO₂ per visit
1.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.8 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
28 buttons without a name
28 buttons have no accessible name, so screen readers announce just “button”.
25 text elements with low contrast
25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (28 elements).
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
8 H1 headlines
There are 8 <h1> headlines (“”, “STAR DROP” and “-10% auf Gleitgel”). One clear main headline is easier for people and search engines.
Meta description is long (181 characters)
Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.
167 internal links, 6 external
The homepage links to 167 pages on nevernot.com and 6 external pages.
6 checks passed
Title: 46 characters
Your title is a healthy 46 characters: “nevernot – deine Go-To Intimate Wellness Brand”.
Canonical URL set
The canonical URL is https://nevernot.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://nevernot.de/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, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,143 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://nevernot.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://nevernot.de/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://nevernot.de/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://nevernot.de/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
11 pages share a meta description
https://nevernot.de/collections/neuheiten, https://nevernot.de/collections/bestseller, https://nevernot.de/collections, https://nevernot.de/collections/intimacy, https://nevernot.de/collections/body-care and https://nevernot.de/collections/hygiene and 5 others use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://nevernot.de/customer_authentication/redirect has 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 58 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
10 small tap targets
10 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
1 checks passed
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.
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
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 831 words of copy
The homepage carries about 831 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Shop All” and “Zurück zum Shop”.
Analytics in place
Analytics detected: Meta Pixel and Hotjar.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Microsoft Ads (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 nevernot.com, 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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Candy Rack · Discount In Cart · chimpstatic.com · cloudfront.net · trustpilot.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on nevernot.com, including 17 speed issues, 2 SEO issues and 4 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.