Website review, no card needed
skantrae.com website review
Visit site (opens in a new tab)Reviewed 19 October 202630 issues · 79 checks
This review found 30 issues worth fixing on skantrae.com, 10 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.0 s |
| May 2, 2026 | 1.0 s |
| May 9, 2026 | 1.0 s |
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 967 ms |
| Jun 20, 2026 | 968 ms |
| Jun 27, 2026 | 964 ms |
| Jul 4, 2026 | 966 ms |
| Jul 11, 2026 | 953 ms |
| Jul 18, 2026 | 969 ms |
| Jul 25, 2026 | 967 ms |
| Aug 1, 2026 | 976 ms |
| Aug 8, 2026 | 992 ms |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 999 ms |
| Aug 29, 2026 | 982 ms |
| Sep 5, 2026 | 984 ms |
| Sep 12, 2026 | 958 ms |
| Sep 19, 2026 | 966 ms |
| Sep 26, 2026 | 992 ms |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 120 ms |
| May 2, 2026 | 117 ms |
| May 9, 2026 | 119 ms |
| May 16, 2026 | 113 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 111 ms |
| Aug 1, 2026 | 110 ms |
| Aug 8, 2026 | 110 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 115 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 139 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.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.1 s
3.5 s
Speed
Render-blocking requests
5.8 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.8 s.
Reduce unused CSS
1.1 s · 138 KiBAbout 138 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Reduce unused JavaScript
300 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 68). 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 (Google Tag Manager, Optanon and JSDelivr CDN and others), adding 2.3 MB and 455 ms of main-thread time.
Improve image delivery
593 KiB7 images could be 593 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 359 ms
359 msGoogle Tag Manager costs a phone 359 ms of main-thread work and 521 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.
Document request latency
362 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Optanon adds 67 ms
67 msOptanon costs a phone 67 ms of main-thread work and 359 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.
sanity.io adds 0 ms
0 mssanity.io costs a phone 0 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.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 453 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 144 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
127 KiB6 files are served with short cache lifetimes, so returning visitors download them again (127 KiB).
Legacy JavaScript
85 KiBPolyfills for old browsers add 85 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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.
Server response: 408 ms
408 msYour server sent the HTML in 408 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 8.7 s
8.7 sThe first text or image appears after 8.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Sfeervolle binnendeur in interieur”.
Time to Interactive: 27.6 s
27.6 sThe page becomes fully interactive after 27.6 s. Good is under 3.8 s.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 120 ms to 139 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-10, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 158 ms
158 msReal visitors wait 158 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 FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 400 ms
400 msReal visitors wait 400 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 129 ms
129 msScripts block the page for only 129 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 104 requests
5.1 MBYour homepage downloads 5.1 MB in 104 requests on a phone: scripts 2.6 MB (41), images 1.2 MB (30) and fonts 603 KiB (3). Under 2 MB keeps phones on slow connections fast.
8 images below the first screen load straight away
8 images further down the page (748 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
7 images far larger than shown
393 KiB7 images are downloaded at several times the size a phone draws them, for example ae1e7f556f0b2d653118aaf2ab572dca8316051a-1900x1425.jpg at 1,333 px wide, shown at 370 px. Resized copies would save about 393 KiB.
2 images in older formats
2 images (178 KiB) are 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 1.4 g of CO₂ per visit
1.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 174.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
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 32 images in the HTML carry an alt attribute.
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (29 characters)
Your title is only 29 characters: “Aan alles gedacht. | Skantrae”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
86 internal links, 9 external
The homepage links to 86 pages on skantrae.com and 9 external pages.
6 checks passed
Meta description: 117 characters
Your meta description is 117 characters: “Skantrae is al ruim 40 jaar fabrikant en leverancier van binnendeuren, buitendeuren, glas, deurbeslag en accessoires.”.
One H1 headline
Your main headline reads: “De specialist in binnen- en buitendeuren”.
Canonical URL set
The canonical URL is https://www.skantrae.com/.
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.skantrae.com/sitemap.xml.
AI search readiness
robots.txt blocks 1 AI answer engine crawler
1 of 6Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description 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.
No llms.txt
There is no https://www.skantrae.com/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.
Opted out of AI training for 4 crawlers
robots.txt blocks GPTBot, ClaudeBot, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (836 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://www.skantrae.com/contact, https://www.skantrae.com/binnendeuren, https://www.skantrae.com/nieuwe-slimseries-ronde-vormen, https://www.skantrae.com/inspiratie/industrieel and https://www.skantrae.com/inspiratie have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://www.skantrae.com/showroom, https://www.skantrae.com/projects, https://www.skantrae.com/inspiratie/landelijk, https://www.skantrae.com/inspiratie/klassiek and https://www.skantrae.com/kwaliteit/next use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.skantrae.com/kwaliteit/next, whose canonical is https://www.skantrae.com/buitendeuren/next-buitendeuren. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.skantrae.com/verkooppunten and https://www.skantrae.com/projects 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 43 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.
Titles are unique
Every page we checked has its own title.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
19 of 20 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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 825 words of copy
The homepage carries about 825 words of visible text.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Contact formulier”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Mixpanel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 skantrae.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on skantrae.com, including 16 speed issues, 2 SEO issues and 2 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.