Skip to report
Scan another site

Performance report

pressemeddelelse.dk

Scanned pressemeddelelse.dk

  • WordPress
  • LiteSpeed
  • PHP

84 out of 100

Warp Score

B Good

TTFB — Needs improvementserver response
451 ms
LCP — Goodlab
1.5 s
LCP — Goodlab
0.5 s
INPno field data
—
CLS — Goodlab
0
CLS — Goodlab
0
Desktop — GoodLighthouse
99
Mobile — GoodLighthouse
100
Transfer
640 KB
Transfer
1.02 MB
Requests
58
Requests
70
Share on X Share on LinkedIn

Overview

Score breakdown

Performance

A+

100 / 100

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

Core Web Vitals

— not scored

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

Server & Cache

D

64 / 100

Page caching could not be determined; the server responded in 451 ms.

Assets

C

79 / 100

640 KB transferred in 58 requests, including 177 KB of JavaScript.

Delivery

B

82 / 100

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

Top improvements

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

    12 stylesheets and scripts block the first paint.

    Evidence

    • pressemeddelelse.dk/wp-content/uploads/…/custom-frontend.min.css?ver=1791020538 (601 ms)
    • pressemeddelelse.dk/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (601 ms)
    • pressemeddelelse.dk/wp-content/themes/voxel/assets/dist/commons.css?ver=1.7.10 (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. Improve static asset cache lifetimeMedium impactPotential savings: 219 KB

    Some CSS, JavaScript or image files tell browsers to cache them only briefly, or not at all.

    Evidence

    • 6 of 6 sampled static assets have a cache lifetime under 30 days
    • pressemeddelelse.dk/wp-content/plu…en.css?ver=0.25.0-localtest-rc14.2 — 7 days
    • pressemeddelelse.dk/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 — not set
    • pressemeddelelse.dk/wp-content/uploads/2026/08/pm-logo.svg — 7 days
    • pressemeddelelse.dk/wp-content/the…assets/dist/commons.css?ver=1.7.10 — 7 days
    • pressemeddelelse.dk/wp-content/plu…ien.js?ver=0.25.0-localtest-rc14.2 — not set
    • pressemeddelelse.dk/wp-content/upl…semeddelelse-JYSK-Logo-300x137.jpg — 7 days
    • Lighthouse flagged 50 resources with a short cache lifetime

    Why it matters

    Returning visitors re-download files that have not changed. Long cache lifetimes make repeat views and page-to-page navigation much faster.

    How to fix

    Serve versioned static files with Cache-Control: public, max-age=31536000, immutable.

  3. Optimize image deliveryMedium impactPotential savings: 141 KB

    Images are larger than they need to be: resizing, recompressing or converting them would save about 141 KB.

    Evidence

    • pressemeddelelse.dk/wp-content/uploads/…or-145-millioner-kroner-i-Aalborg-1.jpg (92 KB could be saved)
    • pressemeddelelse.dk/wp-content/uploads/…e-deler-23-millioner-kroner-768x543.jpg (15 KB could be saved)
    • pressemeddelelse.dk/wp-content/uploads/…enaabner-efter-restaurering-768x512.jpg (13 KB could be saved)

    Why it matters

    Images are usually the largest part of a page and often the LCP element.

    How to fix

    Serve images at the size they are displayed, in WebP or AVIF, with sensible compression.

    Related metric: LCP

    In Warp PerformanceWarp Performance → Media → Local Image OptimizationWarp Performance → Media → Responsive Images
  4. Enable full-page cachingMedium impact

    No evidence of a page cache was found and the server took 451 ms to respond.

    Evidence

    • Server response time: 451 ms
    • No cache status headers were returned

    Why it matters

    Every visitor waits for the server to build the page before anything can render. A page cache serves a stored copy in a few milliseconds, which improves TTFB and everything that follows it, including LCP.

    How to fix

    Turn on full-page caching at the server or CDN so anonymous visitors receive stored HTML, and purge it automatically when content changes.

    Related metric: TTFB

    In Warp PerformanceWarp Performance → Cache → Cache Mode
  5. Reduce unused JavaScriptLow impactPotential savings: 23 KB

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

    Evidence

    • pressemeddelelse.dk/wp-content/themes/v…ssets/vendor/vue/vue.prod.js?ver=3.5.14 (23 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

5 more findings are listed in the other tabs.

Page weight

640 KB transferred · 58 requests · Mobile

  • Images 378 KB 19 requests
  • JavaScript 177 KB 13 requests
  • CSS 48 KB 18 requests
  • HTML 32 KB 1 request
  • Other 6 KB 7 requests

1.02 MB transferred · 70 requests · Desktop

  • Images 780 KB 31 requests
  • JavaScript 177 KB 13 requests
  • CSS 48 KB 18 requests
  • HTML 32 KB 1 request
  • Other 6 KB 7 requests

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
100
LCP — Good
1.5 s
FCP — Good
1.2 s
TBT — Good
4 ms
Speed Index — Good
2.8 s
CLS — Good
0

Desktop

Lighthouse — Good
99
LCP — Good
0.5 s
FCP — Good
0.3 s
TBT — Good
2 ms
Speed Index — Good
1.2 s
CLS — Good
0

Server & Cache

TTFB (server response)
451 ms
HTML cache
Unknown
CDN
None detected
Compression
Brotli
HTTP version
HTTP/2 (HTTP/3 advertised)
Server
LiteSpeed
Redirects
None
Browser caching
HTML is fetched fresh on each visit
Static asset caching
0 of 6 sampled assets cached for 30 days or more

Connection timing from the scanner

DNS
15 ms
TCP
90 ms
TLS
96 ms
First-byte wait
451 ms
Total
677 ms
HTML size
32 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

  • No cache status headers were returned

Response headers (first request)

vary: Accept-Encoding
server: LiteSpeed
content-type: text/html; charset=UTF-8
content-encoding: br
link: <https://pressemeddelelse.dk/wp-json/>; rel="https://api.w.org/", <https://pressemeddelelse.dk/wp-json/wp/v2/pages/130>; rel="alternate"; title="JSON"; type="application/json", <https://pressemeddelelse.dk/>; rel=shortlink
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000
strict-transport-security: max-age=31536000; includeSubDomains; preload

Response headers (repeat request, 481 ms) 

vary: Accept-Encoding
server: LiteSpeed
content-type: text/html; charset=UTF-8
content-encoding: br
link: <https://pressemeddelelse.dk/wp-json/>; rel="https://api.w.org/", <https://pressemeddelelse.dk/wp-json/wp/v2/pages/130>; rel="alternate"; title="JSON"; type="application/json", <https://pressemeddelelse.dk/>; rel=shortlink
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000
strict-transport-security: max-age=31536000; includeSubDomains; preload

Sampled static assets

Asset Cache lifetime Cache-Control
pressemeddelelse.dk/wp-conten…s?ver=0.25.0-localtest-rc14.2 7 days public, max-age=604800
pressemeddelelse.dk/wp-includ…query/jquery.min.js?ver=3.7.1 not set —
pressemeddelelse.dk/wp-content/uploads/2026/08/pm-logo.svg 7 days public, max-age=604800
pressemeddelelse.dk/wp-conten…s/dist/commons.css?ver=1.7.10 7 days public, max-age=604800
pressemeddelelse.dk/wp-conten…s?ver=0.25.0-localtest-rc14.2 not set —
pressemeddelelse.dk/wp-conten…delelse-JYSK-Logo-300x137.jpg 7 days public, max-age=604800
  • Improve static asset cache lifetimeMedium impactPotential savings: 219 KB

    Some CSS, JavaScript or image files tell browsers to cache them only briefly, or not at all.

    Evidence

    • 6 of 6 sampled static assets have a cache lifetime under 30 days
    • pressemeddelelse.dk/wp-content/plu…en.css?ver=0.25.0-localtest-rc14.2 — 7 days
    • pressemeddelelse.dk/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 — not set
    • pressemeddelelse.dk/wp-content/uploads/2026/08/pm-logo.svg — 7 days
    • pressemeddelelse.dk/wp-content/the…assets/dist/commons.css?ver=1.7.10 — 7 days
    • pressemeddelelse.dk/wp-content/plu…ien.js?ver=0.25.0-localtest-rc14.2 — not set
    • pressemeddelelse.dk/wp-content/upl…semeddelelse-JYSK-Logo-300x137.jpg — 7 days
    • Lighthouse flagged 50 resources with a short cache lifetime

    Why it matters

    Returning visitors re-download files that have not changed. Long cache lifetimes make repeat views and page-to-page navigation much faster.

    How to fix

    Serve versioned static files with Cache-Control: public, max-age=31536000, immutable.

  • Enable full-page cachingMedium impact

    No evidence of a page cache was found and the server took 451 ms to respond.

    Evidence

    • Server response time: 451 ms
    • No cache status headers were returned

    Why it matters

    Every visitor waits for the server to build the page before anything can render. A page cache serves a stored copy in a few milliseconds, which improves TTFB and everything that follows it, including LCP.

    How to fix

    Turn on full-page caching at the server or CDN so anonymous visitors receive stored HTML, and purge it automatically when content changes.

    Related metric: TTFB

    In Warp PerformanceWarp Performance → Cache → Cache Mode

JavaScript

177 KB in 13 requests · 28% of page weight · Mobile

177 KB in 13 requests · 17% of page weight · Desktop

  • Eliminate render-blocking resourcesHigh impactPotential savings: 3.9 s

    12 stylesheets and scripts block the first paint.

    Evidence

    • pressemeddelelse.dk/wp-content/uploads/…/custom-frontend.min.css?ver=1791020538 (601 ms)
    • pressemeddelelse.dk/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (601 ms)
    • pressemeddelelse.dk/wp-content/themes/voxel/assets/dist/commons.css?ver=1.7.10 (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: 23 KB

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

    Evidence

    • pressemeddelelse.dk/wp-content/themes/v…ssets/vendor/vue/vue.prod.js?ver=3.5.14 (23 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
  • Minify JavaScriptLow impactPotential savings: 10 KB

    JavaScript files are served unminified; minifying would save about 10 KB.

    Evidence

    • pressemeddelelse.dk/wp-content/plugins/…/cookien.js?ver=0.25.0-localtest-rc14.2 (10 KB could be saved)

    Why it matters

    Whitespace and long names add download and parse time without any benefit to visitors.

    How to fix

    Minify JavaScript as part of the build, or enable minification in your performance plugin.

    In Warp PerformanceWarp Performance → JavaScript → Minify JavaScript

CSS

48 KB in 18 requests · 7% of page weight · Mobile

48 KB in 18 requests · 5% of page weight · Desktop

  • Remove unused CSSLow impactPotential savings: 15 KB

    15 KB of CSS rules are not used by this page.

    Evidence

    • pressemeddelelse.dk/wp-content/themes/v…line-awesome/line-awesome.css?ver=1.3.0 (15 KB could be saved)

    Why it matters

    Stylesheets block rendering, so every unused rule delays the first paint.

    How to fix

    Generate per-page CSS that contains only the rules in use, and load the remainder without blocking rendering.

    Related metric: FCP

    In Warp PerformanceWarp Performance → CSS → Remove Unused CSS
  • Minify CSSLow impactPotential savings: 3 KB

    CSS files are served unminified; minifying would save about 3 KB.

    Evidence

    • pressemeddelelse.dk/wp-content/themes/v…line-awesome/line-awesome.css?ver=1.3.0 (3 KB could be saved)

    Why it matters

    Smaller stylesheets download faster and unblock rendering sooner.

    How to fix

    Minify CSS as part of the build, or enable minification in your performance plugin.

    In Warp PerformanceWarp Performance → CSS → Minify CSS

Images

378 KB in 19 requests · 59% of page weight · Mobile

780 KB in 31 requests · 75% of page weight · Desktop

  • Optimize image deliveryMedium impactPotential savings: 141 KB

    Images are larger than they need to be: resizing, recompressing or converting them would save about 141 KB.

    Evidence

    • pressemeddelelse.dk/wp-content/uploads/…or-145-millioner-kroner-i-Aalborg-1.jpg (92 KB could be saved)
    • pressemeddelelse.dk/wp-content/uploads/…e-deler-23-millioner-kroner-768x543.jpg (15 KB could be saved)
    • pressemeddelelse.dk/wp-content/uploads/…enaabner-efter-restaurering-768x512.jpg (13 KB could be saved)

    Why it matters

    Images are usually the largest part of a page and often the LCP element.

    How to fix

    Serve images at the size they are displayed, in WebP or AVIF, with sensible compression.

    Related metric: LCP

    In Warp PerformanceWarp Performance → Media → Local Image OptimizationWarp Performance → Media → Responsive Images
  • Add width and height to imagesLow impact

    12 images have no explicit dimensions.

    Evidence

    • pressemeddelelse.dk/wp-content/uploads/…o/Pressemeddelelse-DSB-Logo-300x269.png
    • pressemeddelelse.dk/wp-content/uploads/…lelse-Billund-Lufthavn-Logo-300x153.png
    • pressemeddelelse.dk/wp-content/uploads/…/Pressemeddelelse-JYSK-Logo-300x137.jpg

    Why it matters

    Without dimensions the browser cannot reserve space, so content jumps when the image arrives. That movement is measured as CLS.

    How to fix

    Set width and height attributes (or a CSS aspect-ratio) on every image.

    Related metric: CLS

    In Warp PerformanceWarp Performance → Media → Add Missing Dimensions

Fonts

0 B in 0 requests · 0% of page weight · Mobile

0 B in 0 requests · 0% of page weight · Desktop

No Fonts issues found.

Third Parties

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

No common third-party services were detected.

Headers & Delivery

HTTPS
Yes
HSTS
Enabled
Cache-Control
Not set
Validators
None
Content-Type
text/html; charset=UTF-8
Vary
Accept-Encoding
  • 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

  • WordPress Detected
    • Asset paths under /wp-content/
    • Asset paths under /wp-includes/
    • REST API discovery link (api.w.org)
    • Generator meta tag: WordPress
    • link: <https://pressemeddelelse.dk/wp-json/>; rel="https://api.w.org/", <https://pressemeddelelse.dk/wp-json/wp/v2/pages/13…
  • LiteSpeed Detected
    • server: LiteSpeed
  • PHP Detected
    • Implied by WordPress
  • Vue Likely detected
    • Vue runtime script

WordPress

Theme
voxel
REST API
Advertised
Plugins visible in the page
3 plugins

Optimization tools

Unable to determine. No optimization plugin exposed itself in the page or its headers.

Plugins referenced by asset paths

elementor cookien seo-by-rank-math-pro