Skip to report
Scan another site

Performance report

chadbotha.com

Scanned chadbotha.com

  • WordPress
  • LiteSpeed
  • PHP
  • Cloudflare

90 out of 100

Warp Score

A Excellent

TTFB — Needs improvementserver response
228 ms
LCP — Goodlab
1.1 s
LCP — Goodlab
0.3 s
INPno field data
—
CLS — Goodlab
0
CLS — Goodlab
0
Desktop — GoodLighthouse
100
Mobile — GoodLighthouse
99
Transfer
597 KB
Transfer
597 KB
Requests
42
Requests
42
Share on X Share on LinkedIn

Overview

Score breakdown

Performance

A+

99 / 100

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

Core Web Vitals

— not scored

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

Server & Cache

C

76 / 100

No page cache was detected; the server took 228 ms to respond.

Assets

B

86 / 100

597 KB transferred in 42 requests, including 262 KB of JavaScript.

Delivery

A+

100 / 100

Delivered with HTTP/2, Zstandard compression, Cloudflare.

Top improvements

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

    4 stylesheets and scripts block the first paint.

    Evidence

    • chadbotha.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (842 ms)
    • chadbotha.com/wp-content/uploads/wpcodebox/159.css?v=17a808c13aa3c4e2 (506 ms)
    • chadbotha.com/wp-content/cache/xspeed/min/7298e5807899c4948db897166ae7b24d.js (506 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 JavaScriptMedium impactPotential savings: 90 KB

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

    Evidence

    • cdn.iubenda.com/cookie_solution/iubenda_cs/1.109.0/core-en-GB.js (44 KB could be saved)
    • d.plerdy.com/public/js/tracker/core.js?v=2306a983d4 (25 KB could be saved)
    • chadbotha.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (21 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. Reduce the impact of third-party codeMedium impact

    Scripts and resources from other companies account for 231 KB of this page.

    Evidence

    • Third-party code: 231 KB (39% of page weight) across 18 requests
    • cdn.iubenda.com — 131 KB
    • d.plerdy.com — 72 KB
    • cs.iubenda.com — 15 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
  4. Stop sending legacy JavaScript to modern browsersLow impactPotential savings: 50 KB

    About 50 KB of polyfills and transpiled code targets browsers that no longer need it.

    Evidence

    • cdn.iubenda.com/iubenda.js (13 KB could be saved)
    • cdn.iubenda.com/iubenda.js (13 KB could be saved)
    • cdn.iubenda.com/iubenda.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.

  5. Remove unused CSSLow impactPotential savings: 24 KB

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

    Evidence

    • chadbotha.com/wp-content/cache/xspeed/min/f52f810d2ddda72252b13f7e87d6bb04.css (24 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

1 more finding is listed in the other tabs.

Page weight

597 KB transferred · 42 requests · Mobile

  • JavaScript 262 KB 18 requests
  • Fonts 157 KB 8 requests
  • CSS 78 KB 11 requests
  • Images 68 KB 1 request
  • HTML 30 KB 1 request
  • Other 2 KB 3 requests

597 KB transferred · 42 requests · Desktop

  • JavaScript 262 KB 18 requests
  • Fonts 157 KB 8 requests
  • CSS 78 KB 11 requests
  • Images 68 KB 1 request
  • HTML 30 KB 1 request
  • Other 2 KB 3 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
99
LCP — Good
1.1 s
FCP — Good
1.1 s
TBT — Good
35 ms
Speed Index — Good
3.3 s
CLS — Good
0

Desktop

Lighthouse — Good
100
LCP — Good
0.3 s
FCP — Good
0.3 s
TBT — Good
5 ms
Speed Index — Good
1.0 s
CLS — Good
0

Server & Cache

TTFB (server response)
228 ms
HTML cache
Not detected
CDN
Cloudflare HTML caching: Not detected
Compression
Zstandard
HTTP version
HTTP/2 (HTTP/3 advertised)
Server
cloudflare
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
44 ms
TCP
2 ms
TLS
16 ms
First-byte wait
432 ms
Total
451 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

  • cf-cache-status: DYNAMIC (first request)
  • cf-cache-status: DYNAMIC (repeat request)

Response headers (first request)

last-modified: Fri, 06 Nov 2026 16:44:29 GMT
vary: Accept-Encoding
server: cloudflare
content-type: text/html
content-encoding: zstd
alt-svc: h3=":443"; ma=86400
server-timing: cfCacheStatus;desc="DYNAMIC", cfEdge;dur=11,cfOrigin;dur=313
cf-cache-status: DYNAMIC
cf-ray: a565a0ecdeadfbe1-EWR
x-turbo-charged-by: LiteSpeed

Response headers (repeat request, 228 ms)

last-modified: Fri, 06 Nov 2026 16:44:29 GMT
vary: Accept-Encoding
server: cloudflare
content-type: text/html
content-encoding: zstd
alt-svc: h3=":443"; ma=86400
server-timing: cfCacheStatus;desc="DYNAMIC", cfEdge;dur=22,cfOrigin;dur=100
cf-cache-status: DYNAMIC
cf-ray: a565a18a296b1278-EWR
x-turbo-charged-by: LiteSpeed

Sampled static assets

Asset Cache lifetime Cache-Control
chadbotha.com/wp-content/cach…d2ddda72252b13f7e87d6bb04.css 1 year public, max-age=31536000
chadbotha.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 1 year public, max-age=31536000
chadbotha.com/wp-content/uplo…logo-transparent-1024x285.png 1 year public, max-age=31536000
chadbotha.com/wp-content/them…-layer.min.css?ver=1793754775 1 year public, max-age=31536000
chadbotha.com/wp-content/plug…rontend.min.js?ver=1791424167 1 year public, max-age=31536000
chadbotha.com/wp-content/them…hild/style.css?ver=1666964846 1 year public, max-age=31536000
  • Improve static asset cache lifetimeLow impactPotential savings: 18 KB

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

    Evidence

    • 0 of 6 sampled static assets have a cache lifetime under 30 days
    • Lighthouse flagged 4 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

262 KB in 18 requests · 44% of page weight · Mobile

262 KB in 18 requests · 44% of page weight · Desktop

  • Eliminate render-blocking resourcesHigh impactPotential savings: 2 s

    4 stylesheets and scripts block the first paint.

    Evidence

    • chadbotha.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (842 ms)
    • chadbotha.com/wp-content/uploads/wpcodebox/159.css?v=17a808c13aa3c4e2 (506 ms)
    • chadbotha.com/wp-content/cache/xspeed/min/7298e5807899c4948db897166ae7b24d.js (506 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 JavaScriptMedium impactPotential savings: 90 KB

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

    Evidence

    • cdn.iubenda.com/cookie_solution/iubenda_cs/1.109.0/core-en-GB.js (44 KB could be saved)
    • d.plerdy.com/public/js/tracker/core.js?v=2306a983d4 (25 KB could be saved)
    • chadbotha.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (21 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
  • Stop sending legacy JavaScript to modern browsersLow impactPotential savings: 50 KB

    About 50 KB of polyfills and transpiled code targets browsers that no longer need it.

    Evidence

    • cdn.iubenda.com/iubenda.js (13 KB could be saved)
    • cdn.iubenda.com/iubenda.js (13 KB could be saved)
    • cdn.iubenda.com/iubenda.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

78 KB in 11 requests · 13% of page weight · Mobile

78 KB in 11 requests · 13% of page weight · Desktop

  • Remove unused CSSLow impactPotential savings: 24 KB

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

    Evidence

    • chadbotha.com/wp-content/cache/xspeed/min/f52f810d2ddda72252b13f7e87d6bb04.css (24 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

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

68 KB in 1 requests · 11% of page weight · Desktop

No Images issues found.

Fonts

157 KB in 8 requests · 26% of page weight · Mobile

157 KB in 8 requests · 26% of page weight · Desktop

No Fonts issues found.

Third Parties

231 KB from other domains in 18 requests · 39% of page weight

No common third-party services were detected.

  • Reduce the impact of third-party codeMedium impact

    Scripts and resources from other companies account for 231 KB of this page.

    Evidence

    • Third-party code: 231 KB (39% of page weight) across 18 requests
    • cdn.iubenda.com — 131 KB
    • d.plerdy.com — 72 KB
    • cs.iubenda.com — 15 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
Not set
Cache-Control
Not set
Validators
ETag / Last-Modified present
Content-Type
text/html
Vary
Accept-Encoding

No delivery issues found.

Technology

  • WordPress Detected
    • Asset paths under /wp-content/
    • Asset paths under /wp-includes/
    • REST API discovery link (api.w.org)
    • Generator meta tag: WordPress
  • LiteSpeed Detected
    • x-turbo-charged-by: LiteSpeed
  • PHP Detected
    • Implied by WordPress
  • Cloudflare Detected
    • cf-ray: a565a0ecdeadfbe1-EWR
    • cf-cache-status: DYNAMIC
    • server: cloudflare

WordPress

Theme
bricks
REST API
Advertised
Plugins visible in the page
5 plugins

Optimization tools

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

Plugins referenced by asset paths

automaticcss-plugin bricksextras analyticswp xspeed-pro fluentform