Website review, no card needed
inspee.nl website review
Visit site (opens in a new tab)Reviewed 4 November 202629 issues · 84 checks
This review found 29 issues worth fixing on inspee.nl, 10 of them high impact, across 84 checks. The most urgent: fails Core Web Vitals for real visitors. 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
85B- #15,240 of 111,455 reviewed websitesbeats 82%
- #9,767 of 63,670 online storesbeats 79%
- #9,499 of 58,149 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 95 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 99 ms |
| Jun 6, 2026 | 101 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 100 ms |
| Sep 12, 2026 | 99 ms |
| Sep 19, 2026 | 98 ms |
| Sep 26, 2026 | 101 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 103 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 103 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
3,281 HTML elements
The page has 3,281 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
777 KiB21 files are served with short cache lifetimes, so returning visitors download them again (777 KiB).
Improve image delivery
711 KiB48 images could be 711 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
150 ms · 493 KiBAbout 493 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
450 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.3 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 (Facebook, Klaviyo and Shopify and others), adding 955 KiB and 470 ms of main-thread time.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.
Legacy JavaScript
58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
30 KiB30 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
16 KiB16 KiB could be saved by minifying JavaScript.
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: 8 ms
8 msYour server sent the HTML in 8 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.
Time to Interactive: 17.7 s
17.7 sThe page becomes fully interactive after 17.7 s. Good is under 3.8 s.
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “1 slide”.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 344 ms
344 msScripts block taps and scrolling for 344 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 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: 715 ms
715 msReal visitors wait 715 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 576 requests
5.3 MBYour homepage downloads 5.3 MB in 576 requests on a phone: images 2.1 MB (106), scripts 1.6 MB (98) and other files 1.4 MB (326). Under 2 MB keeps phones on slow connections fast.
About 1.5 g of CO₂ per visit
1.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.51 g of CO₂e: 181.3 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (3 elements)
Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 127 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (238 characters)
Your meta description is 238 characters; Google truncates after about 160, so the end of your pitch is cut.
398 internal links, 13 external
The homepage links to 398 pages on inspee.nl and 13 external pages.
6 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “Inspee: Zoekt naar alle vrouwen!”.
Canonical URL set
The canonical URL is https://www.inspee.nl/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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.inspee.nl/sitemap.xml.
AI search readiness
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 (1,069 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.inspee.nl/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages slow to respond
https://www.inspee.nl/collections/nieuw-jeans-en-broeken-31008, https://www.inspee.nl/collections/nieuw-rokken-en-korte-broeken-31006, https://www.inspee.nl/collections/nieuwe-collectie-schoenen-31001, https://www.inspee.nl/collections/5458-coups-de-coeur-nl and https://www.inspee.nl/collections/5320-jurken took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 149 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 72 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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 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.
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 573 words of copy
The homepage carries about 573 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Neem contact met ons op”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Matomo.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Meta Pixel (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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
28 other companies contacted
Loading the homepage contacts 28 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 inspee.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Addingwell · Oxi Social Login Wishlist · Nosto · Gorgias Live Chat Helpdesk · Sc Easy Redirects · Yotpo Loyalty Rewards · Klaviyo Email Marketing Sms · Countdown Timer · Inspee Wishlist App · Inspee Gtm Prod · Inspee Erp App · amazonaws.com
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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Matomo
- Hosting
- Shopify
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 inspee.nl, including 13 speed issues, 2 SEO issues and 5 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.