Website review, no card needed
venderbys.dk website review
Visit site (opens in a new tab)Reviewed 20 November 202645 issues · 92 checks
This review found 45 issues worth fixing on venderbys.dk, 15 of them high impact, across 92 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
71C- #97,203 of 120,386 reviewed websitesbeats 17%
- #59,777 of 68,161 online storesbeats 10%
- #55,556 of 62,115 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.7 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 231 ms |
| Jun 6, 2026 | 248 ms |
| Jun 13, 2026 | 254 ms |
| Jun 20, 2026 | 258 ms |
| Jun 27, 2026 | 255 ms |
| Jul 4, 2026 | 264 ms |
| Jul 11, 2026 | 238 ms |
| Jul 18, 2026 | 587 ms |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 308 ms |
| Aug 22, 2026 | 277 ms |
| Aug 29, 2026 | 290 ms |
| Sep 5, 2026 | 371 ms |
| Sep 12, 2026 | 417 ms |
| Sep 19, 2026 | 511 ms |
| Sep 26, 2026 | 550 ms |
| Oct 3, 2026 | 417 ms |
| Oct 10, 2026 | 337 ms |
| Oct 17, 2026 | 305 ms |
| Oct 24, 2026 | 283 ms |
| Oct 31, 2026 | 304 ms |
| Nov 7, 2026 | 319 ms |
| Nov 14, 2026 | 304 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
Render-blocking requests
1.3 s24 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,408 HTML elements
The page has 7,408 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 3.5 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, Klaviyo and Clarity and others), adding 1.3 MB and 1.0 s of main-thread time.
Reduce unused JavaScript
280 ms · 334 KiBAbout 334 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 280 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 309 ms. During a long task the page ignores taps.
Google Tag Manager adds 267 ms
267 msGoogle Tag Manager costs a phone 267 ms of main-thread work and 185 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.
azurefd.net adds 128 ms
128 msazurefd.net costs a phone 128 ms of main-thread work and 323 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.
Shopify adds 70 ms
70 msShopify costs a phone 70 ms of main-thread work and 371 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.
Use efficient cache lifetimes
112 KiB13 files are served with short cache lifetimes, so returning visitors download them again (112 KiB).
Improve image delivery
88 KiB5 images could be 88 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
50 KiBPolyfills for old browsers add 50 KiB JavaScript that modern phones do not need.
Reduce unused CSS
14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
13 KiB13 KiB could be saved by minifying JavaScript.
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: 79 ms
79 msYour server sent the HTML in 79 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.
Cumulative Layout Shift: 0.583
0.583The layout shifts by 0.583 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 13.3 s
13.3 sThe page becomes fully interactive after 13.3 s. Good is under 3.8 s.
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
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: 254 ms
254 msReal visitors wait 254 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 231 ms to 304 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 81% slower for real visitors
+81%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 497 ms
497 msScripts block taps and scrolling for 497 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
2 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user TTFB: 544 ms
544 msReal visitors wait 544 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.7 MB in 528 requests
4.7 MBYour homepage downloads 4.7 MB in 528 requests on a phone: other files 1.7 MB (304), images 1.3 MB (43) and scripts 1.2 MB (122). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
11 KiB3 images are downloaded at several times the size a phone draws them, for example 019EA7B5-FFB9-4FFC-BA33-B02CA8AF1341.jpg at 500 px wide, shown at 163 px. Resized copies would save about 11 KiB.
About 1.3 g of CO₂ per visit
1.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.34 g of CO₂e: 161.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
29 buttons without a name
29 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
57 links without text
57 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.
ARIA role should be appropriate for the element (8 elements)
ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 80 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 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
46 internal links, 4 external
The homepage links to 46 pages on venderbys.dk and 4 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Hos VENDERBY's finder du moderne tøj til kvinder der vil følge de nyeste trends. Du får 1-3 dages levering i Danmark, 3…”.
Title: 54 characters
Your title is a healthy 54 characters: “Modetøj og accessories til kvinder online | VENDERBY'S”.
Canonical URL set
The canonical URL is https://venderbys.dk/.
Structured data in place
Structured data found: OnlineStore, 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://venderbys.dk/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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,132 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://venderbys.dk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://venderbys.dk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://venderbys.dk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages without a meta description
https://venderbys.dk/customer_authentication/redirect, https://venderbys.dk/collections/all, https://venderbys.dk/collections/going-out-season, https://venderbys.dk/collections/strik-og-loungewear and https://venderbys.dk/collections/most-popular-1 have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://venderbys.dk/customer_authentication/redirect, https://venderbys.dk/collections/all, https://venderbys.dk/collections/swimwear, https://venderbys.dk/collections/pants, https://venderbys.dk/collections/going-out-season and https://venderbys.dk/collections/nederdele and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://venderbys.dk/collections/pants took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
3 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.
Best practices
44 small tap targets
44 of 82 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 673 words of copy
The homepage carries about 673 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now” and “SHOP NOW”.
2 calls to action
The homepage has 2 calls to action, for example “SHOP” and “SHOP NOW”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 1 of them by other companies (measured from a US location before any click).
38 other companies contacted
Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 venderbys.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Microsoft Clarity · Swish · Klaviyo Email Marketing Sms · Triplewhale · Returnflows · T Lab Ai Translate · Orbe Geolocation · Aftersell · Hidepay · trustedshops.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
- 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 45 issues on venderbys.dk, including 22 speed issues, 1 SEO issue 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.