Website review, no card needed

gabriel.dk logo

gabriel.dk website review

Visit site (opens in a new tab)Reviewed 1 November 202628 issues · 84 checks

This review found 28 issues worth fixing on gabriel.dk, 6 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
1.8 s1.1 sMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.4 s
May 30, 20261.3 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.4 s
Aug 8, 20261.3 s
Aug 15, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
144 ms93 msMay 16Oct 2499 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026138 ms
May 23, 2026131 ms
May 30, 2026124 ms
Jun 6, 2026114 ms
Jun 13, 2026114 ms
Jun 20, 2026102 ms
Jun 27, 2026102 ms
Jul 11, 2026113 ms
Jul 18, 2026126 ms
Jul 25, 2026119 ms
Aug 1, 2026119 ms
Aug 29, 2026134 ms
Sep 5, 2026114 ms
Sep 12, 2026112 ms
Sep 19, 2026112 ms
Sep 26, 2026114 ms
Oct 3, 2026115 ms
Oct 10, 2026104 ms
Oct 17, 2026101 ms
Oct 24, 202699 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 gabriel.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gabriel.dk at 0.4 s0.4 s
  2. gabriel.dk at 0.8 s0.8 s
  3. gabriel.dk at 1.1 s1.1 s
  4. gabriel.dk at 1.5 s1.5 s
  5. gabriel.dk at 1.9 s1.9 s
  6. gabriel.dk at 2.3 s2.3 s
  7. gabriel.dk at 2.6 s2.6 s
  8. gabriel.dk at 3.0 s3.0 s

Speed

7 to fix64
  • Use efficient cache lifetimes

    3.4 s · 775 KiB

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

  • Reduce unused JavaScript

    2.1 s · 426 KiB

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

  • Mobile performance score: 64

    64/100

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

  • Render-blocking requests

    500 ms

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

  • Font display

    450 ms

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

  • Reduce unused CSS

    310 ms · 76 KiB

    About 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.

  • 2,505 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Hotjar and cookieinformation.com and others), adding 298 KiB and 228 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 9 KiB

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

  • 6 long tasks on the main thread

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

  • Improve image delivery

    71 KiB

    4 images could be 71 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.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 416 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 11.2 s

    11.2 s

    Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our business partners use technologies, including co…”.

  • Time to Interactive: 11.2 s

    11.2 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • Cumulative Layout Shift: 0.143

    0.143

    The layout shifts by 0.143 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 1 image without width and height

    1 image 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: 1.4 s

    1.4 s

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

  • Real-user INP: 100 ms

    100 ms

    Real visitors wait 100 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 424 ms

    424 ms

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

  • Tap response (INP) got 26% faster for real visitors

    -26%

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

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

    -29%

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

  • Total Blocking Time: 78 ms

    78 ms

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.47 g

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

4 checks passed
  • Page weight: 1.6 MB in 49 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 49 requests on a phone: scripts 732 KiB (19), fonts 598 KiB (3) and images 232 KiB (13). That is a lean page.

  • 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

5 to fixGoogle 9594
  • 1 button without a name

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

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner 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.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 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 10087
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (311 characters)

    Your meta description is 311 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("https://www.gabriel.dk/media/03zhiz2n/gabriel_logo_black.svg")”.

  • 45 internal links, 12 external

    The homepage links to 45 pages on gabriel.dk and 12 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Gabriel Group”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Leading supplier to the global furniture industry - Gabriel”.

  • 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.gabriel.dk/sitemap/.

AI search readiness

100
  • No llms.txt

    There is no https://www.gabriel.dk/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.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

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

Other pages

2 to fix93
  • 15 pages share a meta description

    https://www.gabriel.dk/about, https://www.gabriel.dk/about/175-years-anniversary, https://www.gabriel.dk/about/the-gabriel-culture, https://www.gabriel.dk/about/growth-journey, https://www.gabriel.dk/about/fabrics-from-the-very-beginning and https://www.gabriel.dk/about/co2e-neutral and 9 others use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.gabriel.dk/investor 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 25 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

1 to fixGoogle 10093
  • 4 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 411 words of copy

    The homepage carries about 411 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Hotjar (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.

  • 4 cookies set on arrival

    4

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

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
1851
Headquarters
Aalborg

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on gabriel.dk, including 13 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