Website review, no card needed

dehobbit.nl logo

dehobbit.nl website review

Visit site (opens in a new tab)Reviewed 9 November 202628 issues · 70 checks

This review found 28 issues worth fixing on dehobbit.nl, 5 of them high impact, across 70 checks. The most urgent: hidden but focusable. 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
695 ms597 msMay 23Nov 7620 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026648 ms
May 30, 2026643 ms
Jun 6, 2026637 ms
Jun 13, 2026637 ms
Jun 20, 2026644 ms
Jun 27, 2026642 ms
Jul 4, 2026654 ms
Jul 11, 2026661 ms
Jul 18, 2026675 ms
Jul 25, 2026682 ms
Aug 1, 2026673 ms
Aug 8, 2026684 ms
Aug 15, 2026675 ms
Aug 22, 2026677 ms
Aug 29, 2026675 ms
Sep 5, 2026654 ms
Sep 12, 2026653 ms
Sep 19, 2026635 ms
Sep 26, 2026625 ms
Oct 3, 2026619 ms
Oct 10, 2026608 ms
Oct 17, 2026617 ms
Oct 24, 2026625 ms
Oct 31, 2026630 ms
Nov 7, 2026620 ms
Real-visitor tap response (INP)75th percentile, phones
105 ms87 msMay 23Nov 791 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202694 ms
May 30, 202695 ms
Jun 6, 202696 ms
Jun 13, 2026102 ms
Jun 20, 2026102 ms
Jun 27, 2026103 ms
Jul 4, 2026103 ms
Jul 11, 2026102 ms
Jul 18, 2026102 ms
Jul 25, 202699 ms
Aug 1, 202695 ms
Aug 8, 202694 ms
Aug 15, 202692 ms
Aug 22, 202692 ms
Aug 29, 202691 ms
Sep 5, 202689 ms
Sep 12, 202693 ms
Sep 19, 202692 ms
Sep 26, 202693 ms
Oct 3, 202693 ms
Oct 10, 202691 ms
Oct 17, 202693 ms
Oct 24, 202694 ms
Oct 31, 202694 ms
Nov 7, 202691 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 dehobbit.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix85
  • Mobile performance score: 85

    85/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 871 KiB and 656 ms of main-thread time.

  • Render-blocking requests

    500 ms

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

  • Reduce unused CSS

    300 ms · 39 KiB

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

  • Reduce unused JavaScript

    299 KiB

    About 299 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 2.8 s

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

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    208 KiB

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

  • Improve image delivery

    183 KiB

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

  • Legacy JavaScript

    40 KiB

    Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need.

  • 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: 40 ms

    40 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 11.3 s

    11.3 s

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 4.3 s

    4.3 s

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

  • Total Blocking Time: 224 ms

    224 ms

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

8 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.0 s

    1.0 s

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

  • Real-user INP: 91 ms

    91 ms

    Real visitors wait 91 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.6 s

    0.6 s

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

  • Real-user TTFB: 297 ms

    297 ms

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

  • Cumulative Layout Shift: 0.02

    0.02

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

2 to fix81
  • Page weight: 2.8 MB in 218 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 218 requests on a phone: scripts 1.0 MB (56), other files 856 KiB (119) and images 689 KiB (35). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    S027_c314cc2d-aa39-41ce-b52e-825d348eeb78.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.8 g of CO₂ per visit

    0.78 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.6 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

1 to fixGoogle 9698
  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • Title is long (78 characters)

    Your title is 78 characters, so Google will cut it off around 60: “Uitgeverij De Hobbit - agenda's, kalenders en planners – Uitgeverij De Hobbit®”.

  • No structured data

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

  • Meta description is long (302 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 69 internal links, 0 external

    The homepage links to 69 pages on dehobbit.nl and 0 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Uitgeverij De Hobbit®”.

  • Canonical URL set

    The canonical URL is https://dehobbit.nl/.

  • 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://dehobbit.nl/sitemap.xml.

AI search readiness

1 to fix83
  • 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://dehobbit.nl/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://dehobbit.nl/collections/najaar-2027, https://dehobbit.nl/collections/bundels-2027 and https://dehobbit.nl/collections/2-weeks-kalenders/Najaar have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 links to non-canonical URLs

    Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://dehobbit.nl/collections/alle-agendas/Najaar, whose canonical is https://dehobbit.nl/collections/alle-agendas/najaar. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages slow to respond

    https://dehobbit.nl/collections/2-weeks-kalenders/Najaar, https://dehobbit.nl/collections/maandkalenders/Najaar and https://dehobbit.nl/collections/afsprakenagendas/Najaar took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    12 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 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.

  • Only about 84 words

    The homepage has only about 84 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • 2 short forms

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 1 of them by other companies (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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 dehobbit.nl, 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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Section Factory · Restockrocket · wetracked.io

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
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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 dehobbit.nl, including 11 speed issues, 4 SEO issues and 6 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