Skip to report
Scan another site

Performance report

www.yakuzaev.com

Scanned www.yakuzaev.com

  • WooCommerce
  • WordPress
  • PHP
  • Cloudflare

83 out of 100

Warp Score

B Good

TTFB — Goodserver response
26 ms
LCP — Poorlab
4.2 s
LCP — Goodlab
1.0 s
INP — Goodreal users
136 ms
CLS — Goodlab
0.001
CLS — Goodlab
0.004
Desktop — Needs improvementLighthouse
77
Mobile — Needs improvementLighthouse
82
Transfer
1.99 MB
Transfer
2.04 MB
Requests
75
Requests
75
Share on X Share on LinkedIn

Overview

Since the previous scan (Oct 30, 2026 · 07:37 UTC)

Metric Previous Current Change
Warp Score 80 83 +3 (improved)
LCP (mobile lab) 4.2 s 4.2 s ±0 (no change)
TTFB 688 ms 26 ms −662 ms (improved)
CLS (mobile lab) 0.001 0.001 ±0 (no change)
Transfer size 1.57 MB 1.99 MB +430 KB (regressed)
Desktop Lighthouse 97 77 −20 (regressed)
Mobile Lighthouse 85 82 −3 (regressed)

Score breakdown

Performance

B

80 / 100

Lighthouse scored this page 82 on mobile and 77 on desktop.

Core Web Vitals

A

92 / 100

Real visitors pass Core Web Vitals on this page, with a 75th-percentile LCP of 2.2 s.

Server & Cache

A+

100 / 100

HTML is served from cache by Cloudflare with a warm TTFB of 26 ms.

Assets

F

53 / 100

1.99 MB transferred in 75 requests, including 750 KB of JavaScript.

Delivery

A+

100 / 100

Delivered with HTTP/2, Zstandard compression, Cloudflare.

Top improvements

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

    9 stylesheets and scripts block the first paint.

    Evidence

    • www.yakuzaev.com/wp-content/cache/flying-press/80a702fc1236.woocommerce.css (784 ms)
    • www.yakuzaev.com/wp-content/cache/flyin…ess/b8335b8f9733.woocommerce-layout.css (627 ms)
    • www.yakuzaev.com/wp-content/cache/flying-press/c96973ac843d.yevb.css (471 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. Optimize image deliveryHigh impactPotential savings: 623 KB

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

    Evidence

    • www.yakuzaev.com/wp-content/themes/yakuzaev/assets/Yakuza1.webp?w=279 (146 KB could be saved)
    • www.yakuzaev.com/wp-content/themes/yakuzaev/assets/logo.png (38 KB could be saved)
    • www.yakuzaev.com/wp-content/uploads/2026/07/Sparrow-Plus-THUMBNAIL-700x525.webp (28 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
  3. Reduce unused JavaScriptHigh impactPotential savings: 308 KB

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

    Evidence

    • www.googletagmanager.com/gtm.js?id=GTM-M9JXFLTW (130 KB could be saved)
    • www.yakuzaev.com/ef80/ (105 KB could be saved)
    • www.googletagmanager.com/gtag/js?id=GT-NCLXMJ8T (74 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. Load the LCP image soonerMedium impact

    The largest image on the first screen is not discoverable in the initial HTML or is not prioritized.

    Evidence

    • Request is discoverable in initial document

    Why it matters

    LCP cannot happen until this image has downloaded. Anything that delays its request delays LCP directly.

    How to fix

    Remove lazy-loading from the LCP image, add fetchpriority="high", and preload it if it is set from CSS or JavaScript.

    Related metric: LCP

    In Warp PerformanceWarp Performance → Media → Preload Critical Images
  5. Improve static asset cache lifetimeLow impactPotential savings: 15 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 3 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.

2 more findings are listed in the other tabs.

Page weight

1.99 MB transferred · 75 requests · Mobile

  • Images 1.02 MB 26 requests
  • JavaScript 750 KB 27 requests
  • Fonts 171 KB 4 requests
  • CSS 43 KB 9 requests
  • HTML 24 KB 1 request
  • Other 4 KB 8 requests

2.04 MB transferred · 75 requests · Desktop

  • Images 1.08 MB 26 requests
  • JavaScript 750 KB 27 requests
  • Fonts 171 KB 4 requests
  • CSS 43 KB 9 requests
  • HTML 24 KB 1 request
  • Other 4 KB 8 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 Vitals

Mobile visitors · data for this page

LCP p75 — Good
2.2 s
INP p75 — Good
136 ms
CLS p75 — Good
0
TTFB p75 — Needs improvement
1.3 s
FCP p75 — Needs improvement
2.0 s

Desktop visitors · data for this page

LCP p75 — Good
1.7 s
INP p75 — Good
34 ms
CLS p75 — Good
0
TTFB p75 — Needs improvement
978 ms
FCP p75 — Good
1.5 s

Lab test Google Lighthouse · simulated load

Mobile

Lighthouse — Needs improvement
82
LCP — Poor
4.2 s
FCP — Good
1.1 s
TBT — Needs improvement
220 ms
Speed Index — Good
2.2 s
CLS — Good
0.001

Desktop

Lighthouse — Needs improvement
77
LCP — Good
1.0 s
FCP — Good
0.3 s
TBT — Needs improvement
494 ms
Speed Index — Good
0.9 s
CLS — Good
0.004

Server & Cache

TTFB (server response)
26 ms
HTML cache
Cloudflare Confirmed
CDN
Cloudflare HTML caching: Confirmed
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
60 ms
TCP
2 ms
TLS
27 ms
First-byte wait
26 ms
Total
55 ms
HTML size
24 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: HIT (first request)
  • age: 263033 (first request)
  • cf-cache-status: HIT (repeat request)
  • age: 263077 (repeat request)

Response headers (first request)

cache-control: no-cache, must-revalidate
age: 263033
last-modified: Sat, 07 Nov 2026 09:57:17 GMT
vary: accept-encoding
server: cloudflare
content-type: text/html; charset=utf-8
content-encoding: zstd
alt-svc: h3=":443"; ma=86400
server-timing: cfCacheStatus;desc="HIT", cfEdge;dur=20,cfOrigin;dur=0
cf-cache-status: HIT
cf-ray: a584e37a9e8db3b2-EWR
x-powered-by: WordOps
cdn-cache-control: max-age=2592000

Response headers (repeat request, 27 ms)

cache-control: no-cache, must-revalidate
age: 263077
last-modified: Sat, 07 Nov 2026 09:57:17 GMT
vary: accept-encoding
server: cloudflare
content-type: text/html; charset=utf-8
content-encoding: zstd
alt-svc: h3=":443"; ma=86400
server-timing: cfCacheStatus;desc="HIT", cfEdge;dur=18,cfOrigin;dur=0
cf-cache-status: HIT
cf-ray: a584e48d2d050f63-EWR
x-powered-by: WordOps
cdn-cache-control: max-age=2592000

Sampled static assets

Asset Cache lifetime Cache-Control
www.yakuzaev.com/wp-content/c…g-press/5824a21324ae.main.css 1 year max-age=31536000
www.yakuzaev.com/wp-includes/…query.min.js?ver=826eb77e86b0 1 year max-age=31536000
www.yakuzaev.com/wp-content/themes/yakuzaev/assets/logo.png 10 years max-age=315360000
www.yakuzaev.com/wp-content/c…press/2ea2d89beef2.styles.css 1 year max-age=31536000
www.yakuzaev.com/wp-content/p…ockUI.min.js?ver=ce21b49b1191 1 year max-age=31536000
www.yakuzaev.com/wp-content/themes/yakuzaev/assets/icon.png 10 years max-age=315360000
  • Improve static asset cache lifetimeLow impactPotential savings: 15 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 3 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

750 KB in 27 requests · 37% of page weight · Mobile

750 KB in 27 requests · 36% of page weight · Desktop

  • Eliminate render-blocking resourcesHigh impactPotential savings: 3.8 s

    9 stylesheets and scripts block the first paint.

    Evidence

    • www.yakuzaev.com/wp-content/cache/flying-press/80a702fc1236.woocommerce.css (784 ms)
    • www.yakuzaev.com/wp-content/cache/flyin…ess/b8335b8f9733.woocommerce-layout.css (627 ms)
    • www.yakuzaev.com/wp-content/cache/flying-press/c96973ac843d.yevb.css (471 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 JavaScriptHigh impactPotential savings: 308 KB

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

    Evidence

    • www.googletagmanager.com/gtm.js?id=GTM-M9JXFLTW (130 KB could be saved)
    • www.yakuzaev.com/ef80/ (105 KB could be saved)
    • www.googletagmanager.com/gtag/js?id=GT-NCLXMJ8T (74 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: 10 KB

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

    Evidence

    • static.cloudflareinsights.com/beacon.mi…23e78c4301a35b7e07294d87301792088814092 (10 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

43 KB in 9 requests · 2% of page weight · Mobile

43 KB in 9 requests · 2% of page weight · Desktop

  • Remove unused CSSLow impactPotential savings: 12 KB

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

    Evidence

    • www.yakuzaev.com/wp-content/cache/flying-press/80a702fc1236.woocommerce.css (12 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

1.02 MB in 26 requests · 51% of page weight · Mobile

1.08 MB in 26 requests · 53% of page weight · Desktop

  • Optimize image deliveryHigh impactPotential savings: 623 KB

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

    Evidence

    • www.yakuzaev.com/wp-content/themes/yakuzaev/assets/Yakuza1.webp?w=279 (146 KB could be saved)
    • www.yakuzaev.com/wp-content/themes/yakuzaev/assets/logo.png (38 KB could be saved)
    • www.yakuzaev.com/wp-content/uploads/2026/07/Sparrow-Plus-THUMBNAIL-700x525.webp (28 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
  • Load the LCP image soonerMedium impact

    The largest image on the first screen is not discoverable in the initial HTML or is not prioritized.

    Evidence

    • Request is discoverable in initial document

    Why it matters

    LCP cannot happen until this image has downloaded. Anything that delays its request delays LCP directly.

    How to fix

    Remove lazy-loading from the LCP image, add fetchpriority="high", and preload it if it is set from CSS or JavaScript.

    Related metric: LCP

    In Warp PerformanceWarp Performance → Media → Preload Critical Images

Fonts

171 KB in 4 requests · 8% of page weight · Mobile

171 KB in 4 requests · 8% of page weight · Desktop

No Fonts issues found.

Third Parties

445 KB from other domains in 14 requests · 22% of page weight

Service Transfer size Requests Main-thread blocking
Google Tag Manager 206 KB 2 —
Microsoft Clarity 29 KB 7 —
Google Analytics 800 B 1 —

Headers & Delivery

HTTPS
Yes
HSTS
Not set
Cache-Control
no-cache, must-revalidate
Validators
ETag / Last-Modified present
Content-Type
text/html; charset=utf-8
Vary
accept-encoding

No delivery issues found.

Technology

  • WooCommerce Detected
    • Asset paths under /plugins/woocommerce/
    • WooCommerce body class
    • WooCommerce script data
  • WordPress Detected
    • Asset paths under /wp-content/
    • Asset paths under /wp-includes/
  • PHP Detected
    • Implied by WordPress
  • Cloudflare Detected
    • cf-ray: a584e37a9e8db3b2-EWR
    • cf-cache-status: HIT
    • server: cloudflare

WordPress

Theme
yakuzaev
REST API
Not advertised
Plugins visible in the page
5 plugins

Optimization tools

  • FlyingPress Detected Assets under /cache/flying-press/ · FlyingPress markers in markup
  • Perfmatters Likely detected Perfmatters attributes
Plugins referenced by asset paths

woocommerce google-site-kit contact-form-7 duracelltomi-google-tag-manager click-to-chat-for-whatsapp