Website review, no card needed
nikis-wohnen.ch website review
Visit site (opens in a new tab)Reviewed 11 November 202632 issues · 81 checks
This review found 32 issues worth fixing on nikis-wohnen.ch, 15 of them high impact, across 81 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
77C- #68,824 of 123,940 reviewed websitesbeats 39%
- #44,546 of 69,726 online storesbeats 31%
- #1,097 of 2,897 WooCommerce storesbeats 57%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.5 s |
| Jun 13, 2026 | 4.5 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.3 s |
| Oct 31, 2026 | 3.2 s |
| Nov 7, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 95 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 90 ms |
| Aug 8, 2026 | 91 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 96 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 97 ms |
| Oct 31, 2026 | 96 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
How it loaded on a phone
1.7 s
3.4 s
5.1 s
6.9 s
8.6 s
10.3 s
12.0 s
13.7 s
Speed
Reduce unused JavaScript
3.1 s · 577 KiBAbout 577 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Use efficient cache lifetimes
1.2 s · 326 KiB7 files are served with short cache lifetimes, so returning visitors download them again (326 KiB).
Render-blocking requests
1.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Font display
1.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.0 s).
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.1 MB and 529 ms of main-thread time.
Improve image delivery
150 ms · 457 KiB8 images could be 457 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 346 ms
346 msGoogle Tag Manager costs a phone 346 ms of main-thread work and 767 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.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 123 ms. During a long task the page ignores taps.
Reduce unused CSS
61 KiBAbout 61 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
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: 228 ms
228 msYour server sent the HTML in 228 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (7.2 s).
Speed Index: 17.0 s
17.0 sVisually, the page fills in at 17.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.5 s
17.5 sThe page becomes fully interactive after 17.5 s. Good is under 3.8 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 95 ms to 96 ms 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.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 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.
Largest content (LCP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 4.5 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 79 ms
79 msScripts block the page for only 79 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 82 requests
3.2 MBYour homepage downloads 3.2 MB in 82 requests on a phone: images 1.5 MB (20), scripts 1.4 MB (47) and fonts 120 KiB (7). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (689 KiB) are 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.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.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 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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 1 more 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.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
349 internal links, 2 external
The homepage links to 349 pages on nikis-wohnen.ch and 2 external pages.
6 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Niki's Wohnwelt in Chur bietet ein grosses Sortiment an Möbel, Textilien und Accessoires für Haus und Garten. Jetzt onl…”.
Title: 56 characters
Your title is a healthy 56 characters: “Niki's Wohnwelt in Chur - Das lokale Möbelhaus für dich!”.
Canonical URL set
The canonical URL is https://www.nikis-wohnen.ch/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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.nikis-wohnen.ch/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.nikis-wohnen.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: 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 (824 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a meta description
https://www.nikis-wohnen.ch/accessoires, https://www.nikis-wohnen.ch/accessoires/haushalt, https://www.nikis-wohnen.ch/accessoires/kueche-essen, https://www.nikis-wohnen.ch/accessoires/kueche-essen/pfannen-toepfe, https://www.nikis-wohnen.ch/accessoires/kueche-essen/tischwaesche-set and https://www.nikis-wohnen.ch/accessoires/kueche-essen/kueche-diverses and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages slow to respond
https://www.nikis-wohnen.ch/accessoires, https://www.nikis-wohnen.ch/accessoires/haushalt, https://www.nikis-wohnen.ch/accessoires/kueche-essen, https://www.nikis-wohnen.ch/accessoires/kueche-essen/pfannen-toepfe, https://www.nikis-wohnen.ch/accessoires/kueche-essen/tischwaesche-set and https://www.nikis-wohnen.ch/accessoires/kueche-essen/kueche-diverses and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 166 found) and read each the way a search engine does.
6 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
32 of 35 tappable elements near the top are at least 24 px.
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 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 401 words of copy
The homepage carries about 401 words of visible text.
2 checks passed
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel (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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 2 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.
9 other companies contacted
Loading the homepage contacts 9 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 nikis-wohnen.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- hosttech GmbH
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on nikis-wohnen.ch, including 13 speed issues, 3 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.