Skip to report
Scan another site

Performance report

dierenvoedselbankspijkenisse.nl

Scanned dierenvoedselbankspijkenisse.nl

  • LiteSpeed
  • WordPress
  • PHP

98 out of 100

Warp Score

A+ Excellent

TTFB — Goodserver response
83 ms
LCP — Goodlab
1.5 s
LCP — Goodlab
0.6 s
INPno field data
—
CLS — Goodlab
0.072
CLS — Goodlab
0.036
Desktop — GoodLighthouse
100
Mobile — GoodLighthouse
98
Transfer
461 KB
Transfer
639 KB
Requests
19
Requests
19
Share on X Share on LinkedIn

Overview

Score breakdown

Performance

A+

99 / 100

Lighthouse scored this page 98 on mobile and 100 on desktop.

Core Web Vitals

— not scored

Not enough Chrome UX Report data is available for this URL.

Server & Cache

A+

100 / 100

HTML is served from cache by LiteSpeed Cache with a warm TTFB of 83 ms.

Assets

A+

95 / 100

461 KB transferred in 19 requests, including 50 KB of JavaScript.

Delivery

A

93 / 100

Delivered with HTTP/2, Brotli compression, no CDN detected.

Top improvements

  1. Eliminate render-blocking resourcesHigh impactPotential savings: 3.5 s

    11 stylesheets and scripts block the first paint.

    Evidence

    • dierenvoedselbankspijkenisse.nl/wp-cont…ca683d268caeefc5c59db2d0d.css?ver=52e0d (601 ms)
    • dierenvoedselbankspijkenisse.nl/wp-cont…ac40bd22baf22efb9f75618e5.css?ver=fb9c4 (601 ms)
    • dierenvoedselbankspijkenisse.nl/wp-cont…s/color-palettes.min.css?ver=1793721367 (451 ms)

    Why it matters

    The browser cannot draw anything until these files are downloaded and processed, which delays FCP and LCP.

    How to fix

    Inline the CSS needed for the first screen and load the rest asynchronously; defer scripts that are not needed to render the page.

    Related metric: LCP

    In Warp PerformanceWarp Performance → CSS → Remove Unused CSSWarp Performance → JavaScript → Defer JavaScript
  2. Reduce unused JavaScriptLow impactPotential savings: 43 KB

    43 KB of downloaded JavaScript was never executed during page load.

    Evidence

    • dierenvoedselbankspijkenisse.nl/wp-cont…d40b78fb24a355d15e23907027.js?ver=6328d (43 KB could be saved)

    Why it matters

    Unused code still has to be downloaded, parsed and compiled, which competes with rendering and slows interaction.

    How to fix

    Load scripts only on the pages that use them, split large bundles, and delay scripts that are not needed until the visitor interacts.

    Related metric: LCP

    In Warp PerformanceWarp Performance → JavaScript → Delay JavaScript
  3. Consider a CDNLow impact

    No CDN was detected in front of this page.

    Evidence

    • No CDN headers were present in the response

    Why it matters

    Without a CDN every visitor connects to one origin location, so distant visitors wait longer for every file.

    How to fix

    Serve static assets, and ideally HTML, through a CDN with locations near your audience.

    In Warp PerformanceWarp Performance → CDN → CDN Integration

Page weight

461 KB transferred · 19 requests · Mobile

  • Images 301 KB 5 requests
  • Fonts 63 KB 1 request
  • JavaScript 50 KB 1 request
  • CSS 25 KB 11 requests
  • HTML 22 KB 1 request

639 KB transferred · 19 requests · Desktop

  • Images 479 KB 5 requests
  • Fonts 63 KB 1 request
  • JavaScript 50 KB 1 request
  • CSS 25 KB 11 requests
  • HTML 22 KB 1 request

Shareable summary

Core Web Vitals

Real-user data shows what visitors actually experienced over the last 28 days. The lab test is a single controlled page load, useful for finding causes. The two often differ, and Google uses the real-user data.

Real users Chrome UX Report · 75th percentile

Not enough Chrome UX Report data is available for this URL.

This is common for newer or lower-traffic pages. It does not lower the Warp Score; the score is calculated from the other categories instead.

Lab test Google Lighthouse · simulated load

Mobile

Lighthouse — Good
98
LCP — Good
1.5 s
FCP — Good
1.1 s
TBT — Good
0 ms
Speed Index — Good
2.9 s
CLS — Good
0.072

Desktop

Lighthouse — Good
100
LCP — Good
0.6 s
FCP — Good
0.3 s
TBT — Good
0 ms
Speed Index — Good
1.1 s
CLS — Good
0.036

Server & Cache

TTFB (server response)
83 ms
HTML cache
LiteSpeed Cache Confirmed
CDN
None detected
Compression
Brotli
HTTP version
HTTP/2 (HTTP/3 advertised)
Server
LiteSpeed
Redirects
None
Browser caching
HTML is revalidated on each visit (ETag / Last-Modified)
Static asset caching
6 of 6 sampled assets cached for 30 days or more

Connection timing from the scanner

DNS
437 ms
TCP
82 ms
TLS
86 ms
First-byte wait
83 ms
Total
333 ms
HTML size
22 KB

Measured from the Warp Scan server, so network times reflect its location rather than your visitors'. The TTFB figure above is the first-byte wait on an open connection (the faster of two requests), so it includes one network round trip from the scanner.

Developer details

Cache evidence

  • x-litespeed-cache: hit (first request)
  • x-litespeed-cache: hit (repeat request)

Response headers (first request)

etag: "4837-1793721644;br"
vary: Accept-Encoding,User-Agent
server: LiteSpeed
content-type: text/html; charset=UTF-8
content-encoding: br
link: <https://dierenvoedselbankspijkenisse.nl/wp-json/>; rel="https://api.w.org/", <https://dierenvoedselbankspijkenisse.nl/wp-json/wp/v2/pages/31>; rel="alternate"; title="JSON"; type="application/json", <https://dierenvoedselbankspijkenisse.nl/>; rel=shortlink
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000
strict-transport-security: max-age=31536000
x-litespeed-cache: hit

Response headers (repeat request, 87 ms)

etag: "4837-1793721644;br"
vary: Accept-Encoding,User-Agent
server: LiteSpeed
content-type: text/html; charset=UTF-8
content-encoding: br
link: <https://dierenvoedselbankspijkenisse.nl/wp-json/>; rel="https://api.w.org/", <https://dierenvoedselbankspijkenisse.nl/wp-json/wp/v2/pages/31>; rel="alternate"; title="JSON"; type="application/json", <https://dierenvoedselbankspijkenisse.nl/>; rel=shortlink
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000
strict-transport-security: max-age=31536000
x-litespeed-cache: hit

Sampled static assets

Asset Cache lifetime Cache-Control
dierenvoedselbankspijkenisse.…9800998ecf8427e.css?ver=5cd8d 1 year public, max-age=31557600
dierenvoedselbankspijkenisse.…a355d15e23907027.js?ver=6328d 1 year public, max-age=31557600
dierenvoedselbankspijkenisse.…/uploads/Middel-1-3x-300.webp 1 year public, max-age=31557600
dierenvoedselbankspijkenisse.…aeefc5c59db2d0d.css?ver=52e0d 1 year public, max-age=31557600
dierenvoedselbankspijkenisse.…t/uploads/Vrijwilligster.webp 1 year public, max-age=31557600
dierenvoedselbankspijkenisse.…9800998ecf8427e.css?ver=670e8 1 year public, max-age=31557600

No server or caching issues found.

JavaScript

50 KB in 1 requests · 11% of page weight · Mobile

50 KB in 1 requests · 8% of page weight · Desktop

  • Eliminate render-blocking resourcesHigh impactPotential savings: 3.5 s

    11 stylesheets and scripts block the first paint.

    Evidence

    • dierenvoedselbankspijkenisse.nl/wp-cont…ca683d268caeefc5c59db2d0d.css?ver=52e0d (601 ms)
    • dierenvoedselbankspijkenisse.nl/wp-cont…ac40bd22baf22efb9f75618e5.css?ver=fb9c4 (601 ms)
    • dierenvoedselbankspijkenisse.nl/wp-cont…s/color-palettes.min.css?ver=1793721367 (451 ms)

    Why it matters

    The browser cannot draw anything until these files are downloaded and processed, which delays FCP and LCP.

    How to fix

    Inline the CSS needed for the first screen and load the rest asynchronously; defer scripts that are not needed to render the page.

    Related metric: LCP

    In Warp PerformanceWarp Performance → CSS → Remove Unused CSSWarp Performance → JavaScript → Defer JavaScript
  • Reduce unused JavaScriptLow impactPotential savings: 43 KB

    43 KB of downloaded JavaScript was never executed during page load.

    Evidence

    • dierenvoedselbankspijkenisse.nl/wp-cont…d40b78fb24a355d15e23907027.js?ver=6328d (43 KB could be saved)

    Why it matters

    Unused code still has to be downloaded, parsed and compiled, which competes with rendering and slows interaction.

    How to fix

    Load scripts only on the pages that use them, split large bundles, and delay scripts that are not needed until the visitor interacts.

    Related metric: LCP

    In Warp PerformanceWarp Performance → JavaScript → Delay JavaScript

CSS

25 KB in 11 requests · 5% of page weight · Mobile

25 KB in 11 requests · 4% of page weight · Desktop

No CSS issues found.

Images

301 KB in 5 requests · 65% of page weight · Mobile

479 KB in 5 requests · 75% of page weight · Desktop

No Images issues found.

Fonts

63 KB in 1 requests · 14% of page weight · Mobile

63 KB in 1 requests · 10% of page weight · Desktop

No Fonts issues found.

Third Parties

0 B from other domains in 0 requests · 0% of page weight

Service Transfer size Requests Main-thread blocking
Google Analytics Referenced in the page; not measured during the test

Headers & Delivery

HTTPS
Yes
HSTS
Enabled
Cache-Control
Not set
Validators
ETag / Last-Modified present
Content-Type
text/html; charset=UTF-8
Vary
Accept-Encoding,User-Agent
  • Consider a CDNLow impact

    No CDN was detected in front of this page.

    Evidence

    • No CDN headers were present in the response

    Why it matters

    Without a CDN every visitor connects to one origin location, so distant visitors wait longer for every file.

    How to fix

    Serve static assets, and ideally HTML, through a CDN with locations near your audience.

    In Warp PerformanceWarp Performance → CDN → CDN Integration

Technology

  • LiteSpeed Detected
    • server: LiteSpeed
    • x-litespeed-cache: hit
  • WordPress Detected
    • Asset paths under /wp-content/
    • REST API discovery link (api.w.org)
    • link: <https://dierenvoedselbankspijkenisse.nl/wp-json/>; rel="https://api.w.org/", <https://dierenvoedselbankspijkenisse.n…
  • PHP Detected
    • Implied by WordPress

WordPress

Theme
bricks-child
REST API
Advertised
Plugins visible in the page
None visible

Optimization tools

  • LiteSpeed Cache Detected LiteSpeed Cache HTML comment · Assets under /wp-content/litespeed/ · LiteSpeed Cache attributes