C — https://rijksmuseum.nl | BeaverCheck Audit

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Mostly accessible, but some users still face barriers.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Apple · 1212 peers

You 72

Avg 72

At average

0 50 100

Better than 33% of Apple sites See full Apple benchmark →

core-js · 1472 peers

You 72

Avg 72

At average

0 50 100

Better than 37% of core-js sites See full core-js benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

114 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

115 HTTP requests — consider bundling or reducing

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Frijksmuseum.nl)](https://beavercheck.com/results/f6a1dff3-e665-4d31-8dbc-21a5a00873ee)

HTML

<a href="https://beavercheck.com/results/f6a1dff3-e665-4d31-8dbc-21a5a00873ee"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Frijksmuseum.nl" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Frijksmuseum.nl

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 3.7s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

Your LCP is 3.7s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

1 critical 6 warning

7 barrier(s) likely increasing bounce by ~23%.

Speed (2)

Page loads in 3.7s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 1.2s over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

Page feels frozen for 3.3s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€468 investment → €1,837/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +4614%

Investment

€468

6h · 5 findings

Monthly returns

€1,837 /mo

~€22,038 / year

Conversions recovered €1,836
Bandwidth savings €0.67

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
AVG EUR 20,000,000
EAA EUR 500,000

Payback period

0 12mo 24mo

€128 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€468

5.5 developer hours at €85/hr

Based on Netherlands rates (€85/hr)

Quick wins

€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,008 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveAVGEAA

No privacy policy link detected
AVG: EUR 10,000 – EUR 20,000,000
2 advertising/retargeting trackers detected
AVG: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
AVG: EUR 5,000 – EUR 10,000,000

+5 more

Bandwidth Waste

€0.67 /mo

9093.4 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~909 KB per page load
Saves €0.67/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 3 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.21 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.69 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.26 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

6.41 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

21.95 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:2347.88799987793 label:Time to first byte subpart:timeToFirstByte] map[duration:236.68700012207032 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-H1

nodeLabel: Highlights en tickets

path: 3,MAIN,0,SECTION,1,DIV,0,A,0,DIV,1,DIV,0,H1

selector: a.block-link > div.block-content > div.block-content-ordered > h1.heading-2

snippet: <h1 class="heading-2">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/statics/generated/rijksmuseum-app.css?v=bauL2fGuHsDKYNfz...	22.5 KiB	308 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
cdn-4.convertexperiments.com/v1/js/10042695-10043546.js?environment=production	300.0 s	86.2 KiB
/signals/config/1002921673111303?v=2.9.303&r=stable&domai...	1200.0 s	46.5 KiB
scripts.clarity.ms/0.8.60-beta/clarity.js	86400.0 s	25.0 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
static.hotjar.com/c/hotjar-1107212.js?sv=7	60.0 s	6.2 KiB
/config/nl/8ebc9c2f-419d-4bd9-b478-1c5fde6061d9.js?v=3.56...	0.0 ms	467 B
/collect?v=2&fmt=js&pid=1424529&time=1776894277273&li_ads...	0.0 ms	270 B
/tr/?id=1002921673111303&ev=PageView&dl=https%3A%2F%2Fwww...	0.0 ms	16 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
a.block-link > div.background-image > picture > img.lazy-image-placeholder `a.block-link > div.background-image > picture > img.lazy-image-placeholder`	/assets/e45e3a0b-61e1-4b22-b4e0-5e0defe985d1?w=20&h=21&fx...	673.5 KiB	673.5 KiB
a.block-link > div.background-image > picture.hidden > img.lazy-image-placeholder `a.block-link > div.background-image > picture.hidden > img.lazy-image-placeholder`	/assets/4ef912c6-338f-4a68-a033-deab0702d0f0?w=20&h=43&fx...	39.3 KiB	39.2 KiB
a.block-link > div.background-image > picture > img.lazy-image-placeholder `a.block-link > div.background-image > picture > img.lazy-image-placeholder`	/assets/d7360324-7a68-4691-817d-e737dd383d81?w=20&h=43&fx...	5.3 KiB	5.2 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.1 s

URL	Time Spent
rijksmuseum.nl/	1.2 s
www.rijksmuseum.nl/	895 ms
www.rijksmuseum.nl/nl	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 945 ms

URL	Time Spent
www.rijksmuseum.nl/nl	1.0 s

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 160 ms 20.4 KiB

URL	Transfer Size	Est Savings
/statics/generated/rijksmuseum-app.css?v=bauL2fGuHsDKYNfz...	22.2 KiB	20.4 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	1.2 s	84 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-TDHW9DQ	764 ms	658 ms	88 ms
www.googletagmanager.com/gtag/js?id=G-CS3DSQ64VQ&cx=c&gtm=4e64k0	570 ms	454 ms	52 ms
www.rijksmuseum.nl/nl	476 ms	19 ms	3.7 ms
cdn-4.convertexperiments.com/v1/js/10042695-10043546.js?environment=production	440 ms	363 ms	40 ms
www.googletagmanager.com/gtag/js?id=G-12345&cx=c&gtm=4e64k0	369 ms	296 ms	68 ms
www.rijksmuseum.nl/statics/generated/vue-router.1d374ba6a02c7388ebe5.mjs	364 ms	326 ms	4.6 ms
scripts.clarity.ms/0.8.60-beta/clarity.js	346 ms	297 ms	16 ms
www.googletagmanager.com/gtag/destination?id=AW-970895607&cx=c&gtm=4e64k0	323 ms	281 ms	39 ms
www.googletagmanager.com/gtag/destination?id=AW-976087125&cx=c&gtm=4e64k0	302 ms	216 ms	35 ms
www.googletagmanager.com/gtag/destination?id=DC-14853655&cx=c&gtm=4e64k0	273 ms	234 ms	35 ms
www.googletagmanager.com/gtag/destination?id=AW-794194365&cx=c&gtm=4e64k0	261 ms	214 ms	42 ms
www.googletagmanager.com/gtag/destination?id=AW-990532474&cx=c&gtm=4e64k0	239 ms	203 ms	32 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	233 ms	181 ms	50 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	227 ms	159 ms	62 ms
sc-static.net/scevent.min.js	208 ms	182 ms	6.6 ms
/statics/generated/rijksmuseum-app.mjs?v=kwVeN3xp5lqUqH9x...	205 ms	145 ms	1.1 ms
connect.facebook.net/en_US/fbevents.js	197 ms	134 ms	62 ms
/signals/config/1002921673111303?v=2.9.303&r=stable&domai...	183 ms	160 ms	21 ms
snap.licdn.com/li.lms-analytics/insight.min.js	72 ms	60 ms	6.1 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js	67 ms	40 ms	26 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	4.8 s
Other	1.5 s
Script Parsing & Compilation	711 ms
Style & Layout	187 ms
Garbage Collection	152 ms
Parse HTML & CSS	124 ms
Rendering	68 ms

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 650.2 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-CS3DSQ64VQ&cx=c&gtm=4e64k0	164.3 KiB	64.2 KiB
www.googletagmanager.com/gtag/destination?id=DC-14853655&cx=c&gtm=4e64k0	129.2 KiB	62.4 KiB
www.googletagmanager.com/gtag/js?id=G-12345&cx=c&gtm=4e64k0	136.6 KiB	60.4 KiB
www.googletagmanager.com/gtag/destination?id=AW-970895607&cx=c&gtm=4e64k0	144.5 KiB	60.1 KiB
www.googletagmanager.com/gtag/destination?id=AW-990532474&cx=c&gtm=4e64k0	133.9 KiB	59.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-794194365&cx=c&gtm=4e64k0	133.9 KiB	59.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-976087125&cx=c&gtm=4e64k0	136.3 KiB	58.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-TDHW9DQ	181.1 KiB	57.2 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	93.3 KiB	53.4 KiB
cdn-4.convertexperiments.com/v1/js/10042695-10043546.js?environment=production	86.0 KiB	45.0 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	37.8 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	32.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/assets/e45e3a0b-61e1-4b22-b4e0-5e0defe985d1?w=20&h=21&fx...	674.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-TDHW9DQ	181.4 KiB
www.googletagmanager.com/gtag/js?id=G-CS3DSQ64VQ&cx=c&gtm=4e64k0	164.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-970895607&cx=c&gtm=4e64k0	144.5 KiB
www.googletagmanager.com/gtag/js?id=G-12345&cx=c&gtm=4e64k0	136.7 KiB
www.googletagmanager.com/gtag/destination?id=AW-976087125&cx=c&gtm=4e64k0	136.4 KiB
www.googletagmanager.com/gtag/destination?id=AW-794194365&cx=c&gtm=4e64k0	133.9 KiB
www.googletagmanager.com/gtag/destination?id=AW-990532474&cx=c&gtm=4e64k0	133.9 KiB
www.googletagmanager.com/gtag/destination?id=DC-14853655&cx=c&gtm=4e64k0	129.2 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	110.0 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Kpn logo `li.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/kpn-logo-white.svg
ING logo `li.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/ing.svg
anbi logo `ul.link-buttons > li.logo-link > a > img.logo-image`	www.rijksmuseum.nl/statics/logos/anbi.svg
Vriendenloterij logo `li.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/vrienden-loterij.svg
Ministerie van Onderwijs, Cultuur en Wetenschap logo `li.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/m-ocw-nl.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 31 user timings

●Avoid long main-thread tasks 20 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 220 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.09 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.48 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

374 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.71 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.38 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
cdn-4.convertexperiments.com/v1/js/10042695-10043546.js?environment=production	300.0 s	86.2 KiB
/signals/config/1002921673111303?v=2.9.303&r=stable&domai...	1200.0 s	46.6 KiB
scripts.clarity.ms/0.8.60-beta/clarity.js	86400.0 s	25.0 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
static.hotjar.com/c/hotjar-1107212.js?sv=7	60.0 s	6.2 KiB
/config/nl/8ebc9c2f-419d-4bd9-b478-1c5fde6061d9.js?v=3.56...	0.0 ms	467 B
/collect?v=2&fmt=js&pid=1424529&time=1776894298003&li_ads...	0.0 ms	273 B
/tr/?id=1002921673111303&ev=PageView&dl=https%3A%2F%2Fwww...	0.0 ms	16 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
a.block-link > div.background-image > picture > img.lazy-image-placeholder `a.block-link > div.background-image > picture > img.lazy-image-placeholder`	/assets/e45e3a0b-61e1-4b22-b4e0-5e0defe985d1?w=20&h=30&fx...	673.7 KiB	673.7 KiB
a.block-link > div.background-image > picture.hidden > img.lazy-image-placeholder `a.block-link > div.background-image > picture.hidden > img.lazy-image-placeholder`	/assets/4ef912c6-338f-4a68-a033-deab0702d0f0?w=20&h=15&fx...	39.1 KiB	39.1 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/statics/generated/rijksmuseum-app.css?v=bauL2fGuHsDKYNfz...	22.5 KiB	82 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 866 ms

URL	Time Spent
rijksmuseum.nl/	646 ms
www.rijksmuseum.nl/	220 ms
www.rijksmuseum.nl/nl	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 20.0 KiB

URL	Transfer Size	Est Savings
/statics/generated/rijksmuseum-app.css?v=bauL2fGuHsDKYNfz...	22.2 KiB	20.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 659.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-CS3DSQ64VQ&cx=c&gtm=4e64k0	164.3 KiB	64.1 KiB
www.googletagmanager.com/gtag/destination?id=DC-14853655&cx=c&gtm=4e64k0	129.1 KiB	62.4 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	108.9 KiB	62.3 KiB
www.googletagmanager.com/gtag/js?id=G-12345&cx=c&gtm=4e64k0	136.5 KiB	61.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-970895607&cx=c&gtm=4e64k0	144.5 KiB	60.1 KiB
www.googletagmanager.com/gtag/destination?id=AW-794194365&cx=c&gtm=4e64k0	133.9 KiB	59.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-976087125&cx=c&gtm=4e64k0	136.3 KiB	59.1 KiB
www.googletagmanager.com/gtag/destination?id=AW-990532474&cx=c&gtm=4e64k0	133.9 KiB	58.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-TDHW9DQ	181.1 KiB	57.2 KiB
cdn-4.convertexperiments.com/v1/js/10042695-10043546.js?environment=production	85.9 KiB	45.0 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	37.6 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	32.7 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/assets/e45e3a0b-61e1-4b22-b4e0-5e0defe985d1?w=20&h=30&fx...	675.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-TDHW9DQ	181.4 KiB
www.googletagmanager.com/gtag/js?id=G-CS3DSQ64VQ&cx=c&gtm=4e64k0	164.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-970895607&cx=c&gtm=4e64k0	144.5 KiB
www.googletagmanager.com/gtag/js?id=G-12345&cx=c&gtm=4e64k0	136.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-976087125&cx=c&gtm=4e64k0	136.4 KiB
www.googletagmanager.com/gtag/destination?id=AW-794194365&cx=c&gtm=4e64k0	133.9 KiB
www.googletagmanager.com/gtag/destination?id=AW-990532474&cx=c&gtm=4e64k0	133.9 KiB
www.googletagmanager.com/gtag/destination?id=DC-14853655&cx=c&gtm=4e64k0	129.2 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	109.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Kpn logo `div.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/kpn-logo-white.svg
Kpn logo `li.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/kpn-logo-white.svg
ING logo `div.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/ing.svg
ING logo `li.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/ing.svg
anbi logo `ul.link-buttons > li.logo-link > a > img.logo-image`	www.rijksmuseum.nl/statics/logos/anbi.svg
Vriendenloterij logo `div.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/vrienden-loterij.svg
Vriendenloterij logo `li.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/vrienden-loterij.svg
Ministerie van Onderwijs, Cultuur en Wetenschap logo `div.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/m-ocw-nl.svg
Ministerie van Onderwijs, Cultuur en Wetenschap logo `li.sponsor-logos-section > div.grid-column > a.logo-link > img.logo-image`	www.rijksmuseum.nl/statics/logos/m-ocw-nl.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Max Potential First Input Delay 130 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 31 user timings

●JavaScript execution time 1.2 s

●Minimizes main-thread work 2.0 s

●Avoid long main-thread tasks 13 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 30 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

100

Accessibility

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://rijksmuseum.nl

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Content (2)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Keyboard Shortcuts