Website review, no card needed
snuskompagniet.com website review
Visit site (opens in a new tab)Reviewed 13 November 202625 issues · 76 checks
This review found 25 issues worth fixing on snuskompagniet.com, 9 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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
85B- #14,776 of 107,969 reviewed websitesbeats 82%
- #9,411 of 61,160 online storesbeats 79%
- #9,154 of 55,794 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 734 ms |
| May 30, 2026 | 716 ms |
| Jun 6, 2026 | 672 ms |
| Jun 13, 2026 | 628 ms |
| Jun 20, 2026 | 587 ms |
| Jun 27, 2026 | 607 ms |
| Jul 4, 2026 | 640 ms |
| Jul 11, 2026 | 654 ms |
| Jul 18, 2026 | 708 ms |
| Jul 25, 2026 | 720 ms |
| Aug 1, 2026 | 701 ms |
| Aug 8, 2026 | 738 ms |
| Aug 15, 2026 | 723 ms |
| Aug 22, 2026 | 730 ms |
| Aug 29, 2026 | 737 ms |
| Sep 5, 2026 | 711 ms |
| Sep 12, 2026 | 701 ms |
| Sep 19, 2026 | 689 ms |
| Sep 26, 2026 | 694 ms |
| Oct 3, 2026 | 636 ms |
| Oct 10, 2026 | 612 ms |
| Oct 17, 2026 | 602 ms |
| Oct 24, 2026 | 590 ms |
| Oct 31, 2026 | 609 ms |
| Nov 7, 2026 | 639 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 70 ms |
| May 30, 2026 | 70 ms |
| Jun 6, 2026 | 70 ms |
| Jun 13, 2026 | 69 ms |
| Jun 20, 2026 | 69 ms |
| Jun 27, 2026 | 71 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 80 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 77 ms |
| Aug 8, 2026 | 71 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 70 ms |
| Aug 29, 2026 | 70 ms |
| Sep 5, 2026 | 70 ms |
| Sep 12, 2026 | 70 ms |
| Sep 19, 2026 | 70 ms |
| Sep 26, 2026 | 71 ms |
| Oct 3, 2026 | 71 ms |
| Oct 10, 2026 | 72 ms |
| Oct 17, 2026 | 71 ms |
| Oct 24, 2026 | 71 ms |
| Oct 31, 2026 | 70 ms |
| Nov 7, 2026 | 70 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.1 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Improve image delivery
317 KiB11 images could be 317 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
6 third-party services on the page
6 third-party services load with your homepage (jQuery CDN, Shopify and Bootstrap CDN and others), adding 225 KiB and 41 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
34 KiBAbout 34 KiB of CSS is downloaded but never applied on this page.
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.
Use efficient cache lifetimes
4 KiB2 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).
3 checks passed
Mobile performance score: 91
91/100Your mobile performance score is 91. That is in Google's “good” band (90 and up).
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 209 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 70 ms to 70 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 71 ms
71 msReal visitors wait 71 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 278 ms
278 msReal visitors wait 278 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “At Snuskompagniet, we specialize in both tobacco snus and n…”.
Time to Interactive: 2.3 s
2.3 sThe page is fully interactive after 2.3 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
9 images in older formats
9 images (2.1 MB) 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.
10 images below the first screen load straight away
10 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.8 MB in 138 requests
1.8 MBYour homepage downloads 1.8 MB in 138 requests on a phone: other files 659 KiB (63), images 602 KiB (24) and fonts 259 KiB (6). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
14 images without alt text
14 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 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.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (85 characters)
Your title is 85 characters, so Google will cut it off around 60: “Buy cheap tobacco snus & nicotine pouches online at great prices – Snuskompagniet.com”.
174 internal links, 0 external
The homepage links to 174 pages on snuskompagniet.com and 0 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://snuskompagniet.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.
XML sitemap found
Your XML sitemap is reachable at https://snuskompagniet.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (638 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://snuskompagniet.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://snuskompagniet.com/collections/all, https://snuskompagniet.com/collections/77, https://snuskompagniet.com/collections/apres, https://snuskompagniet.com/collections/catch, https://snuskompagniet.com/collections/ettan and https://snuskompagniet.com/collections/fix and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 82 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'checked')”.
2 checks passed
Tap targets are thumb-sized
25 of 26 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 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 431 words of copy
The homepage carries about 431 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (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 snuskompagniet.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- jQuery
- 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 25 issues on snuskompagniet.com, including 5 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.