Website review, no card needed
ninepine.dk website review
Visit site (opens in a new tab)Reviewed 17 November 202644 issues · 88 checks
This review found 44 issues worth fixing on ninepine.dk, 17 of them high impact, across 88 checks. The most urgent: page weight: 23.0 MB in 571 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
67D- #104,542 of 116,295 reviewed websitesbeats 8%
- #63,158 of 66,755 online storesbeats 4%
- #58,174 of 60,924 Shopify storesbeats 4%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.3 s |
| Oct 31, 2026 | 3.4 s |
| Nov 7, 2026 | 3.3 s |
| Nov 14, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 190 ms |
| Jun 6, 2026 | 195 ms |
| Jun 13, 2026 | 278 ms |
| Jun 20, 2026 | 318 ms |
| Jun 27, 2026 | 320 ms |
| Jul 4, 2026 | 319 ms |
| Jul 11, 2026 | 252 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 213 ms |
| Aug 8, 2026 | 211 ms |
| Aug 15, 2026 | 228 ms |
| Aug 22, 2026 | 216 ms |
| Aug 29, 2026 | 223 ms |
| Sep 5, 2026 | 237 ms |
| Sep 12, 2026 | 246 ms |
| Sep 19, 2026 | 301 ms |
| Sep 26, 2026 | 365 ms |
| Oct 3, 2026 | 388 ms |
| Oct 10, 2026 | 416 ms |
| Oct 17, 2026 | 419 ms |
| Oct 24, 2026 | 411 ms |
| Oct 31, 2026 | 411 ms |
| Nov 7, 2026 | 370 ms |
| Nov 14, 2026 | 312 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.5 s
2.9 s
4.4 s
5.8 s
7.3 s
8.8 s
10.2 s
11.7 s
Speed
Improve image delivery
1.4 s · 231 KiB13 images could be 231 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Main-thread work: 14.0 s
A phone's processor spends 14.0 s on main-thread work while loading, 6.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,769 HTML elements
The page has 7,769 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and weglot.com and others), adding 3.3 MB and 2.1 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.3 MBAbout 1.3 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.
Render-blocking requests
950 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused CSS
600 ms · 116 KiBAbout 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 538 ms
538 msGoogle Tag Manager costs a phone 538 ms of main-thread work and 1.2 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.
Clarity adds 507 ms
507 msClarity costs a phone 507 ms of main-thread work and 30 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.
weglot.com adds 487 ms
487 msweglot.com costs a phone 487 ms of main-thread work and 80 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 351 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
257 KiB18 files are served with short cache lifetimes, so returning visitors download them again (257 KiB).
Shopify adds 130 ms
130 msShopify costs a phone 130 ms of main-thread work and 950 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.
Klaviyo adds 187 ms
187 msKlaviyo costs a phone 187 ms of main-thread work and 325 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.
Minify CSS
150 ms · 17 KiB17 KiB could be saved by minifying CSS.
Legacy JavaScript
46 KiBPolyfills for old browsers add 46 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: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.7 s
13.7 sYour largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 33.7 s
33.7 sThe page becomes fully interactive after 33.7 s. Good is under 3.8 s.
Speed Index: 12.5 s
12.5 sVisually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 743 ms
743 msScripts block taps and scrolling for 743 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 262 ms
262 msReal visitors wait 262 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 77% slower for real visitors
+77%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 190 ms to 312 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.0 MB in 571 requests
23.0 MBYour homepage downloads 23.0 MB in 571 requests on a phone: media 15.4 MB (2), scripts 3.0 MB (157) and images 2.3 MB (91). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
677 KiB6 images are downloaded at several times the size a phone draws them, for example Untitled_design_8.png at 2,048 px wide, shown at 36 px. Resized copies would save about 677 KiB.
7 images below the first screen load straight away
7 images further down the page (705 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.5 g of CO₂ per visit
6.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.52 g of CO₂e: 782.2 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
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
25 images without alt text
25 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate 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.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 4 mores 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.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: url points at a different host (https://www.ninepine.se)”.
395 internal links, 5 external
The homepage links to 395 pages on ninepine.dk and 5 external pages.
6 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Effortless sophistication meets comfort - we’re a Stockholm-based studio purveying versatile & meticulously designed pi…”.
Title: 32 characters
Your title is a healthy 32 characters: “Ninepine | The Luxury of Comfort”.
Canonical URL set
The canonical URL is https://www.ninepine.com/.
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.ninepine.com/sitemap.xml.
AI search readiness
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 description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,447 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ninepine.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages without an H1
https://www.ninepine.com/collections/all, https://www.ninepine.com/collections/bestsellers, https://www.ninepine.com/collections/aw26, https://www.ninepine.com/collections/new-arrivals, https://www.ninepine.com/collections/archivesale and https://www.ninepine.com/collections/asana-line-1 and 2 others have 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 125 found) and read each the way a search engine does.
6 checks passed
Linked pages load
8 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 8 pages that loaded have a meta description.
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 8 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught The container with id "ingrid-faq-widget" was not found!”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
30 of 36 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 672 words of copy
The homepage carries about 672 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
16 calls to action
The homepage has 16 calls to action, for example “SHOP”, “SHOP Show menu” and “SHOP ALL”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 customer or partner logos, a star rating and “Over 2.000 reviews”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.
32 cookies set on arrival
32Opening the homepage sets 32 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.
59 other companies contacted
Loading the homepage contacts 59 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 ninepine.dk, 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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Intelligems A B Testing · Blockify Fraud Filter · Klaviyo Email Marketing Sms · Microsoft Clarity · Triplewhale · Depict Search Merchandising · Rebuy Personalization Engine · Gorgias Live Chat Helpdesk · Okendo · Gdpr Cookie Consent · Region Restrictions · Countdown Timer · Delivery Timer · Orbe Geolocation · Gg Hover Slider · snapchat.com · weglot.com · rebuyengine.com · Swym Wishlist Plus
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 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 44 issues on ninepine.dk, including 27 speed issues, 2 SEO issues and 1 conversion gap. 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.