Website review, no card needed
bambuni.dk website review
Visit site (opens in a new tab)Reviewed 9 November 202638 issues · 74 checks
This review found 38 issues worth fixing on bambuni.dk, 18 of them high impact, across 74 checks. The most urgent: reduce unused JavaScript. 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
70C- #100,332 of 120,267 reviewed websitesbeats 14%
- #61,201 of 68,107 online storesbeats 8%
- #56,706 of 62,069 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 146 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 139 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 141 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 148 ms |
| Sep 5, 2026 | 149 ms |
| Sep 12, 2026 | 151 ms |
| Sep 19, 2026 | 153 ms |
| Sep 26, 2026 | 156 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 163 ms |
| Oct 31, 2026 | 169 ms |
| Nov 7, 2026 | 175 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
Speed
Reduce unused JavaScript
5.6 s · 1,022 KiBAbout 1,022 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.6 s faster on a phone.
Use efficient cache lifetimes
1.5 s · 299 KiB23 files are served with short cache lifetimes, so returning visitors download them again (299 KiB).
Minify JavaScript
1.0 s · 71 KiB71 KiB could be saved by minifying JavaScript.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.7 s
A phone's processor spends 5.7 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,898 HTML elements
The page has 3,898 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 (Shopify, Klaviyo and Clarity and others), adding 4.7 MB and 1.2 s of main-thread time.
Shopify adds 539 ms
539 msShopify costs a phone 539 ms of main-thread work and 3.6 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.
Render-blocking requests
700 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Legacy JavaScript
600 ms · 58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
300 ms · 63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Klaviyo adds 159 ms
159 msKlaviyo costs a phone 159 ms of main-thread work and 387 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 · 6 KiB6 KiB could be saved by minifying CSS.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 134 ms. During a long task the page ignores taps.
Duplicated JavaScript
50 ms · 8 KiB8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.
Improve image delivery
27 KiB5 images could be 27 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 80 ms
80 msYour server sent the HTML in 80 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.
Largest Contentful Paint: 21.9 s
21.9 sYour largest element takes 21.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vi og vores 1037 partnere bruger cookies og andre sporingst…”.
Time to Interactive: 25.6 s
25.6 sThe page becomes fully interactive after 25.6 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.18
0.18The layout shifts by 0.18 while loading, so content jumps under the reader's thumb. Good is under 0.1.
24 images without width and height
24 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 265 ms
265 msScripts block taps and scrolling for 265 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 146 ms to 175 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 478 ms
478 msReal visitors wait 478 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 6.5 MB in 403 requests
6.5 MBYour homepage downloads 6.5 MB in 403 requests on a phone: scripts 2.2 MB (138), media 2.0 MB (1) and other files 1.0 MB (150). Under 2 MB keeps phones on slow connections fast.
About 1.9 g of CO₂ per visit
1.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.85 g of CO₂e: 222.3 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
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 7 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
6 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Nyd blødt bambustøj om dagen og lækkert sengetøj om natten. Se det store udvalg, og køb med hurtig levering og 365 dage…”.
Title: 55 characters
Your title is a healthy 55 characters: “Bambuni Denmark | Stort udvalg af bambustøj og sengetøj”.
Canonical URL set
The canonical URL is https://bambuni.dk/.
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://bambuni.dk/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 1,211 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
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.
llms.txt published
The site publishes https://bambuni.dk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Best practices
3 broken images
3 images failed to load on a phone, for example https://bambuni.dk/.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
86 of 89 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 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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,211 words of copy
The homepage carries about 1,211 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
26 cookies set on arrival
26Opening the homepage sets 26 cookies (measured from a US location before any click).
64 other companies contacted
Loading the homepage contacts 64 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 bambuni.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 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Cookieyes Gdpr · Swatch King · Langshop · Essential Announcer · Sa Variants · Profitmetrics · Klaviyo Email Marketing Sms · Returnflows · Ecomposer Builder · Variant Image Swatch · Essential Announcement Bar · Mp Size Chart Size Guide · Sea Survey · Announcement Bar Maker By Apphero · Guarantees Features Icons · Countdown Timer · Quick Announcement Bar Prod · trustpilot.com · viaads.dk
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
- Vue.js
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on bambuni.dk, including 21 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.