Skip to report
Scan another site

Performance report

droidfeats.com

Scanned droidfeats.com

  • WordPress
  • PHP
  • Cloudflare

79 out of 100

Warp Score

C Fair

TTFB — Needs improvementserver response
213 ms
LCP — Poorlab
5.0 s
LCP — Goodlab
1.1 s
INP — Needs improvementreal users
202 ms
CLS — Goodlab
0
CLS — Goodlab
0
Desktop — GoodLighthouse
96
Mobile — Needs improvementLighthouse
75
Transfer
890 KB
Transfer
958 KB
Requests
37
Requests
55
Share on X Share on LinkedIn

Overview

Score breakdown

Performance

B

83 / 100

Lighthouse scored this page 75 on mobile and 96 on desktop.

Core Web Vitals

C

70 / 100

Real visitors do not pass Core Web Vitals across the whole site. 75th-percentile LCP is 3.6 s.

Server & Cache

C

76 / 100

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

Assets

C

76 / 100

890 KB transferred in 37 requests, including 261 KB of JavaScript.

Delivery

A+

100 / 100

Delivered with HTTP/2, Zstandard compression, Cloudflare.

Top improvements

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

    3 stylesheets and scripts block the first paint.

    Evidence

    • cdn.droidfeats.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (1.2 s)
    • cdn.droidfeats.com/wp-content/cache/rab…droidfeats.com/url-f4e689ea6ae09cc0.css (1.1 s)
    • cdn.droidfeats.com/wp-content/cache/rab…undle-38cff9f7a036-5a415504d740.min.css (752 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 deliveryMedium impactPotential savings: 173 KB

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

    Evidence

    • cdn.droidfeats.com/wp-content/uploads/2…iny-over-billions-sa-0c1c3f-768x475.jpg (63 KB could be saved)
    • cdn.droidfeats.com/wp-content/uploads/2026/04/Vivo-X300-Ultra-768x523.avif (51 KB could be saved)
    • cdn.droidfeats.com/wp-content/uploads/2020/03/MX-Player-Custom-Codec-750x441.png (21 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 JavaScriptMedium impactPotential savings: 107 KB

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

    Evidence

    • cdn.droidfeats.com/wp-content/cache/rab…idfeats.com/js-15f6f0d6f200-15b7947f.js (70 KB could be saved)
    • data:text/javascript;base64,ZnVuY3Rpb24…yZkPj42O2QmPTYzO2dbbCsrXT0iQUJDREVGR0hJ (36 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. Remove unused CSSLow impactPotential savings: 19 KB

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

    Evidence

    • cdn.droidfeats.com/wp-content/cache/rab…droidfeats.com/url-f4e689ea6ae09cc0.css (19 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

890 KB transferred · 37 requests · Mobile

  • Images 357 KB 17 requests
  • JavaScript 261 KB 10 requests
  • Fonts 172 KB 5 requests
  • HTML 66 KB 1 request
  • CSS 34 KB 2 requests
  • Other 798 B 2 requests

958 KB transferred · 55 requests · Desktop

  • Images 425 KB 35 requests
  • JavaScript 261 KB 10 requests
  • Fonts 172 KB 5 requests
  • HTML 66 KB 1 request
  • CSS 34 KB 2 requests
  • Other 798 B 2 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

Does not pass Core Web Vitals

Mobile visitors · data for the whole site (not enough for this page alone)

LCP p75 — Needs improvement
3.6 s
INP p75 — Needs improvement
202 ms
CLS p75 — Needs improvement
0.17
TTFB p75 — Poor
2.1 s
FCP p75 — Poor
3.7 s

Desktop visitors · data for the whole site (not enough for this page alone)

LCP p75 — Needs improvement
2.8 s
INP p75 — Good
65 ms
CLS p75 — Good
0.05
TTFB p75 — Needs improvement
1.7 s
FCP p75 — Needs improvement
2.6 s

Lab test Google Lighthouse · simulated load

Mobile

Lighthouse — Needs improvement
75
LCP — Poor
5.0 s
FCP — Needs improvement
2.9 s
TBT — Good
120 ms
Speed Index — Needs improvement
3.5 s
CLS — Good
0

Desktop

Lighthouse — Good
96
LCP — Good
1.1 s
FCP — Good
0.6 s
TBT — Good
15 ms
Speed Index — Good
1.4 s
CLS — Good
0

Server & Cache

TTFB (server response)
213 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
21 ms
TCP
3 ms
TLS
20 ms
First-byte wait
524 ms
Total
645 ms
HTML size
68 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)

cache-control: no-cache, must-revalidate, max-age=0
last-modified: Wed, 07 Oct 2026 07:52:11 GMT
vary: Accept-Encoding
server: cloudflare
content-type: text/html; charset=utf-8
content-encoding: zstd
alt-svc: h3=":443"; ma=86400
cf-cache-status: DYNAMIC
cf-ray: a46b695a8d030c78-EWR

Response headers (repeat request, 213 ms) 

cache-control: no-cache, must-revalidate, max-age=0
last-modified: Wed, 07 Oct 2026 07:52:11 GMT
vary: Accept-Encoding
server: cloudflare
content-type: text/html; charset=utf-8
content-encoding: zstd
alt-svc: h3=":443"; ma=86400
cf-cache-status: DYNAMIC
cf-ray: a46b6a4c2adf83ad-EWR

Sampled static assets

Asset Cache lifetime Cache-Control
cdn.droidfeats.com/wp-content…f9f7a036-5a415504d740.min.css 1 year max-age=31536000, public, max-age=31536000, immutable
cdn.droidfeats.com/wp-content…ost-views-b33271d17442.min.js 1 year max-age=31536000, public, max-age=31536000, immutable
cdn.droidfeats.com/wp-content…-Blue-Black-SVG-Dark-mode.svg 30 days max-age=2592000, public
cdn.droidfeats.com/wp-content….com/url-f4e689ea6ae09cc0.css 1 year max-age=31536000, public, max-age=31536000, immutable
cdn.droidfeats.com/wp-content…/js/v4-shims.min.js?ver=4.3.4 30 days max-age=2592000, public
cdn.droidfeats.com/wp-content…Droidfeats-Blue-Black-SVG.svg 30 days max-age=2592000, public

No server or caching issues found.

JavaScript

261 KB in 10 requests · 29% of page weight · Mobile

261 KB in 10 requests · 27% of page weight · Desktop

  • Eliminate render-blocking resourcesHigh impactPotential savings: 3 s

    3 stylesheets and scripts block the first paint.

    Evidence

    • cdn.droidfeats.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (1.2 s)
    • cdn.droidfeats.com/wp-content/cache/rab…droidfeats.com/url-f4e689ea6ae09cc0.css (1.1 s)
    • cdn.droidfeats.com/wp-content/cache/rab…undle-38cff9f7a036-5a415504d740.min.css (752 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: 107 KB

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

    Evidence

    • cdn.droidfeats.com/wp-content/cache/rab…idfeats.com/js-15f6f0d6f200-15b7947f.js (70 KB could be saved)
    • data:text/javascript;base64,ZnVuY3Rpb24…yZkPj42O2QmPTYzO2dbbCsrXT0iQUJDREVGR0hJ (36 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

34 KB in 2 requests · 4% of page weight · Mobile

34 KB in 2 requests · 4% of page weight · Desktop

  • Remove unused CSSLow impactPotential savings: 19 KB

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

    Evidence

    • cdn.droidfeats.com/wp-content/cache/rab…droidfeats.com/url-f4e689ea6ae09cc0.css (19 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

357 KB in 17 requests · 40% of page weight · Mobile

425 KB in 35 requests · 44% of page weight · Desktop

  • Optimize image deliveryMedium impactPotential savings: 173 KB

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

    Evidence

    • cdn.droidfeats.com/wp-content/uploads/2…iny-over-billions-sa-0c1c3f-768x475.jpg (63 KB could be saved)
    • cdn.droidfeats.com/wp-content/uploads/2026/04/Vivo-X300-Ultra-768x523.avif (51 KB could be saved)
    • cdn.droidfeats.com/wp-content/uploads/2020/03/MX-Player-Custom-Codec-750x441.png (21 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

172 KB in 5 requests · 19% of page weight · Mobile

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

No Fonts issues found.

Third Parties

1 KB from other domains in 3 requests · 0% of page weight

Service Transfer size Requests Main-thread blocking
Google Analytics 798 B 1 —
Google AdSense Referenced in the page; not measured during the test
Microsoft Clarity Referenced in the page; not measured during the test

Headers & Delivery

HTTPS
Yes
HSTS
Not set
Cache-Control
no-cache, must-revalidate, max-age=0
Validators
ETag / Last-Modified present
Content-Type
text/html; charset=utf-8
Vary
Accept-Encoding
  • Reduce the size of the DOMLow impact

    The page contains 1,579 HTML elements.

    Evidence

    • DOM elements: 1,579

    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

Technology

  • WordPress Detected
    • Asset paths under /wp-content/
    • Asset paths under /wp-includes/
  • PHP Detected
    • Implied by WordPress
  • Cloudflare Detected
    • cf-ray: a46b695a8d030c78-EWR
    • cf-cache-status: DYNAMIC
    • server: cloudflare

WordPress

Theme
smart-mag
REST API
Not 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 contact-form-7 rabbitpress