Website review, no card needed

gigasnus.de logo

gigasnus.de website review

Visit site (opens in a new tab)Reviewed 6 November 202626 issues · 81 checks

This review found 26 issues worth fixing on gigasnus.de, 7 of them high impact, across 81 checks. The most urgent: main-thread work: 4.4 s. 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
1.0 s881 msMay 16Oct 31900 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026986 ms
May 23, 2026990 ms
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 2026966 ms
Jun 20, 2026951 ms
Jun 27, 2026940 ms
Jul 4, 2026951 ms
Jul 11, 2026973 ms
Jul 18, 2026972 ms
Jul 25, 2026952 ms
Aug 1, 2026937 ms
Aug 8, 2026959 ms
Aug 15, 2026947 ms
Aug 22, 2026954 ms
Aug 29, 2026972 ms
Sep 5, 2026967 ms
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 2026995 ms
Oct 3, 2026947 ms
Oct 10, 2026905 ms
Oct 17, 2026909 ms
Oct 24, 2026908 ms
Oct 31, 2026900 ms
Real-visitor tap response (INP)75th percentile, phones
103 ms84 msMay 16Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202686 ms
May 23, 202689 ms
May 30, 202690 ms
Jun 6, 202692 ms
Jun 13, 202694 ms
Jun 20, 202694 ms
Jun 27, 202695 ms
Jul 4, 202696 ms
Jul 11, 202695 ms
Jul 18, 202696 ms
Jul 25, 202694 ms
Aug 1, 202696 ms
Aug 8, 202697 ms
Aug 15, 202695 ms
Aug 22, 202696 ms
Aug 29, 202695 ms
Sep 5, 202696 ms
Sep 12, 202697 ms
Sep 19, 202697 ms
Sep 26, 2026101 ms
Oct 3, 202699 ms
Oct 10, 202699 ms
Oct 17, 2026100 ms
Oct 24, 202699 ms
Oct 31, 202696 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 gigasnus.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gigasnus.de at 0.8 s0.8 s
  2. gigasnus.de at 1.5 s1.5 s
  3. gigasnus.de at 2.3 s2.3 s
  4. gigasnus.de at 3.0 s3.0 s
  5. gigasnus.de at 3.8 s3.8 s
  6. gigasnus.de at 4.6 s4.6 s
  7. gigasnus.de at 5.3 s5.3 s
  8. gigasnus.de at 6.1 s6.1 s

Speed

5 to fix90
  • Main-thread work: 4.4 s

    A phone's processor spends 4.4 s on main-thread work while loading, 662 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 4,051 HTML elements

    The page has 4,051 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Render-blocking requests

    500 ms

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

  • Reduce unused JavaScript

    273 KiB

    About 273 KiB of JavaScript is downloaded but never used on this page.

  • Shopify adds 108 ms

    108 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, Cloudflare CDN and shop.app and others), adding 609 KiB and 150 ms of main-thread time.

  • Improve image delivery

    119 KiB

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

  • 6 long tasks on the main thread

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

  • Duplicated JavaScript

    48 KiB

    48 KiB JavaScript is shipped twice across bundles.

  • Reduce unused CSS

    25 KiB

    About 25 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    15 KiB

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

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

2 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90. That is in Google's “good” band (90 and up).

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 3.4 s

    3.4 s

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

  • Time to Interactive: 5.0 s

    5.0 s

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

  • 1 image without width and height

    1 image 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-31, real Chrome visitors' tap response (inp) went from 86 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -9%

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

10 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.3 s

    1.3 s

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

  • Real-user INP: 103 ms

    103 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 571 ms

    571 ms

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

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.071

    0.071

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

  • Total Blocking Time: 72 ms

    72 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

3 to fix69
  • Page weight: 2.7 MB in 308 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 308 requests on a phone: images 1.1 MB (83), other files 775 KiB (86) and scripts 500 KiB (110). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    2659_984-1.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).

  • 1 image far larger than shown

    18 KiB

    1 image is downloaded at several times the size a phone draws it, for example VELO-Freezing-Peppermint.webp at 300 px wide, shown at 91 px. Resized copies would save about 18 KiB.

  • 5 images in older formats

    5 images (344 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.8 g of CO₂ per visit

    0.76 g

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

Accessibility

5 to fixGoogle 9494
  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

  • 82 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 218 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 361 internal links, 1 external

    The homepage links to 361 pages on gigasnus.de and 1 external page.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Gigasnus.de – Dein Shop für Nikotinbeutel in Deutschland ab 1,50 € ✓ Top Marken ✓ schneller Versand ✓ Versandfrei ab 45…”.

  • One H1 headline

    Your main headline reads: “Deine Nikotinbeutel online kaufen in Deutschland”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Nikotinbeutel online kaufen in Deutschland ab 1,50 €”.

  • Canonical URL set

    The canonical URL is https://gigasnus.de/.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://gigasnus.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,014 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 1 page slow to respond

    https://gigasnus.de/collections/getraenke-nikotinbeutel took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 7791
  • 13 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

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

4 to fix42
  • 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 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 1,424 words of copy

    The homepage carries about 1,424 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

2 checks passed
  • 6 short forms

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

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

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

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 gigasnus.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

3d Seasonal Effects · Inbox

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 26 issues on gigasnus.de, including 8 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

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