Website review, no card needed

lule.dk logo

lule.dk website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 77 checks

This review found 32 issues worth fixing on lule.dk, 11 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. 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

Full-page screenshot of lule.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lule.dk at 0.9 s0.9 s
  2. lule.dk at 1.8 s1.8 s
  3. lule.dk at 2.7 s2.7 s
  4. lule.dk at 3.5 s3.5 s
  5. lule.dk at 4.4 s4.4 s
  6. lule.dk at 5.3 s5.3 s
  7. lule.dk at 6.2 s6.2 s
  8. lule.dk at 7.1 s7.1 s

Speed

9 to fix62
  • Reduce unused JavaScript

    2.3 s · 537 KiB

    About 537 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Use efficient cache lifetimes

    1.2 s · 412 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (rebuyengine.com, Shopify and Judge.me and others), adding 19.7 MB and 505 ms of main-thread time.

  • Shopify adds 99 ms

    99 ms

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    550 ms · 229 KiB

    15 images could be 229 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

  • Main-thread work: 3.8 s

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

  • rebuyengine.com adds 150 ms

    150 ms

    rebuyengine.com costs a phone 150 ms of main-thread work and 710 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.

  • 2,075 HTML elements

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

  • Legacy JavaScript

    200 ms · 70 KiB

    Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • Render-blocking requests

    250 ms

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

  • 10 long tasks on the main thread

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

  • Reduce unused CSS

    65 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

5 to fix64
  • Largest Contentful Paint: 19.2 s

    19.2 s

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

  • Time to Interactive: 22.3 s

    22.3 s

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

  • Speed Index: 8.4 s

    8.4 s

    Visually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.

  • 36 images without width and height

    36 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 190 ms

    190 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix63
  • Page weight: 23.1 MB in 364 requests

    23.1 MB

    Your homepage downloads 23.1 MB in 364 requests on a phone: media 17.8 MB (1), images 2.1 MB (65) and scripts 1.6 MB (87). Under 2 MB keeps phones on slow connections fast.

  • 14 images below the first screen load straight away

    14 images further down the page (352 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.55 g

    By the Sustainable Web Design model, a visit to your homepage emits about 6.55 g of CO₂e: 785.4 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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8391
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 7 text elements with low contrast

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

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

  • 4 links without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 9279
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (78 characters)

    Your title is 78 characters, so Google will cut it off around 60: “Heart of Lule, stilfuldt og lækkert træningstøj til kvinder – Heart of Lule DK”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 87 internal links, 10 external

    The homepage links to 87 pages on lule.dk and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Heart of Lule DK”.

  • Canonical URL set

    The canonical URL is https://lule.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://lule.dk/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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 (791 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://lule.dk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://lule.dk/pages/contact has 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 35 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.

  • Every page has a meta description

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

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    42 of 51 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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 571 words of copy

    The homepage carries about 571 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”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “SHOP” and “Shop now”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 62 testimonial or review blocks and a star rating.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 28 cookies set on arrival

    28

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

  • 37 other companies contacted

    Loading the homepage contacts 37 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 lule.dk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on lule.dk, including 14 speed issues, 3 SEO issues and 2 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