Website review, no card needed
gemivawebwinkel.nl website review
Visit site (opens in a new tab)Reviewed 12 November 202633 issues · 79 checks
This review found 33 issues worth fixing on gemivawebwinkel.nl, 7 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 689 ms |
| May 30, 2026 | 718 ms |
| Jun 6, 2026 | 697 ms |
| Jun 13, 2026 | 679 ms |
| Jun 20, 2026 | 640 ms |
| Jun 27, 2026 | 623 ms |
| Aug 29, 2026 | 746 ms |
| Sep 5, 2026 | 746 ms |
| Oct 17, 2026 | 583 ms |
| Oct 24, 2026 | 586 ms |
| Oct 31, 2026 | 582 ms |
| Nov 7, 2026 | 622 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 83 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 80 ms |
| Oct 31, 2026 | 80 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.7 s · 584 KiBAbout 584 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (YouTube, jwwb.nl and Plausible and others), adding 2.1 MB and 1.1 s of main-thread time.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
YouTube adds 812 ms
812 msYouTube costs a phone 812 ms of main-thread work and 982 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
450 ms · 138 KiBAbout 138 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
300 ms · 216 KiB5 images could be 216 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
450 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
jwwb.nl adds 237 ms
237 msjwwb.nl costs a phone 237 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 252 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
150 ms · 49 KiB4 files are served with short cache lifetimes, so returning visitors download them again (49 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 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: 104 ms
104 msYour server sent the HTML in 104 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.6 s
11.6 sYour largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 12.4 s
12.4 sThe page becomes fully interactive after 12.4 s. Good is under 3.8 s.
Total Blocking Time: 430 ms
430 msScripts block taps and scrolling for 430 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 83 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.6 s
0.6 sReal visitors wait 0.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.5 s
0.5 sReal visitors see the first content after 0.5 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 52 requests
2.1 MBYour homepage downloads 2.1 MB in 52 requests on a phone: scripts 1.0 MB (14), images 717 KiB (20) and fonts 164 KiB (5). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
logo-gemiva-high-dowuzz.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.6 g of CO₂ per visit
0.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 70.5 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
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 4 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 short (23 characters)
Your title is only 23 characters: “Home | Gemiva Webwinkel”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (186 characters)
Your meta description is 186 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
148 internal links, 1 external
The homepage links to 148 pages on gemivawebwinkel.nl and 1 external page.
6 checks passed
One H1 headline
Your main headline reads: “Gemiva Webwinkel”.
Canonical URL set
The canonical URL is https://www.gemivawebwinkel.nl/.
Structured data in place
Structured data found: 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.gemivawebwinkel.nl/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.gemivawebwinkel.nl/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 (643 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.gemivawebwinkel.nl/winkelwagen is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
6 pages without a meta description
https://www.gemivawebwinkel.nl/winkelwagen, https://www.gemivawebwinkel.nl/webwinkel/kerst/kerstproducten, https://www.gemivawebwinkel.nl/webwinkel/kerst/kerstkaarsen-2, https://www.gemivawebwinkel.nl/webwinkel/hout, https://www.gemivawebwinkel.nl/webwinkel/kaarsen and https://www.gemivawebwinkel.nl/webwinkel/kaarsen/geboortekaarsen have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://www.gemivawebwinkel.nl/webwinkel, https://www.gemivawebwinkel.nl/webwinkel/kerst, https://www.gemivawebwinkel.nl/webwinkel/kerst/kerstproducten, https://www.gemivawebwinkel.nl/webwinkel/kerst/kerstkaarsen-2, https://www.gemivawebwinkel.nl/webwinkel/kerst/kerstkaarten and https://www.gemivawebwinkel.nl/webwinkel/sinterklaas and 8 others 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 143 found) and read each the way a search engine does.
4 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of null (reading 'addEventListener')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
6 of 7 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 248 words
The homepage has only about 248 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.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Plausible.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 gemivawebwinkel.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Plausible
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on gemivawebwinkel.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.