Website review, no card needed

niococktails.de logo

niococktails.de website review

Visit site (opens in a new tab)Reviewed 10 November 202633 issues · 80 checks

This review found 33 issues worth fixing on niococktails.de, 7 of them high impact, across 80 checks. The most urgent: avoid multiple page redirects. 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

Full-page screenshot of niococktails.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. niococktails.de at 2.6 s2.6 s
  2. niococktails.de at 5.2 s5.2 s
  3. niococktails.de at 7.9 s7.9 s
  4. niococktails.de at 10.5 s10.5 s
  5. niococktails.de at 13.1 s13.1 s
  6. niococktails.de at 15.7 s15.7 s
  7. niococktails.de at 18.4 s18.4 s
  8. niococktails.de at 21.0 s21.0 s

Speed

12 to fix56
  • Avoid multiple page redirects

    3.3 s

    The page goes through 2 redirects before it starts loading, costing about 3.3 s. Link and advertise the final URL directly.

  • Main-thread work: 4.3 s

    A phone's processor spends 4.3 s on main-thread work while loading, 2.0 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 (Google Tag Manager, Freshchat and Clarity and others), adding 5.5 MB and 1.4 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    800 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • Google Tag Manager adds 377 ms

    377 ms

    Google Tag Manager costs a phone 377 ms of main-thread work and 539 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.

  • Freshchat adds 304 ms

    304 ms

    Freshchat costs a phone 304 ms of main-thread work and 787 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.

  • niococktails.co.uk adds 144 ms

    144 ms

    niococktails.co.uk costs a phone 144 ms of main-thread work and 1.9 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.

  • commslayer.com adds 122 ms

    122 ms

    commslayer.com costs a phone 122 ms of main-thread work and 1.3 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.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 255 ms. During a long task the page ignores taps.

  • Shopify adds 85 ms

    85 ms

    Shopify costs a phone 85 ms of main-thread work and 389 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.

  • Reduce unused CSS

    150 ms · 155 KiB

    About 155 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.

  • Use efficient cache lifetimes

    50 ms · 176 KiB

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

  • Document request latency

    200 ms

    The HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    55 KiB

    Polyfills for old browsers add 55 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    29 KiB

    29 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 JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 37 ms

    37 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 31.0 s

    31.0 s

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

  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Eine Nachricht an die Kunden von NIO Deutschland”.

  • Speed Index: 6.1 s

    6.1 s

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

  • Total Blocking Time: 499 ms

    499 ms

    Scripts block taps and scrolling for 499 ms in total while the page loads. Good is under 200 ms.

  • 9 images without width and height

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

8 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: 1.1 s

    1.1 s

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

  • Real-user INP: 167 ms

    167 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 315 ms

    315 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 6.0 MB in 530 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 530 requests on a phone: scripts 3.3 MB (149), other files 1.5 MB (285) and fonts 525 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    51 KiB

    1 image is downloaded at several times the size a phone draws it, for example MAIN_CHRISTMAR_BOX_6_2000_X_200.jpg at 390 px wide, shown at 12 px. Resized copies would save about 51 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (89 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.70 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 203.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9296
  • 9 images without alt text

    9 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

  • 15 links without text

    15 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8578
  • Title is long (81 characters)

    Your title is 81 characters, so Google will cut it off around 60: “Premium Ready Made Cocktails | 24hr Delivery | NIO Cocktails – NIO Cocktails (UK)”.

  • Canonical points to another host

    Your canonical URL points to niococktails.co.uk, not niococktails.de, so Google may credit that host instead.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (161 characters)

    Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 277 internal links, 15 external

    The homepage links to 277 pages on niococktails.de and 15 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “We are ready-to-sip premium cocktails premixed in Italy with carefully selected spirits and ingredients.”.

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://niococktails.de/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.

2 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,716 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9687
  • 27 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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.

  • Only about 163 words

    The homepage has only about 163 words of visible text; thin pages give Google and first-time buyers little to go on.

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Must Try - 30% OFF”, “Track my order” and “Contact Us”.

  • 25 short forms

    25 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 60 testimonial or review blocks, 4 customer or partner logos, a star rating and 27 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and TikTok Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Microsoft Ads 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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 4 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.

  • 34 other companies contacted

    Loading the homepage contacts 34 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 niococktails.de, 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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Sc Easy Redirects · Leaf Signal Nio Cocktails Uk · Beans Id Verification · Microsoft Clarity · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · trustpilot.com · webgains.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
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on niococktails.de, including 17 speed issues, 5 SEO issues 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

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