Website review, no card needed

fonq.nl logo

fonq.nl website review

Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 87 checks

This review found 39 issues worth fixing on fonq.nl, 16 of them high impact, across 87 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.3 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.6 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
143 ms92 msMay 16Oct 31124 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202699 ms
May 23, 202698 ms
May 30, 2026103 ms
Jun 6, 2026110 ms
Jun 13, 2026114 ms
Jun 20, 2026122 ms
Jun 27, 2026128 ms
Jul 4, 2026131 ms
Jul 11, 2026135 ms
Jul 18, 2026137 ms
Jul 25, 2026134 ms
Aug 1, 2026131 ms
Aug 8, 2026133 ms
Aug 15, 2026130 ms
Aug 22, 2026130 ms
Aug 29, 2026129 ms
Sep 5, 2026128 ms
Sep 12, 2026128 ms
Sep 19, 2026128 ms
Sep 26, 2026128 ms
Oct 3, 2026130 ms
Oct 10, 2026133 ms
Oct 17, 2026135 ms
Oct 24, 2026130 ms
Oct 31, 2026124 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 fonq.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fonq.nl at 0.6 s0.6 s
  2. fonq.nl at 1.2 s1.2 s
  3. fonq.nl at 1.8 s1.8 s
  4. fonq.nl at 2.4 s2.4 s
  5. fonq.nl at 3.1 s3.1 s
  6. fonq.nl at 3.7 s3.7 s
  7. fonq.nl at 4.3 s4.3 s
  8. fonq.nl at 4.9 s4.9 s

Speed

11 to fix50
  • Use efficient cache lifetimes

    4.0 s · 3.0 MB

    59 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).

  • Improve image delivery

    1.7 s · 647 KiB

    19 images could be 647 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

  • Render-blocking requests

    1.1 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.1 s.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookie-Script.com and others), adding 5.4 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 668 KiB

    About 668 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 938 ms

    938 ms

    Google Tag Manager costs a phone 938 ms of main-thread work and 1.0 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: 50

    50/100

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

  • etrias.nl adds 8 ms

    8 ms

    etrias.nl costs a phone 8 ms of main-thread work and 4.1 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.

  • Main-thread work: 3.0 s

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

  • 13 long tasks on the main thread

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

  • 1,558 HTML elements

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

  • Reduce unused CSS

    150 ms · 49 KiB

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

  • Font display

    150 ms

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

  • Legacy JavaScript

    36 KiB

    Polyfills for old browsers add 36 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: 106 ms

    106 ms

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

Core Web Vitals

7 to fix100
  • Time to Interactive: 18.6 s

    18.6 s

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

  • Largest Contentful Paint: 7.6 s

    7.6 s

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

  • Total Blocking Time: 850 ms

    850 ms

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

  • 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 99 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 5.1 s

    5.1 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 18 images without width and height

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

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.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: 155 ms

    155 ms

    Real visitors wait 155 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.0 s

    1.0 s

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

  • Real-user TTFB: 581 ms

    581 ms

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

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

    -10%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix35
  • Page weight: 5.6 MB in 96 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 96 requests on a phone: images 3.8 MB (42), scripts 1.6 MB (28) and fonts 58 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    fonq pop up.png weighs 2.0 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.8 MB

    1 image is downloaded at several times the size a phone draws it, for example fonq pop up.png at 3,000 px wide, shown at 300 px. Resized copies would save about 1.8 MB.

  • 6 images below the first screen load straight away

    6 images further down the page (254 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.58 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 7987
  • 1 button without a name

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

  • 14 text elements with low contrast

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

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Alternative text of images should not be repeated as text (17 elements)

    Alternative text of images should not be repeated as text: 17 elements on the page fail this check, rated minor by axe-core.

  • 3 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 52 images in the HTML carry an alt attribute.

  • 42 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: 42 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10090
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 672 internal links, 8 external

    The homepage links to 672 pages on fonq.nl and 8 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Kan jouw huis wel wat fonQ gebruiken? Naast een groot aanbod voor je interieur vind je ook keuzehulp en inspiratie. Gee…”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “fonQ * De online woonwinkel voor jou | fonQ.nl”.

  • Canonical URL set

    The canonical URL is https://www.fonq.nl/.

  • Structured data in place

    Structured data found: BreadcrumbList and Organization.

  • 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.fonq.nl/sitemap/fonq_nl/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.fonq.nl/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix78
  • 3 pages share a title

    https://www.fonq.nl/veelgesteldevragen/wat-zijn-de-verzendkosten-fonq, https://www.fonq.nl/veelgesteldevragen/hoe-kan-ik-betalen and https://www.fonq.nl/veelgesteldevragen all use the title “Klantenservice | fonQ.nl”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.fonq.nl/veelgesteldevragen/wat-zijn-de-verzendkosten-fonq, https://www.fonq.nl/veelgesteldevragen/hoe-kan-ik-betalen and https://www.fonq.nl/veelgesteldevragen have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.fonq.nl/veelgesteldevragen/hoe-kan-ik-betalen, whose canonical is https://www.fonq.nl/veelgesteldevragen/contact-fonq. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 pages without an H1

    https://www.fonq.nl/veelgesteldevragen/wat-zijn-de-verzendkosten-fonq, https://www.fonq.nl/veelgesteldevragen/hoe-kan-ik-betalen, https://www.fonq.nl/veelgesteldevragen, https://www.fonq.nl/collections/kasten, https://www.fonq.nl/collections/tv-meubel and https://www.fonq.nl/collections/dressoir and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.fonq.nl/veelgesteldevragen/hoe-kan-ik-betalen and https://www.fonq.nl/veelgesteldevragen have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 197 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.

  • 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 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=4032902&Ver=2&mid=6997cc40-5279-44ec-8051-9a9216dfe169&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=fonQ%20*%20De%20online%20woonwinkel%20voor%20jou%20%7C%2.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://bzrcdn.openai.com/sdk/oaiq.min.js' violates the following Content Security Policy directive…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    35 of 38 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 503 words of copy

    The homepage carries about 503 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Onze eigen collectie shop by fonQ” and “Verlichting shop collectie”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Onze eigen collectie shop by fonQ”, “Verlichting shop collectie” and “Meubels shop collectie”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 2 cookies set on arrival

    2

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 fonq.nl, 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
Mirakl;Shopify;Shopify Local Pickup;Shopify Plus
Hosting
Cloudflare

Company

Founded
2005
Headquarters
Utrecht

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on fonq.nl, including 18 speed issues, 1 SEO issue and 1 conversion gap. 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