Website review, no card needed

mokani.nl logo

mokani.nl website review

Visit site (opens in a new tab)Reviewed 10 November 202631 issues · 76 checks

This review found 31 issues worth fixing on mokani.nl, 12 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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 mokani.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mokani.nl at 0.9 s0.9 s
  2. mokani.nl at 1.7 s1.7 s
  3. mokani.nl at 2.6 s2.6 s
  4. mokani.nl at 3.5 s3.5 s
  5. mokani.nl at 4.4 s4.4 s
  6. mokani.nl at 5.2 s5.2 s
  7. mokani.nl at 6.1 s6.1 s
  8. mokani.nl at 7.0 s7.0 s

Speed

7 to fix56
  • Render-blocking requests

    2.6 s

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

  • Reduce unused JavaScript

    1.4 s · 352 KiB

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

  • Main-thread work: 5.3 s

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

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. 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 (Shopify, Clarity and chatway.app and others), adding 859 KiB and 613 ms of main-thread time.

  • Shopify adds 214 ms

    214 ms

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

  • chatway.app adds 145 ms

    145 ms

    chatway.app costs a phone 145 ms of main-thread work and 434 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.

  • Reduce unused CSS

    150 ms · 123 KiB

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

  • Use efficient cache lifetimes

    150 ms · 26 KiB

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

  • 5 long tasks on the main thread

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix63
  • Largest Contentful Paint: 9.7 s

    9.7 s

    Your largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “TRES – Ronde Eettafel | Roestvrij Staal”.

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Speed Index: 7.6 s

    7.6 s

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

  • Time to Interactive: 9.8 s

    9.8 s

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

  • Total Blocking Time: 208 ms

    208 ms

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

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 220 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 220 requests on a phone: scripts 991 KiB (68), other files 703 KiB (90) and images 291 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.65 g

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

3 checks passed
  • 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 9693
  • 17 text elements with low contrast

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

  • 2 tap targets too small

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 24 links without text

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

  • Headings skip levels

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

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

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

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 3 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 short (24 characters)

    Your title is only 24 characters: “Japandi meubels | MOKANI”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://mokaniatelier.de/)”.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 97 internal links, 9 external

    The homepage links to 97 pages on mokani.nl and 9 external pages.

4 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Ontdek Japandi meubels bij MOKANI. Bekijk eettafels, stoelen en barkrukken en vind meubels die passen bij jouw interieu…”.

  • Canonical URL set

    The canonical URL is https://www.mokani.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://www.mokani.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://www.mokani.nl/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.mokani.nl/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.mokani.nl/blogs/news and https://www.mokani.nl/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.mokani.nl/products/mokani-tv-meubel-microcement-op-maat-gemaakt, https://www.mokani.nl/collections/japandi-eetkamerstoelen, https://www.mokani.nl/collections/japandi-eettafels, https://www.mokani.nl/collections/japandi-barkrukken, https://www.mokani.nl/customer_authentication/redirect and https://www.mokani.nl/products/japandi-eetkamerstoel-tijdloos-scandinavisch-design-met-walnoot-hout-kleur and 1 other have 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 31 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.

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

Best practices

1 to fixGoogle 9697
  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    28 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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: 5 testimonial or review blocks. 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.

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

    The homepage carries about 336 words of visible text.

5 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Contact” and “Contact”.

  • 6 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 12 cookies set on arrival

    12

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

  • 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 mokani.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Searchpie Seo Speed · Optis Product Options · Microsoft Clarity · Omega Instafeed · loox.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
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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 mokani.nl, including 12 speed issues, 4 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