Website review, no card needed
naipo.ch website review
Visit site (opens in a new tab)Reviewed 16 November 202629 issues · 80 checks
This review found 29 issues worth fixing on naipo.ch, 7 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. 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- #47,899 of 122,681 reviewed websitesbeats 55%
- #31,747 of 69,244 online storesbeats 48%
- #30,523 of 63,061 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Sep 5, 2026 | 1.4 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 19, 2026 | 209 ms |
| Oct 31, 2026 | 219 ms |
| Nov 7, 2026 | 228 ms |
| Nov 14, 2026 | 242 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
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 1.8 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 (Facebook, TikTok and Shopify and others), adding 1.0 MB and 1.2 s of main-thread time.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Use efficient cache lifetimes
409 KiB27 files are served with short cache lifetimes, so returning visitors download them again (409 KiB).
Reduce unused JavaScript
388 KiBAbout 388 KiB of JavaScript is downloaded but never used on this page.
Facebook adds 336 ms
336 msFacebook costs a phone 336 ms of main-thread work and 277 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.
TikTok adds 325 ms
325 msTikTok costs a phone 325 ms of main-thread work and 162 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,667 HTML elements
The page has 2,667 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 236 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
84 KiBPolyfills for old browsers add 84 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
15 KiB15 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.
Improve image delivery
5 KiB1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
5 KiB5 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
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.
Time to Interactive: 16.9 s
16.9 sThe page becomes fully interactive after 16.9 s. Good is under 3.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Real-user INP: 242 ms
242 msReal visitors wait 242 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Die nächste Generation der Entspannung.”.
Total Blocking Time: 395 ms
395 msScripts block taps and scrolling for 395 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 209 ms to 242 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.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: 492 ms
492 msReal visitors wait 492 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 2.5 MB in 193 requests
2.5 MBYour homepage downloads 2.5 MB in 193 requests on a phone: scripts 1.1 MB (83), other files 602 KiB (74) and images 315 KiB (13). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Mini_Massagepistole.jpg 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).
1 image far larger than shown
4 KiB1 image is downloaded at several times the size a phone draws it, for example Mini_Massagepistole.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 4 KiB.
1 image in older formats
1 image (35 KiB) is 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.7 g of CO₂ per visit
0.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.70 g of CO₂e: 84.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 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
Structured data has 1 problem
Structured data found (BreadcrumbList, MobileApplication, Organization and Store) but with 1 problem, for example “Organization: missing name”.
294 internal links, 22 external
The homepage links to 294 pages on naipo.ch and 22 external pages.
7 checks passed
Meta description: 86 characters
Your meta description is 86 characters: “NAIPO Massagegeräte & Massagesessel - Das original aus Hamburg mit neuster Technologie”.
One H1 headline
Your main headline reads: “NAIPO”.
Title: 46 characters
Your title is a healthy 46 characters: “NAIPO Massagesessel & Massagegeräte | Wellness”.
Canonical URL set
The canonical URL is https://naipo.ch/.
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://naipo.ch/sitemap.xml.
AI search readiness
No llms.txt
There is no https://naipo.ch/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.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,267 words), so crawlers that don't run JavaScript still read it.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
8 small tap targets
8 of 13 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.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))”.
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 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 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 602 words of copy
The homepage carries about 602 words of visible text.
8 checks passed
1 call to action
The homepage has 1 call to action, for example “Download on the App Store”.
7 short forms
7 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 12 customer or partner logos, a star rating and 14 trust badges.
Analytics in place
Analytics detected: Meta Pixel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 4 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
21 other companies contacted
Loading the homepage contacts 21 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 naipo.ch, 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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Adcell Tracking Remarketing · Opinew Reviews · Simprosys Google Shopping Feed · Avada Cookie Bar · Pdf Invoice Customizer · Avada Faqs · Cowlendar · Push Service · gtranslate.io · trustpilot.com · splitit.com · goaffpro.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
- E-commerce
- Shopify
- Hosting
- Shopify
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 naipo.ch, including 15 speed issues, 1 SEO issue and 1 conversion gap. 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.