Website review, no card needed
nrc.nl website review
Visit site (opens in a new tab)Reviewed 28 October 202630 issues · 81 checks
This review found 30 issues worth fixing on nrc.nl, 10 of them high impact, across 81 checks. The most urgent: 22,320 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 888 ms |
| May 16, 2026 | 887 ms |
| May 23, 2026 | 889 ms |
| May 30, 2026 | 891 ms |
| Jun 6, 2026 | 900 ms |
| Jun 13, 2026 | 908 ms |
| Jun 20, 2026 | 915 ms |
| Jun 27, 2026 | 921 ms |
| Jul 4, 2026 | 920 ms |
| Jul 11, 2026 | 930 ms |
| Jul 18, 2026 | 934 ms |
| Jul 25, 2026 | 945 ms |
| Aug 1, 2026 | 960 ms |
| Aug 8, 2026 | 955 ms |
| Aug 15, 2026 | 946 ms |
| Aug 22, 2026 | 925 ms |
| Aug 29, 2026 | 916 ms |
| Sep 5, 2026 | 904 ms |
| Sep 12, 2026 | 905 ms |
| Sep 19, 2026 | 911 ms |
| Sep 26, 2026 | 915 ms |
| Oct 3, 2026 | 922 ms |
| Oct 10, 2026 | 924 ms |
| Oct 17, 2026 | 915 ms |
| Oct 24, 2026 | 911 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 127 ms |
| May 16, 2026 | 123 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 124 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 132 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 130 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 125 ms |
| Oct 24, 2026 | 123 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
22,320 HTML elements
The page has 22,320 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
1.0 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 50). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
450 ms · 545 KiBAbout 545 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
150 ms · 599 KiB9 images could be 599 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Didomi and mhtr.be and others), adding 713 KiB and 529 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 403 KiB13 files are served with short cache lifetimes, so returning visitors download them again (403 KiB).
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 304 ms. During a long task the page ignores taps.
Reduce unused CSS
25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 208 ms
208 msYour server sent the HTML in 208 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 17.2 s
17.2 sThe page becomes fully interactive after 17.2 s. Good is under 3.8 s.
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 870 ms
870 msScripts block taps and scrolling for 870 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.24
0.24The layout shifts by 0.24 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 127 ms to 123 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-24, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s 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.7 s
0.7 sReal visitors wait 0.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 166 ms
166 msReal visitors wait 166 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: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 251 ms
251 msReal visitors wait 251 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 2.4 MB in 69 requests
2.4 MBYour homepage downloads 2.4 MB in 69 requests on a phone: scripts 1.1 MB (21), images 857 KiB (16) and fonts 242 KiB (7). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
281026VER_2037834406_seance.jpg 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.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 82.7 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
97 links without text
97 visible links have no text or label, so screen readers cannot say where they go.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate 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. (83 elements).
2 checks passed
Every image has alt text
All 208 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (NewsMediaOrganization and WebSite) but with 1 problem, for example “WebSite: missing name”.
317 internal links, 41 external
The homepage links to 317 pages on nrc.nl and 41 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Nieuws, duiding, analyse en onderzoeksjournalistiek over onderwerpen die er echt toe doen. Feitelijk, betrouwbaar, diep…”.
One H1 headline
Your main headline reads: “NRC - Nieuws, achtergronden en onderzoeksjournalistiek”.
Title: 54 characters
Your title is a healthy 54 characters: “NRC - Nieuws, achtergronden en onderzoeksjournalistiek”.
Canonical URL set
The canonical URL is https://www.nrc.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://www.nrc.nl/sitemap/index.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-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.
No llms.txt
There is no https://www.nrc.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, 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.
2 checks passed
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 (5,135 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.nrc.nl/columnisten has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 156 found) and read each the way a search engine does.
6 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 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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
37 of 39 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.
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 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 2,081 words of copy
The homepage carries about 2,081 words of visible text.
1 checks passed
4 calls to action
The homepage has 4 calls to action, for example “E-book” and “Contact”.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Comscore, Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
21 cookies set on arrival
21Opening the homepage sets 21 cookies (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Didomi
A consent management tool (Didomi) 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 nrc.nl, 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
- Hosting
- Intermax Cloudsourcing B.V.
Company
- Founded
- 1970
- Headquarters
- Amsterdam
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 nrc.nl, including 15 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.