Website review, no card needed

jutter.co logo

jutter.co website review

Visit site (opens in a new tab)Reviewed 16 November 202629 issues · 81 checks

This review found 29 issues worth fixing on jutter.co, 10 of them high impact, across 81 checks. The most urgent: improve image delivery. 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.1 s494 msMay 30Nov 14580 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.0 s
Jun 6, 2026987 ms
Jun 13, 2026956 ms
Jun 20, 2026834 ms
Jun 27, 2026751 ms
Jul 4, 2026667 ms
Jul 11, 2026631 ms
Jul 18, 2026653 ms
Jul 25, 2026642 ms
Aug 1, 2026636 ms
Aug 8, 2026631 ms
Aug 15, 2026652 ms
Aug 22, 2026633 ms
Aug 29, 2026625 ms
Sep 5, 2026626 ms
Sep 12, 2026585 ms
Sep 19, 2026593 ms
Sep 26, 2026586 ms
Oct 3, 2026574 ms
Oct 10, 2026565 ms
Oct 17, 2026571 ms
Oct 24, 2026590 ms
Oct 31, 2026601 ms
Nov 7, 2026596 ms
Nov 14, 2026580 ms
Real-visitor tap response (INP)75th percentile, phones
104 ms68 msMay 30Nov 1479 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202697 ms
Jun 6, 2026100 ms
Jun 13, 202696 ms
Jun 20, 202690 ms
Jun 27, 202685 ms
Jul 4, 202677 ms
Jul 11, 202677 ms
Jul 18, 202678 ms
Jul 25, 202678 ms
Aug 1, 202679 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202675 ms
Aug 29, 202672 ms
Sep 5, 202674 ms
Sep 12, 202678 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202679 ms
Oct 10, 202678 ms
Oct 17, 202677 ms
Oct 24, 202678 ms
Oct 31, 202679 ms
Nov 7, 202679 ms
Nov 14, 202679 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 jutter.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jutter.co at 0.4 s0.4 s
  2. jutter.co at 0.9 s0.9 s
  3. jutter.co at 1.3 s1.3 s
  4. jutter.co at 1.7 s1.7 s
  5. jutter.co at 2.2 s2.2 s
  6. jutter.co at 2.6 s2.6 s
  7. jutter.co at 3.0 s3.0 s
  8. jutter.co at 3.4 s3.4 s

Speed

7 to fix78
  • Improve image delivery

    1.0 s · 1.4 MB

    9 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 78

    78/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, webshopapp.com and adapts2ls.online and others), adding 2.2 MB and 288 ms of main-thread time.

  • Reduce unused JavaScript

    255 KiB

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

  • Google Tag Manager adds 206 ms

    206 ms

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

  • webshopapp.com adds 65 ms

    65 ms

    webshopapp.com costs a phone 65 ms of main-thread work and 1.7 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.

  • Use efficient cache lifetimes

    250 ms · 37 KiB

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

  • Reduce unused CSS

    150 ms · 28 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 118 ms. During a long task the page ignores taps.

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

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

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 4.9 s

    4.9 s

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

  • Time to Interactive: 7.1 s

    7.1 s

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

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

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 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.

10 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: 0.9 s

    0.9 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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: 505 ms

    505 ms

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

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

    -20%

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

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

    -42%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.6 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).

  • Total Blocking Time: 34 ms

    34 ms

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

Images and page weight

2 to fix65
  • 7 images far larger than shown

    808 KiB

    7 images are downloaded at several times the size a phone draws them, for example slider-1-mobile.jpg at 1,600 px wide, shown at 360 px. Resized copies would save about 808 KiB.

  • Page weight: 2.5 MB in 50 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 50 requests on a phone: images 1.6 MB (12), scripts 564 KiB (14) and other files 250 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (240 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.7 g of CO₂ per visit

    0.71 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 7185
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    2 dropdowns have no label.

  • 15 text elements with low contrast

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

  • 15 images without alt text

    15 images have no alt text, which hurts accessibility and image search.

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

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

  • 32 links without text

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

  • 10 form fields without a label

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

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 35 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • 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.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 227 internal links, 3 external

    The homepage links to 227 pages on jutter.co and 3 external pages.

6 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Speelgoed is belangrijk voor de ontwikkeling van de kinderen op een kinderopvang. Bekijk onze webshop voor het volledig…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Speelgoed voor de kinderopvang bestellen - JUTTER & Co.”.

  • Canonical URL set

    The canonical URL is https://www.jutter.co/.

  • Structured data in place

    Structured data found: Organization.

  • 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.jutter.co/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.jutter.co/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 (830 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    40 of 41 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

    The homepage carries about 527 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact & informatie” and “Start vergelijking”.

  • 18 short forms

    18 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 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
  • 3 trackers load before any consent

    3

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

  • 5 cookies set on arrival

    5

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 jutter.co, 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 Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on jutter.co, including 12 speed issues, 2 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