Skip to report
Scan another site

Performance report

siamglove.com

Scanned siamglove.com

  • WordPress
  • nginx
  • PHP

86 out of 100

Warp Score

B Good

TTFB — Needs improvementserver response
542 ms
LCP — Needs improvementlab
3.7 s
LCP — Goodlab
0.9 s
INPno field data
—
CLS — Goodlab
0
CLS — Goodlab
0
Desktop — GoodLighthouse
97
Mobile — Needs improvementLighthouse
89
Transfer
891 KB
Transfer
1.07 MB
Requests
42
Requests
50
Share on X Share on LinkedIn

Overview

Since the previous scan (Nov 13, 2026 · 13:31 UTC)

Metric Previous Current Change
Warp Score 85 86 +1 (improved)
LCP (mobile lab) 3.7 s 3.7 s +47 ms (regressed)
TTFB 631 ms 542 ms −89 ms (improved)
CLS (mobile lab) 0 0 ±0 (no change)
Transfer size 890 KB 891 KB +668 B (regressed)
Desktop Lighthouse 96 97 +1 (improved)
Mobile Lighthouse 88 89 +1 (improved)

Score breakdown

Performance

A

92 / 100

Lighthouse scored this page 89 on mobile and 97 on desktop.

Core Web Vitals

— not scored

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

Server & Cache

B

82 / 100

HTML appears to be cached by WP Rocket; the server responded in 542 ms.

Assets

C

77 / 100

891 KB transferred in 42 requests, including 490 KB of JavaScript.

Delivery

A

93 / 100

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

Top improvements

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

    10 stylesheets and scripts block the first paint.

    Evidence

    • siamglove.com/wp-content/themes/kadence/assets/css/header.min.css?ver=1.6.0 (1.1 s)
    • siamglove.com/wp-content/plugins/kadenc…st/style-blocks-rowlayout.css?ver=3.9.0 (1.1 s)
    • siamglove.com/wp-content/themes/kadence/assets/css/footer.min.css?ver=1.6.0 (1.1 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 JavaScript
  2. Reduce the impact of third-party codeHigh impact

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

    Evidence

    • Third-party code: 588 KB (66% of page weight) across 20 requests
    • www.googletagmanager.com — 469 KB
    • fonts.gstatic.com — 100 KB
    • t.usermaven.com — 14 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
  3. Reduce unused JavaScriptMedium impactPotential savings: 224 KB

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

    Evidence

    • www.googletagmanager.com/gtag/js?id=G-PTLTPYQFKJ&cx=c&gtm=4e6bb1 (81 KB could be saved)
    • www.googletagmanager.com/gtag/js?id=UA-25698515-1 (72 KB could be saved)
    • www.googletagmanager.com/gtm.js?id=GTM-ML9DDQL (71 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
  4. 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

891 KB transferred · 42 requests · Mobile

  • JavaScript 490 KB 5 requests
  • Images 240 KB 10 requests
  • Fonts 100 KB 9 requests
  • CSS 35 KB 11 requests
  • HTML 23 KB 1 request
  • Other 2 KB 6 requests

1.07 MB transferred · 50 requests · Desktop

  • JavaScript 490 KB 5 requests
  • Images 414 KB 15 requests
  • Fonts 129 KB 12 requests
  • CSS 35 KB 11 requests
  • HTML 23 KB 1 request
  • Other 2 KB 6 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 — Needs improvement
89
LCP — Needs improvement
3.7 s
FCP — Good
1.1 s
TBT — Good
38 ms
Speed Index — Good
3.3 s
CLS — Good
0

Desktop

Lighthouse — Good
97
LCP — Good
0.9 s
FCP — Good
0.3 s
TBT — Good
25 ms
Speed Index — Good
1.6 s
CLS — Good
0

Server & Cache

TTFB (server response)
542 ms
HTML cache
WP Rocket Likely
CDN
None detected
Compression
Gzip
HTTP version
HTTP/2
Server
nginx
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
377 ms
TCP
298 ms
TLS
299 ms
First-byte wait
612 ms
Total
1.3 s
HTML size
23 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

  • WP Rocket cache signature found in the HTML

Response headers (first request)

cache-control: max-age=0
last-modified: Fri, 13 Nov 2026 06:48:47 GMT
expires: Fri, 13 Nov 2026 14:58:48 GMT
vary: Accept-Encoding,User-Agent
server: nginx
content-type: text/html; charset=UTF-8
content-encoding: gzip
content-length: 23478

Response headers (repeat request, 542 ms)

cache-control: max-age=0
last-modified: Fri, 13 Nov 2026 06:48:47 GMT
expires: Fri, 13 Nov 2026 14:59:19 GMT
vary: Accept-Encoding,User-Agent
server: nginx
content-type: text/html; charset=UTF-8
content-encoding: gzip
content-length: 23478

Sampled static assets

Asset Cache lifetime Cache-Control
siamglove.com/wp-content/them…/css/global.min.css?ver=1.6.0 1 year max-age=31536000, public
siamglove.com/wp-content/them…s/navigation.min.js?ver=1.6.0 1 year max-age=31536000, public
siamglove.com/wp-content/uplo…/Blue-Nitirile-SG-500500.webp 120 days max-age=10368000
siamglove.com/wp-content/them…/css/header.min.css?ver=1.6.0 1 year max-age=31536000, public
siamglove.com/wp-content/uplo…/Pink-Nitirile-SG-500500.webp 120 days max-age=10368000
siamglove.com/wp-content/them…css/content.min.css?ver=1.6.0 1 year max-age=31536000, public

No server or caching issues found.

JavaScript

490 KB in 5 requests · 55% of page weight · Mobile

490 KB in 5 requests · 45% of page weight · Desktop

  • Eliminate render-blocking resourcesHigh impactPotential savings: 7.5 s

    10 stylesheets and scripts block the first paint.

    Evidence

    • siamglove.com/wp-content/themes/kadence/assets/css/header.min.css?ver=1.6.0 (1.1 s)
    • siamglove.com/wp-content/plugins/kadenc…st/style-blocks-rowlayout.css?ver=3.9.0 (1.1 s)
    • siamglove.com/wp-content/themes/kadence/assets/css/footer.min.css?ver=1.6.0 (1.1 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 JavaScript
  • Reduce unused JavaScriptMedium impactPotential savings: 224 KB

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

    Evidence

    • www.googletagmanager.com/gtag/js?id=G-PTLTPYQFKJ&cx=c&gtm=4e6bb1 (81 KB could be saved)
    • www.googletagmanager.com/gtag/js?id=UA-25698515-1 (72 KB could be saved)
    • www.googletagmanager.com/gtm.js?id=GTM-ML9DDQL (71 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

35 KB in 11 requests · 4% of page weight · Mobile

35 KB in 11 requests · 3% of page weight · Desktop

No CSS issues found.

Images

240 KB in 10 requests · 27% of page weight · Mobile

414 KB in 15 requests · 38% of page weight · Desktop

No Images issues found.

Fonts

100 KB in 9 requests · 11% of page weight · Mobile

129 KB in 12 requests · 12% of page weight · Desktop

No Fonts issues found.

Third Parties

588 KB from other domains in 20 requests · 66% of page weight

Service Transfer size Requests Main-thread blocking
Google Analytics 324 KB 3 —
Google Tag Manager 146 KB 1 —
Google Fonts 102 KB 10 —
  • Reduce the impact of third-party codeHigh impact

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

    Evidence

    • Third-party code: 588 KB (66% of page weight) across 20 requests
    • www.googletagmanager.com — 469 KB
    • fonts.gstatic.com — 100 KB
    • t.usermaven.com — 14 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
max-age=0
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

  • WordPress Detected
    • Asset paths under /wp-content/
    • Asset paths under /wp-includes/
    • REST API discovery link (api.w.org)
    • Generator meta tag: WordPress
  • nginx Detected
    • server: nginx
  • PHP Detected
    • Implied by WordPress

WordPress

Theme
kadence
REST API
Advertised
Plugins visible in the page
2 plugins

Optimization tools

  • WP Rocket Detected WP Rocket HTML comment
Plugins referenced by asset paths

kadence-blocks kadence-blocks-pro