Website review, no card needed

nivocase.de logo

nivocase.de website review

Visit site (opens in a new tab)Reviewed 23 October 202628 issues · 79 checks

This review found 28 issues worth fixing on nivocase.de, 7 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.4 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.9 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.7 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
90 ms77 msMay 2Oct 1787 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202679 ms
May 9, 202678 ms
May 16, 202678 ms
May 23, 202678 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202680 ms
Jul 11, 202682 ms
Jul 18, 202683 ms
Jul 25, 202684 ms
Aug 1, 202684 ms
Aug 8, 202685 ms
Aug 15, 202686 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202688 ms
Sep 26, 202687 ms
Oct 3, 202688 ms
Oct 10, 202687 ms
Oct 17, 202687 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

Full-page screenshot of nivocase.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nivocase.de at 0.4 s0.4 s
  2. nivocase.de at 0.9 s0.9 s
  3. nivocase.de at 1.3 s1.3 s
  4. nivocase.de at 1.8 s1.8 s
  5. nivocase.de at 2.2 s2.2 s
  6. nivocase.de at 2.7 s2.7 s
  7. nivocase.de at 3.1 s3.1 s
  8. nivocase.de at 3.6 s3.6 s

Speed

5 to fix72
  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    800 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 800 ms.

  • Use efficient cache lifetimes

    600 ms · 191 KiB

    18 files are served with short cache lifetimes, so returning visitors download them again (191 KiB).

  • 3 third-party services on the page

    3 third-party services load with your homepage (Usercentrics CMP, Adobe Experience Cloud and nivocase.com), adding 2.2 MB and 94 ms of main-thread time.

  • nivocase.com adds 0 ms

    0 ms

    nivocase.com costs a phone 0 ms of main-thread work and 2.0 MB 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.

  • Reduce unused JavaScript

    250 ms · 226 KiB

    About 226 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 250 ms faster on a phone.

  • Improve image delivery

    114 KiB

    2 images could be 114 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 80 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 447 ms of it running JavaScript. That is comfortably low.

  • Server response: 110 ms

    110 ms

    Your server sent the HTML in 110 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • 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: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Real-user TTFB: 896 ms

    896 ms

    Real visitors wait 896 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 5.3 s

    5.3 s

    Visually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.

  • Cumulative Layout Shift: 0.202

    0.202

    The layout shifts by 0.202 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 5.9 s

    5.9 s

    The page becomes fully interactive after 5.9 s. Good is under 3.8 s.

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 11% slower for real visitors

    +11%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 79 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 15% slower for real visitors

    +15%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 15 ms

    15 ms

    Scripts block the page for only 15 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 97 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 97 requests on a phone: images 2.9 MB (56), scripts 442 KiB (16) and fonts 53 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.00 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 119.7 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

5 to fixGoogle 9193
  • 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.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 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.

  • 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.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

2 checks passed
  • Every image has alt text

    All 55 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • Structured data has 3 problems

    Structured data found (Brand, Organization, WebPage and WebSite) but with 3 problems, for example “Organization: url is not an absolute URL ("www.nivocase.de")”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 123 internal links, 0 external

    The homepage links to 123 pages on nivocase.de and 0 external pages.

7 checks passed
  • Meta description: 115 characters

    Your meta description is 115 characters: “NIVOCASE by DeinDesign bietet zuverlässigen Schutz für dein Smartphone – mit individuellem Design. Jetzt entdecken.”.

  • One H1 headline

    Your main headline reads: “Uniquely Protected”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “DeinDesign wird NIVOCASE – Smartphone Schutz & Design”.

  • Canonical URL set

    The canonical URL is https://www.nivocase.de/de.

  • 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://www.nivocase.de/sitemap.xml.

AI search readiness

100
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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (499 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.nivocase.de/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85
  • 1 page without a meta description

    https://www.nivocase.de/de/warenkorb has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.nivocase.de/de/produktdetails/gurtband-deep-blue, whose canonical is https://www.nivocase.de/de/produktdetails/urban-strap-bold-black. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.nivocase.de/de/warenkorb 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 67 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 7 small tap targets

    7 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Missing source maps

    Large scripts ship without source maps.

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

5 to fix33
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 353 words of copy

    The homepage carries about 353 words of visible text.

1 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 6 other companies contacted

    Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) loads with the page.

  • 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 nivocase.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on nivocase.de, including 12 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25