Website review, no card needed
sillysanta.nl website review
Visit site (opens in a new tab)Reviewed 12 November 202636 issues · 88 checks
This review found 36 issues worth fixing on sillysanta.nl, 13 of them high impact, across 88 checks. The most urgent: 11,957 HTML elements. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82B- #31,964 of 112,578 reviewed websitesbeats 66%
- #21,538 of 64,677 online storesbeats 60%
- #20,843 of 59,122 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 164 ms |
| Jul 25, 2026 | 160 ms |
| Aug 1, 2026 | 159 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 169 ms |
| Aug 22, 2026 | 174 ms |
| Aug 29, 2026 | 177 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 164 ms |
| Oct 3, 2026 | 160 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 157 ms |
| Oct 24, 2026 | 155 ms |
| Oct 31, 2026 | 158 ms |
| Nov 7, 2026 | 161 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
Speed
11,957 HTML elements
The page has 11,957 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
1.1 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and Cookiebot and others), adding 1,013 KiB and 957 ms of main-thread time.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
467 KiB27 images could be 467 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
402 KiBAbout 402 KiB of JavaScript is downloaded but never used on this page.
Shopify adds 358 ms
358 msShopify costs a phone 358 ms of main-thread work and 285 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.
Google Tag Manager adds 267 ms
267 msGoogle Tag Manager costs a phone 267 ms of main-thread work and 358 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 240 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 58 KiBAbout 58 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
69 KiB8 files are served with short cache lifetimes, so returning visitors download them again (69 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 25 ms
25 msYour server sent the HTML in 25 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 446 ms
446 msScripts block taps and scrolling for 446 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.7 s
4.7 sVisually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
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 162 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 479 ms
479 msReal visitors wait 479 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 44% faster for real visitors
-44%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.014
0.014The layout barely moves while loading (CLS 0.014, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 278 requests
4.0 MBYour homepage downloads 4.0 MB in 278 requests on a phone: images 1.8 MB (96), scripts 1.1 MB (77) and other files 779 KiB (80). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.8 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
287 text elements with low contrast
287 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
20 form fields without a label
20 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 598 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (86 characters)
Your title is 86 characters, so Google will cut it off around 60: “SillySanta | Kersttruien & Kerstpyjama's | 1.000.000+ Tevreden Klanten – SillySanta.nl”.
Meta description is long (195 characters)
Your meta description is 195 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("sillysanta.nl")”.
689 internal links, 0 external
The homepage links to 689 pages on sillysanta.nl and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “SillySanta.nl”.
Canonical URL set
The canonical URL is https://sillysanta.nl/.
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://sillysanta.nl/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (3,005 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://sillysanta.nl/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages share a meta description
https://sillysanta.nl/products/fuck-off-pantoffels, https://sillysanta.nl/products/but-first-coffee-pantoffels and https://sillysanta.nl/products/dont-disturb-im-gaming-pantoffels use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
7 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 11 pages that loaded have a meta description.
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 11 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=52016394&tm=gtm002&Ver=2&mid=2ea84b2a-696a-44b0-a130-10753849e266&bo=1&sid=42b61250de6a11f1acdf21a87280f71f&vid=42b62b30de6a11f1b0a26534d3087ba2&vids=1&msclkid=N&pi=91.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
174 of 188 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 230 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 2,485 words of copy
The homepage carries about 2,485 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Shop kerstcadeaus”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
7 trackers load before any consent
7Before 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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 1 of them by other companies (measured from a US location before any click).
30 other companies contacted
Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 sillysanta.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
- Shopify;Shopify Plus
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on sillysanta.nl, including 16 speed issues, 3 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.