Website review, no card needed

louispoulsen.com logo

louispoulsen.com website review

Visit site (opens in a new tab)Reviewed 4 November 202631 issues · 75 checks

This review found 31 issues worth fixing on louispoulsen.com, 11 of them high impact, across 75 checks. The most urgent: 47,454 HTML elements. 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

Real-visitor load time (LCP)75th percentile, phones
10.7 s1.4 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.7 s
May 23, 20264.8 s
May 30, 20264.8 s
Jun 6, 20265.5 s
Jun 13, 20269.6 s
Jun 20, 20269.0 s
Jun 27, 20268.9 s
Jul 4, 20268.9 s
Jul 11, 20267.2 s
Jul 18, 20265.7 s
Jul 25, 20265.0 s
Aug 1, 20264.9 s
Aug 8, 20264.8 s
Aug 15, 20264.8 s
Aug 22, 20264.8 s
Aug 29, 20264.8 s
Sep 5, 20264.7 s
Sep 12, 20264.7 s
Sep 19, 20264.6 s
Sep 26, 20264.6 s
Oct 3, 20264.6 s
Oct 10, 20264.3 s
Oct 17, 20263.7 s
Oct 24, 20263.0 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
1.0 s127 msMay 16Oct 31312 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026233 ms
May 23, 2026241 ms
May 30, 2026247 ms
Jun 6, 2026301 ms
Jun 13, 2026938 ms
Jun 20, 2026880 ms
Jun 27, 2026862 ms
Jul 4, 2026860 ms
Jul 11, 2026683 ms
Jul 18, 2026434 ms
Jul 25, 2026271 ms
Aug 1, 2026265 ms
Aug 8, 2026270 ms
Aug 15, 2026280 ms
Aug 22, 2026287 ms
Aug 29, 2026292 ms
Sep 5, 2026297 ms
Sep 12, 2026297 ms
Sep 19, 2026297 ms
Sep 26, 2026296 ms
Oct 3, 2026294 ms
Oct 10, 2026291 ms
Oct 17, 2026289 ms
Oct 24, 2026298 ms
Oct 31, 2026312 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

Full-page screenshot of louispoulsen.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. louispoulsen.com at 0.5 s0.5 s
  2. louispoulsen.com at 1.1 s1.1 s
  3. louispoulsen.com at 1.6 s1.6 s
  4. louispoulsen.com at 2.1 s2.1 s
  5. louispoulsen.com at 2.7 s2.7 s
  6. louispoulsen.com at 3.2 s3.2 s
  7. louispoulsen.com at 3.7 s3.7 s
  8. louispoulsen.com at 4.3 s4.3 s

Speed

12 to fix39
  • 47,454 HTML elements

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

  • Render-blocking requests

    1.8 s

    44 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Reduce unused JavaScript

    1.1 s · 615 KiB

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

  • Mobile performance score: 39

    39/100

    Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.6 s

    A phone's processor spends 6.6 s on main-thread work while loading, 3.7 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, Cookiebot and getflowbox.com and others), adding 1.6 MB and 1.3 s of main-thread time.

  • 13 long tasks on the main thread

    13 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    650 ms · 331 KiB

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

  • Google Tag Manager adds 692 ms

    692 ms

    Google Tag Manager costs a phone 692 ms of main-thread work and 678 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.

  • Improve image delivery

    733 KiB

    7 images could be 733 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Cookiebot adds 436 ms

    436 ms

    Cookiebot costs a phone 436 ms of main-thread work and 456 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.

  • getflowbox.com adds 138 ms

    138 ms

    getflowbox.com costs a phone 138 ms of main-thread work and 423 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.

  • Legacy JavaScript

    250 ms · 14 KiB

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

  • Reduce unused CSS

    27 KiB

    About 27 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.

1 checks passed
  • Server response: 279 ms

    279 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 13.3 s

    13.3 s

    Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our 1089 partners process your personal data, e.g. y…”.

  • Time to Interactive: 21.2 s

    21.2 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

    Scripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 9.0 s

    9.0 s

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

  • Tap response (INP) got 29% slower for real visitors

    +29%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 233 ms to 312 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 6 images without width and height

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

9 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: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 148 ms

    148 ms

    Real visitors wait 148 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 650 ms

    650 ms

    Real visitors wait 650 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 42% faster for real visitors

    -42%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.7 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix67
  • Page weight: 3.7 MB in 145 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 145 requests on a phone: scripts 1.9 MB (49), images 1.1 MB (28) and media 321 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.06 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 126.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

2 to fixGoogle 9998
  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • 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.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 107 internal links, 5 external

    The homepage links to 107 pages on louispoulsen.com and 5 external pages.

6 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Explore modern and timeless lamps from Louis Poulsen. Discover inspiring designs that enhance your living spaces with q…”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “Designer Lamps | Modern & Timeless Lamps”.

  • Canonical URL set

    The canonical URL is https://www.louispoulsen.com/en-us.

  • 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.louispoulsen.com/sitemapindex.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.

  • No llms.txt

    There is no https://www.louispoulsen.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (398 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without a meta description

    https://www.louispoulsen.com/en-us/c and https://www.louispoulsen.com/en-us/c/indoor-lighting/portable-lamps/vl-45-radiohus-portable-lamp-gaskil-us 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 49 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

2 to fixGoogle 9687
  • 24 small tap targets

    24 of 50 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was 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.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 577 words of copy

    The homepage carries about 577 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign up for trade”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Sign up for trade”, “Sign up now” and “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 7 other companies contacted

    Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 louispoulsen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Vercel

Company

Founded
1874
Headquarters
Copenhagen

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on louispoulsen.com, including 18 speed issues, 3 SEO issues and 3 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