Website review, no card needed
northcdatacenters.com website review
Visit site (opens in a new tab)Reviewed 24 October 202628 issues · 76 checks
This review found 28 issues worth fixing on northcdatacenters.com, 10 of them high impact, across 76 checks. The most urgent: page weight: 12.3 MB in 194 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
86BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.6 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 314 ms |
| May 9, 2026 | 148 ms |
| May 16, 2026 | 122 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 93 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 116 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 107 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 108 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 116 ms |
| Aug 29, 2026 | 119 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 131 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 122 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
Mobile performance score: 79
79/100Your mobile performance score is 79 (desktop: 93). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Reduce unused CSS
450 ms · 63 KiBAbout 63 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.
2,098 HTML elements
The page has 2,098 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 5 KiB5 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.
Improve image delivery
48 KiB2 images could be 48 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 540 ms of it running JavaScript. That is comfortably low.
Server response: 197 ms
197 msYour server sent the HTML in 197 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: 4.8 s
4.8 sYour largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Digital business. Personal connections.”.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 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.
Time to Interactive: 4.8 s
4.8 sThe page becomes fully interactive after 4.8 s. Good is under 3.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 127 ms
127 msReal visitors wait 127 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.
Tap response (INP) got 47% faster for real visitors
-47%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 314 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.6 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 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).
Total Blocking Time: 21 ms
21 msScripts block the page for only 21 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 12.3 MB in 194 requests
12.3 MBYour homepage downloads 12.3 MB in 194 requests on a phone: media 11.3 MB (3), scripts 303 KiB (38) and fonts 234 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 3.5 g of CO₂ per visit
3.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.49 g of CO₂e: 418.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
Certain ARIA roles must be contained by particular parents (5 elements)
Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Orphan list items
Some list items are not inside a list.
14 images without alt text
14 images have no alt text, which hurts accessibility and image search.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
106 internal links, 4 external
The homepage links to 106 pages on northcdatacenters.com and 4 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Duurzame, betrouwbare datacenterdiensten voor bedrijven, IT-dienstverleners, instellingen en overheden in Nederland, Du…”.
One H1 headline
Your main headline reads: “Digital business.Personal connections.”.
Title: 56 characters
Your title is a healthy 56 characters: “Datacenter- en colocatieoplossingen | NorthC Datacenters”.
Canonical URL set
The canonical URL is https://www.northcdatacenters.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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.northcdatacenters.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.northcdatacenters.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.
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 sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,051 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.northcdatacenters.com/portal has no meta description, so Google writes the search snippet from whatever text it finds.
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.northcdatacenters.com/kennisbank, whose canonical is https://www.northcdatacenters.com/insights. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.
5 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.
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
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_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
22 of 24 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 14-field form
Your longest form asks for 14 fields (7 required). Every extra field lowers completion.
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 585 words of copy
The homepage carries about 585 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact”, “Download carrierlijst” and “Contact opnemen”.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
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 northcdatacenters.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on northcdatacenters.com, including 11 speed issues, 1 SEO issue 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.