Performance report
duramat.co.uk
- LiteSpeed
- WordPress
- PHP
- WooCommerce
83 out of 100
Warp Score
B Good
- TTFB — Goodserver response
- 104 ms
- LCP — Needs improvementlab
- 3.2 s
- LCP — Goodlab
- 0.8 s
- INP — Goodreal users
- 133 ms
- CLS — Goodlab
- 0.034
- CLS — Goodlab
- 0.004
- Desktop — GoodLighthouse
- 93
- Mobile — Needs improvementLighthouse
- 74
- Transfer
- 1.25 MB
- Transfer
- 1.3 MB
- Requests
- 34
- Requests
- 37
Overview
Score breakdown
Performance
B82 / 100
Lighthouse scored this page 74 on mobile and 93 on desktop.
Core Web Vitals
A91 / 100
Real visitors pass Core Web Vitals on this page, with a 75th-percentile LCP of 2.4 s.
Server & Cache
A90 / 100
HTML is served from cache by LiteSpeed Cache with a warm TTFB of 104 ms.
Assets
D68 / 100
1.25 MB transferred in 34 requests, including 754 KB of JavaScript.
Delivery
B82 / 100
Delivered with HTTP/2, Gzip compression, no CDN detected.
Top improvements
Eliminate render-blocking resources
6 stylesheets and scripts block the first paint.
Evidence
- duramat.co.uk/wp-content/litespeed/css/…f187051912cf4217236551444.css?ver=0e4ad (2 s)
- duramat-co-uk.b-cdn.net/wp-content/themes/flatsome/assets/css/flatsome.css (1.5 s)
- duramat-co-uk.b-cdn.net/wp-includes/css/dashicons.min.css (1.5 s)
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 JavaScriptReduce the impact of third-party code
Scripts and resources from other companies account for 1.01 MB of this page.
Evidence
- Third-party code: 1.01 MB (81% of page weight) across 28 requests
- www.googletagmanager.com — 526 KB
- connect.facebook.net — 228 KB
- duramat-co-uk.b-cdn.net — 205 KB
Why it matters
Tags, widgets and embeds run on the same main thread as your own code and are outside your control. They are a common cause of slow interaction.
How to fix
Remove tags that are no longer used, load the rest after the first interaction, and replace heavy embeds (video, maps, chat) with a lightweight placeholder that loads on click.
Related metric: TBT
In Warp PerformanceWarp Performance → JavaScript → Delay JavaScriptReduce unused JavaScript
288 KB of downloaded JavaScript was never executed during page load.
Evidence
- www.googletagmanager.com/gtag/js?id=G-8YEVK4ZZBS (74 KB could be saved)
- www.googletagmanager.com/gtm.js?id=GTM-PXWMD94 (71 KB could be saved)
- www.googletagmanager.com/gtag/js?id=AW-1071964201&cx=c>m=4e6b41 (68 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 JavaScriptRemove unused CSS
126 KB of CSS rules are not used by this page.
Evidence
- duramat.co.uk/wp-content/litespeed/css/…f187051912cf4217236551444.css?ver=0e4ad (66 KB could be saved)
- duramat-co-uk.b-cdn.net/wp-includes/css/dashicons.min.css (34 KB could be saved)
- duramat-co-uk.b-cdn.net/wp-content/themes/flatsome/assets/css/flatsome.css (26 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 CSSDelay non-critical JavaScript
JavaScript kept the main thread busy for 477 ms while the page was loading.
Evidence
- Total Blocking Time: 477 ms
Why it matters
While scripts run, the page cannot respond to taps or clicks. High blocking time is the main cause of poor INP and a sluggish first interaction.
How to fix
Delay scripts that are not required for initial rendering (analytics, chat widgets, ads, social embeds) until the first user interaction.
Related metric: TBT
In Warp PerformanceWarp Performance → JavaScript → Delay JavaScript
5 more findings are listed in the other tabs.
Page weight
1.25 MB transferred · 34 requests · Mobile
- JavaScript 754 KB 5 requests
- Fonts 163 KB 5 requests
- CSS 152 KB 6 requests
- HTML 90 KB 1 request
- Other 72 KB 12 requests
- Images 53 KB 5 requests
1.3 MB transferred · 37 requests · Desktop
- JavaScript 754 KB 5 requests
- Fonts 184 KB 6 requests
- CSS 152 KB 6 requests
- HTML 90 KB 1 request
- Images 76 KB 6 requests
- Other 72 KB 13 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
Passes Core Web VitalsMobile visitors · data for this page
- LCP p75 — Good
- 2.4 s
- INP p75 — Good
- 133 ms
- CLS p75 — Good
- 0
- TTFB p75 — Needs improvement
- 1.5 s
- FCP p75 — Good
- 1.8 s
Desktop visitors · data for this page
- LCP p75 — Needs improvement
- 2.5 s
- INP p75 — Good
- 59 ms
- CLS p75 — Good
- 0.02
- TTFB p75 — Needs improvement
- 1.6 s
- FCP p75 — Needs improvement
- 2.0 s
Lab test Google Lighthouse · simulated load
Mobile
- Lighthouse — Needs improvement
- 74
- LCP — Needs improvement
- 3.2 s
- FCP — Poor
- 3.2 s
- TBT — Needs improvement
- 477 ms
- Speed Index — Good
- 3.2 s
- CLS — Good
- 0.034
Desktop
- Lighthouse — Good
- 93
- LCP — Good
- 0.8 s
- FCP — Good
- 0.8 s
- TBT — Needs improvement
- 202 ms
- Speed Index — Good
- 0.8 s
- CLS — Good
- 0.004
Server & Cache
- TTFB (server response)
- 104 ms
- HTML cache
- LiteSpeed Cache Confirmed
- CDN
- None detected
- Compression
- Gzip
- HTTP version
- HTTP/2 (HTTP/3 advertised)
- Server
- LiteSpeed
- Redirects
- None
- Browser caching
- HTML is fetched fresh on each visit
- Static asset caching
- 3 of 6 sampled assets cached for 30 days or more
Connection timing from the scanner
- DNS
- 77 ms
- TCP
- 104 ms
- TLS
- 109 ms
- First-byte wait
- 104 ms
- Total
- 527 ms
- HTML size
- 88 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)
vary: Accept-Encoding
server: LiteSpeed
content-type: text/html; charset=UTF-8
content-encoding: gzip
content-length: 90592
link: <https://duramat.co.uk/wp-json/>; rel="https://api.w.org/", <https://duramat.co.uk/wp-json/wp/v2/pages/66>; rel="alternate"; title="JSON"; type="application/json", <https://duramat.co.uk/>; rel=shortlink
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"
strict-transport-security: max-age=31536000
x-litespeed-cache: hit
Response headers (repeat request, 104 ms)
vary: Accept-Encoding
server: LiteSpeed
content-type: text/html; charset=UTF-8
content-encoding: gzip
content-length: 90592
link: <https://duramat.co.uk/wp-json/>; rel="https://api.w.org/", <https://duramat.co.uk/wp-json/wp/v2/pages/66>; rel="alternate"; title="JSON"; type="application/json", <https://duramat.co.uk/>; rel=shortlink
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"
strict-transport-security: max-age=31536000
x-litespeed-cache: hit
Sampled static assets
| Asset | Cache lifetime | Cache-Control |
|---|---|---|
| duramat.co.uk/wp-content/lite…cf4217236551444.css?ver=0e4ad | 365 days | public, max-age=31535990 |
| duramat.co.uk/wp-content/plug…ssets/js/frontend-gtag.min.js | not set | — |
| duramat.co.uk/wp-content/uploads/google-review.png | 365 days | public, max-age=31535990 |
| duramat.co.uk/wp-content/plug…d/gtm4wp-ecommerce-generic.js | not set | — |
| duramat.co.uk/wp-content/plug…-feed-pro/img/placeholder.png | 365 days | public, max-age=31535990 |
| duramat.co.uk/wp-content/plug…r/build/gtm4wp-woocommerce.js | not set | — |
Improve static asset cache lifetime
Some CSS, JavaScript or image files tell browsers to cache them only briefly, or not at all.
Evidence
- 3 of 6 sampled static assets have a cache lifetime under 30 days
- duramat.co.uk/wp-content/plugins/g…ium/assets/js/frontend-gtag.min.js — not set
- duramat.co.uk/wp-content/plugins/d…/build/gtm4wp-ecommerce-generic.js — not set
- duramat.co.uk/wp-content/plugins/d…anager/build/gtm4wp-woocommerce.js — not set
- Lighthouse flagged 2 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.
JavaScript
754 KB in 5 requests · 59% of page weight · Mobile
754 KB in 5 requests · 57% of page weight · Desktop
Eliminate render-blocking resources
6 stylesheets and scripts block the first paint.
Evidence
- duramat.co.uk/wp-content/litespeed/css/…f187051912cf4217236551444.css?ver=0e4ad (2 s)
- duramat-co-uk.b-cdn.net/wp-content/themes/flatsome/assets/css/flatsome.css (1.5 s)
- duramat-co-uk.b-cdn.net/wp-includes/css/dashicons.min.css (1.5 s)
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 JavaScriptReduce unused JavaScript
288 KB of downloaded JavaScript was never executed during page load.
Evidence
- www.googletagmanager.com/gtag/js?id=G-8YEVK4ZZBS (74 KB could be saved)
- www.googletagmanager.com/gtm.js?id=GTM-PXWMD94 (71 KB could be saved)
- www.googletagmanager.com/gtag/js?id=AW-1071964201&cx=c>m=4e6b41 (68 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 JavaScriptDelay non-critical JavaScript
JavaScript kept the main thread busy for 477 ms while the page was loading.
Evidence
- Total Blocking Time: 477 ms
Why it matters
While scripts run, the page cannot respond to taps or clicks. High blocking time is the main cause of poor INP and a sluggish first interaction.
How to fix
Delay scripts that are not required for initial rendering (analytics, chat widgets, ads, social embeds) until the first user interaction.
Related metric: TBT
In Warp PerformanceWarp Performance → JavaScript → Delay JavaScriptStop sending legacy JavaScript to modern browsers
About 13 KB of polyfills and transpiled code targets browsers that no longer need it.
Evidence
- connect.facebook.net/en_US/fbevents.js (13 KB could be saved)
Why it matters
Modern browsers download and run compatibility code they never use.
How to fix
Update the build target (browserslist) to current browsers and remove unnecessary polyfills.
CSS
152 KB in 6 requests · 12% of page weight · Mobile
152 KB in 6 requests · 11% of page weight · Desktop
Remove unused CSS
126 KB of CSS rules are not used by this page.
Evidence
- duramat.co.uk/wp-content/litespeed/css/…f187051912cf4217236551444.css?ver=0e4ad (66 KB could be saved)
- duramat-co-uk.b-cdn.net/wp-includes/css/dashicons.min.css (34 KB could be saved)
- duramat-co-uk.b-cdn.net/wp-content/themes/flatsome/assets/css/flatsome.css (26 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
Images
53 KB in 5 requests · 4% of page weight · Mobile
76 KB in 6 requests · 6% of page weight · Desktop
No Images issues found.
Fonts
163 KB in 5 requests · 13% of page weight · Mobile
184 KB in 6 requests · 14% of page weight · Desktop
Keep text visible while fonts load
1 web font hides text until it has loaded.
Evidence
- maxcdn.bootstrapcdn.com/font-awesome/4.…fonts/fontawesome-webfont.woff2?v=4.5.0 (35 ms)
Why it matters
Visitors see blank space where text should be until the font arrives, which delays FCP and can delay LCP.
How to fix
Use font-display: swap (or optional) so text renders immediately in a fallback font.
Related metric: FCP
In Warp PerformanceWarp Performance → Fonts → Font Display Swap
Third Parties
1.01 MB from other domains in 28 requests · 81% of page weight
| Service | Transfer size | Requests | Main-thread blocking |
|---|---|---|---|
| Google Ads | 188 KB | 1 | — |
| Google Analytics | 181 KB | 3 | — |
| Google Tag Manager | 159 KB | 1 | — |
| Meta Pixel | 115 KB | 2 | — |
| Google AdSense | 2 KB | 3 | — |
| YouTube | Referenced in the page; not measured during the test | ||
| Google reCAPTCHA | Referenced in the page; not measured during the test | ||
Reduce the impact of third-party code
Scripts and resources from other companies account for 1.01 MB of this page.
Evidence
- Third-party code: 1.01 MB (81% of page weight) across 28 requests
- www.googletagmanager.com — 526 KB
- connect.facebook.net — 228 KB
- duramat-co-uk.b-cdn.net — 205 KB
Why it matters
Tags, widgets and embeds run on the same main thread as your own code and are outside your control. They are a common cause of slow interaction.
How to fix
Remove tags that are no longer used, load the rest after the first interaction, and replace heavy embeds (video, maps, chat) with a lightweight placeholder that loads on click.
Related metric: TBT
In Warp PerformanceWarp Performance → JavaScript → Delay JavaScript
Headers & Delivery
- HTTPS
- Yes
- HSTS
- Enabled
- Cache-Control
- Not set
- Validators
- None
- Content-Type
- text/html; charset=UTF-8
- Vary
- Accept-Encoding
Reduce the size of the DOM
The page contains 3,386 HTML elements.
Evidence
- DOM elements: 3,386
Why it matters
Large documents make style calculation, layout and every interaction slower.
How to fix
Simplify page-builder nesting, paginate long lists, and render off-screen sections only when they are needed.
Related metric: INP
Consider a CDN
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/
- Asset paths under /wp-includes/
- REST API discovery link (api.w.org)
- Generator meta tag: WordPress
- link: <https://duramat.co.uk/wp-json/>; rel="https://api.w.org/", <https://duramat.co.uk/wp-json/wp/v2/pages/66>; rel="alte…
-
PHP Detected
- Implied by WordPress
-
WooCommerce Detected
- WooCommerce body class
- WooCommerce script data
-
React Likely detected
- React runtime script
WordPress
- Theme
- flatsome
- REST API
- Advertised
- Plugins visible in the page
- 8 plugins
Optimization tools
- LiteSpeed Cache Detected LiteSpeed Cache HTML comment · Assets under /wp-content/litespeed/ · Assets under /plugins/litespeed-cache/
Plugins referenced by asset paths
reviews-feed-pro
instagram-feed-pro
duracelltomi-google-tag-manager
google-analytics-premium
wpforms
wpconsent-cookies-banner-privacy-suite
yith-woocommerce-advanced-product-options-premium
litespeed-cache