Tested 2026-06-18 15:42:50 using Chrome 149.0.7827.53 (runtime settings)
Use --filmstrip.showAll to show all filmstrips.
0 s0.2 sLayout Shift 0.65185 164 msFirst Contentful Paint 167 msLCP <IMG> 167 msCPU Long Task duration 75 ms
0.3 sFirst Visual Change 234 msDOM Content Loaded Time 250 msPage Load Time 253 ms
0.4 s
0.5 s
0.6 sLast Visual Change 534 msVisual Complete 85% 534 msVisual Complete 95% 534 msVisual Complete 99% 534 msThe coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices. Tested using Coach-core version 9.2.1.
modernImageFormatsThe page ships 14 images (out of 14) in JPEG/PNG/GIF without a modern alternative. Wrap them in a <picture> with a <source type="image/avif"> or "image/webp" before the legacy <img>, or serve modern formats from your image pipeline directly. AVIF and WebP usually deliver 25–50% smaller files at the same quality.
AVIF and WebP routinely deliver 25–50% smaller files than JPEG and PNG at the same perceived quality, and every browser version still under support understands at least one of them. Ship modern formats either through a <picture> element with <source type="image/avif"> / "image/webp" entries in front of the legacy <img>, or directly from a content-negotiating image pipeline that returns AVIF / WebP when the client accepts it. https://web.dev/articles/serve-images-webp
cssSizeThe total CSS transfer size is 159.4 kB and uncompressed size is 873.6 kB. That is big and the CSS could most probably be smaller.
Delivering a massive amount of CSS to the browser is not the best thing you can do, because it means more work for the browser when parsing the CSS against the HTML and that makes the rendering slower. Try to send only the CSS that is used on that page. And make sure to remove CSS rules when they aren't used anymore.
javascriptSizeThe total JavaScript transfer size is 253.5 kB and the uncompressed size is 897.9 kB. This is quite large.
A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks?
| URL | Transfer | Content |
|---|---|---|
| https://nvkgoudsmederij.nl/wp-content/litespeed/js/ccb38df1eda8aad0eb9551fe867070e6.js?ver=c93f5 | 247.5 KB | 876.9 KB |
pageSizeThe page total transfer size is 4.8 MB, which is more than the coach limit of 3 MB. That is really big and you need to make it smaller.
Avoid having pages that have a transfer size over the wire of more than 3 MB (desktop) and 2 MB (mobile) because heavy pages hurt performance and are expensive for users on metered connections. Reference: HTTP Archive median page weight in 2024 was around 2.7 MB desktop / 2.4 MB mobile, so this rule fires when a page is above the modern median.
fewFontsThe page has 5 font requests. Do you really need them? What value does the fonts give the user?
How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive.
imageSizeThe page total image size is 4.3 MB. It's really big. Is the page using the right format for the images? Can they be lazy loaded? Are they compressed as good as they can be? Make them smaller by using https://imageoptim.com/.
Avoid having too many large images on the page. The images will not affect the first paint of the page, but it will eat bandwidth for the user.
avoidScalingImagesThe page has 4 images that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them.
It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one.
decodingAsyncThe page has 5 images (out of 14) without a decoding hint. Add decoding="async" to non-critical images so the browser can decode them off the main thread.
Setting decoding="async" on an <img> tells the browser it can decode the image off the main thread, which keeps the page responsive to user interactions while images are being processed. The default ("auto") leaves the choice to the browser. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#decoding
lazyLoadingImagesThe page has 2 below-the-fold images without loading="lazy". Add loading="lazy" so the browser defers downloading and decoding them until the user scrolls them into view.
Adding loading="lazy" to an <img> tells the browser not to download or decode it until it is close to the viewport. For images that the user may never see (deep in the page, behind a tab, in a footer carousel), this saves bandwidth and main-thread time during initial render. The LCP image and any image in the initial viewport should NOT be lazy-loaded — that delays the first paint. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#loading
longTasksThe page has 1 CPU long task with the total of 75 ms. The total blocking time is 25 ms . However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks.
Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler.
optimalCssSizehttps://nvkgoudsmederij.nl/wp-content/litespeed/css/af69793475a82663389c17edb589ac91.css?ver=c93f5 size is 156.2 kB (156205) and that is bigger than the limit of 25 kB. Try to keep each CSS response under 25 kB.
Render-blocking CSS holds up the first paint until it has fully downloaded, parsed and applied, so smaller CSS files mean a faster start. Split your CSS into a small critical bundle inlined or eagerly loaded, with the rest lazy-loaded.
| URL | Transfer | Content |
|---|---|---|
| https://nvkgoudsmederij.nl/wp-content/litespeed/css/af69793475a82663389c17edb589ac91.css?ver=c93f5 | 152.5 KB | 844.0 KB |
privateAssetsThe page has 1 request with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone.
If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private.
inlineCssThe page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens.
In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded.
cacheHeadersLongThe page has 5 requests that have a shorter cache time than one year (but still a cache time).
Setting a cache header is good. Setting a long cache header (a year) is even better because the asset will stay in the browser cache across visits. For content-hashed URLs (e.g. app.4af2.css) you can safely use Cache-Control: max-age=31536000, immutable. For unversioned URLs that may change, use a revalidating strategy instead.
cumulativeLayoutShiftYou have a poor cumulative layout shift score (0.6519). It is in the Google Web Vitals poor range, with a shift higher than 0.25. You should manually check the filmstrip or video and check if it will affect the user.
Cumulative Layout Shift measures the sum total of all individual layout shift scores for unexpected layout shift that occur. The metric is measuring visual stability by quantify how often users experience unexpected layout shifts. It is one of Google Web Vitals.
metaDescriptionThe page is missing a meta description.
Use a page description to make the page more relevant to search engines.
unnecessaryHeadersThere are 26 responses that sets both a max-age and expires header. There are 1 response that sets a pragma no-cache header (that is a request header). There are 27 responses that sets a server header.
Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.
imageAltTextThe page has 3 images without an alt attribute. Add alt="..." with a description, or alt="" if the image is purely decorative.
Every <img> needs an alt attribute. Use alt="meaningful description" for content images so assistive technologies can announce them, or alt="" (or role="presentation" / aria-hidden="true") for purely decorative images so they are skipped. A missing alt attribute leaves screen reader users with no information at all. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#alt
viewportThe viewport meta tag sets maximum-scale to 1 or less, which prevents the user from zooming in. Remove it.
The viewport meta tag tells the browser how to lay out the page on small screens. Without it (or without width=device-width) the page is rendered at a desktop fallback width and scaled down, which makes text unreadable on mobile. Disabling zoom (user-scalable=no, maximum-scale<=1) is also an accessibility regression. https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag
referrerPolicyNo <meta name="referrer"> tag was found on the page. Set a Referrer-Policy response header (preferred) or add a meta tag, for example <meta name="referrer" content="strict-origin-when-cross-origin">.
Without an explicit referrer policy the browser falls back to the user-agent default and may leak the full URL of the previous page (including query strings) to every cross-origin request. Set a Referrer-Policy response header (preferred) or a <meta name="referrer"> tag in the document. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy
nelHeaderSet a NEL header (paired with Reporting-Endpoints) to collect connection-level error reports from the field.
The NEL (Network Error Logging) response header tells the browser to record connection-level failures (DNS, TLS, HTTP errors) and ship them to a reporting endpoint. NEL pairs with the Reporting-Endpoints / Report-To header — the page declares the endpoint group and NEL points at it. Together they give you visibility into errors that never reach your origin server. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/NEL
permissionsPolicyHeaderSet a Permissions-Policy header to control which browser features the page can use.
The Permissions-Policy response header (the successor to Feature-Policy) lets a site explicitly opt in or out of powerful browser features such as camera, microphone, geolocation, payment and clipboard. Setting a strict policy reduces the attack surface and limits what embedded third parties can do. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
reportingEndpointsHeaderSet a Reporting-Endpoints header (or the legacy Report-To header) so CSP reports, NEL data and other Reporting-API events have an endpoint to land at.
The Reporting-Endpoints response header (the successor to Report-To) names the URLs that browsers should POST reports to. Without it, CSP report-to directives, Cross-Origin-Opener-Policy reports, NEL data and other Reporting-API events have nowhere to go. The legacy Report-To header is still accepted for older Chromium versions. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Reporting-Endpoints
thirdPartyPrivacyThe page has 7% requests that are 3rd party (2 requests with a size of 9 kB). The page also have request to companies that harvest data from users and do not respect users privacy (see https://en.wikipedia.org/wiki/Surveillance_capitalism). The page do 2 surveillance requests and uses 1 surveillance tool.
Using third party requests shares user information with that third party. Please avoid that! The project https://github.com/patrickhulce/third-party-web is used to categorize first/third party requests.
contentSecurityPolicyHeaderThe policy declares no default-src or script-src directive, which means scripts can be loaded from anywhere. Add at least default-src so unknown directive types fall back to a safe value. Set object-src 'none' (or a default-src 'none' fallback) so the page cannot load Flash, plugins or other legacy embeddable content. The policy declares no default-src or script-src directive, which means scripts can be loaded from anywhere. Add at least default-src so unknown directive types fall back to a safe value. Set object-src 'none' (or a default-src 'none' fallback) so the page cannot load Flash, plugins or other legacy embeddable content.
A Content-Security-Policy response header tells the browser which sources of script, style, and other content are allowed. The most effective form is a strict CSP using nonces or hashes together with strict-dynamic; the worst is a missing header, with unsafe-inline and unsafe-eval close behind. https://web.dev/articles/strict-csp
Data collected using
Coach-core version 9.2.1. With updated code from
Webappanalyzer 2026-05-04. Use
--browsertime.firefox.includeResponseBodies html or
--browsertime.chrome.includeResponseBodies html to help Wappalyzer find more information about technologies used.
Data collected using Third Party Web version 0.29.2.
0.0s0.2s0.3s0.4s0.5s0.6sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div#Wrapper > div#Content > div > main > div > div > section:eq(1) > div:eq(1) > div:eq(1) > div > div:eq(1) > div > div > div > img
The LCP element is highlighted in the screenshot. If nothing is highlighted the element was removed before the screenshot or the LCP API couldn't find it.
The Largest Contentful Paint API matched this image:
How much the page's content shifts as it loads, collected via the Cumulative Layout Shift API.
Sorted by individual shift score (higher = bigger shift). The top entries usually account for most of the page's CLS.
body > div#Wrapper > div#Content
Elements that shifted by more than 0.01 are highlighted in the screenshot. If an element shifted outside the viewport, it won't appear here — check the video or filmstrip to see the shift.
Want render-blocking and recalculate-style metrics for FCP and LCP, plus CPU long tasks? Run with --cpu.
A long animation frame (LOAF) is a frame that took ≥ 50 ms from input to the next paint. The breakdown shows where that time went. Read more about the Long Animation Frames API.
Showing the top 10 longest animation frames.
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 59.9 KB | 200.3 KB | 3 |
| css | 0 b | 155.7 KB | 853.1 KB | 5 |
| javascript | 0 b | 247.5 KB | 876.9 KB | 1 |
| image | 0 b | 4.1 MB | 4.1 MB | 13 |
| font | 0 b | 39.5 KB | 39.2 KB | 5 |
| Total | 0 b | 4.6 MB | 6.0 MB | 27 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| nvkgoudsmederij.nl | 633 ms | 4.6 MB | 6.0 MB | 25 |
| fonts.googleapis.com | 41 ms | 1.1 KB | 2.8 KB | 1 |
| fonts.gstatic.com | 4 ms | 7.7 KB | 7.6 KB | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 year | 1 year |
| Last modified | 0 seconds | 2 hours | 4 years |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 1.7 KB | 2 |
| javascript | 0 b | 0 |
| image | 2.0 MB | 2 |
| font | 7.7 KB | 1 |
| favicon | 0 b | 0 |
| Total | 2.0 MB | 5 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 1.7 KB | 2 |
| javascript | 0 b | 0 |
| image | 2.0 MB | 2 |
| font | 7.7 KB | 1 |
| favicon | 0 b | 0 |
| Total | 2.0 MB | 5 |
Render blocking information directly from Chrome.
| Blocking | In body parser blocking | Potentially blocking |
|---|---|---|
| 1 | 0 | 0 |
| URL | Type |
|---|---|
| https://nvkgoudsmede...9551fe867070e6.js | nonblocking |
| https://nvkgoudsmede...c17edb589ac91.css | blocking |
| https://nvkgoudsmede...talic-latin.woff2 | nonblocking |
| https://nvkgoudsmede...s-600-latin.woff2 | nonblocking |
| https://nvkgoudsmede...s-400-latin.woff2 | nonblocking |
| https://fonts.gstati...rLDD4Z1xlFQ.woff2 | nonblocking |
| https://nvkgoudsmede...s-500-latin.woff2 | nonblocking |
| https://nvkgoudsmede...ic/css/sr7.lp.css | nonblockingdynamic |
| https://fonts.google...ogleapis.com/css2 | inbodyparserblocking |
| https://nvkgoudsmede...css/sr7.media.css | nonblockingdynamic |
| https://nvkgoudsmede...preloaders/t2.css | nonblockingdynamic |
Third party requests categorised by Third party web version 0.29.2.
Calculated using .*nvkgoudsmederij.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 59.9 KB | 200.3 KB | 3 |
| css | 0 b | 154.6 KB | 850.3 KB | 4 |
| javascript | 0 b | 247.5 KB | 876.9 KB | 1 |
| image | 0 b | 4.1 MB | 4.1 MB | 13 |
| font | 0 b | 31.9 KB | 31.5 KB | 4 |
| favicon | 0 b | 0 b | 0 b | 0 |
| Total | N/A | 4.6 MB | 6.0 MB | 25 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 0 |
| css | 0 b | 1.1 KB | 2.8 KB | 1 |
| javascript | 0 b | 0 b | 0 b | 0 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 7.7 KB | 7.6 KB | 1 |
| favicon | 0 b | 0 b | 0 b | 0 |
| Total | N/A | 8.8 KB | 10.5 KB | 2 |
