Skip to report
Scan another site

Performance report

iprakan.com

Scanned iprakan.com

  • WordPress
  • nginx
  • PHP

94 out of 100

Warp Score

A Excellent

TTFB — Needs improvementserver response
537 ms
LCP — Goodlab
0.9 s
LCP — Goodlab
0.3 s
INPno field data
—
CLS — Goodlab
0
CLS — Goodlab
0
Desktop — GoodLighthouse
100
Mobile — GoodLighthouse
99
Transfer
49 KB
Transfer
49 KB
Requests
5
Requests
5
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

B

82 / 100

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

Assets

A+

100 / 100

49 KB transferred in 5 requests, including 17 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: 1.1 s

    3 stylesheets and scripts block the first paint.

    Evidence

    • iprakan.com/wp-content/themes/astra/ass…/js/minified/frontend.min.js?ver=4.14.3 (451 ms)
    • iprakan.com/wp-content/themes/astra-child/style.css?ver=1.0.0 (451 ms)
    • iprakan.com/wp-content/themes/astra/assets/css/minified/main.min.css?ver=4.14.3 (151 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. 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

49 KB transferred · 5 requests · Mobile

  • HTML 20 KB 1 request
  • JavaScript 17 KB 2 requests
  • CSS 12 KB 2 requests

49 KB transferred · 5 requests · Desktop

  • HTML 20 KB 1 request
  • JavaScript 17 KB 2 requests
  • CSS 12 KB 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

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
0.9 s
FCP — Good
0.9 s
TBT — Good
0 ms
Speed Index — Good
3.0 s
CLS — Good
0

Desktop

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

Server & Cache

TTFB (server response)
537 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
4 of 4 sampled assets cached for 30 days or more

Connection timing from the scanner

DNS
104 ms
TCP
292 ms
TLS
279 ms
First-byte wait
537 ms
Total
1.1 s
HTML size
19 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 11:55:35 GMT
expires: Fri, 13 Nov 2026 15:03:02 GMT
vary: Accept-Encoding,User-Agent
server: nginx
content-type: text/html; charset=UTF-8
content-encoding: gzip
content-length: 19700

Response headers (repeat request, 626 ms)

cache-control: max-age=0
last-modified: Fri, 13 Nov 2026 11:55:35 GMT
expires: Fri, 13 Nov 2026 15:03:24 GMT
vary: Accept-Encoding,User-Agent
server: nginx
content-type: text/html; charset=UTF-8
content-encoding: gzip
content-length: 19700

Sampled static assets

Asset Cache lifetime Cache-Control
iprakan.com/wp-content/themes…ified/main.min.css?ver=4.14.3 1 year max-age=31536000, public
iprakan.com/wp-content/themes…ed/frontend.min.js?ver=4.14.3 1 year max-age=31536000, public
iprakan.com/wp-content/themes…tra-child/style.css?ver=1.0.0 1 year max-age=31536000, public
iprakan.com/wp-content/plugin…t/assets/js/wpr-beacon.min.js 1 year max-age=31536000, public

No server or caching issues found.

JavaScript

17 KB in 2 requests · 35% of page weight · Mobile

17 KB in 2 requests · 35% of page weight · Desktop

  • Eliminate render-blocking resourcesHigh impactPotential savings: 1.1 s

    3 stylesheets and scripts block the first paint.

    Evidence

    • iprakan.com/wp-content/themes/astra/ass…/js/minified/frontend.min.js?ver=4.14.3 (451 ms)
    • iprakan.com/wp-content/themes/astra-child/style.css?ver=1.0.0 (451 ms)
    • iprakan.com/wp-content/themes/astra/assets/css/minified/main.min.css?ver=4.14.3 (151 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

CSS

12 KB in 2 requests · 25% of page weight · Mobile

12 KB in 2 requests · 25% of page weight · Desktop

No CSS issues found.

Images

0 B in 0 requests · 0% of page weight · Mobile

0 B in 0 requests · 0% of page weight · Desktop

No Images issues found.

Fonts

0 B in 0 requests · 0% of page weight · Mobile

0 B in 0 requests · 0% of page weight · Desktop

No Fonts issues found.

Third Parties

0 B from other domains in 0 requests · 0% of page weight

No common third-party services were detected.

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
astra
REST API
Advertised
Plugins visible in the page
1 plugin

Optimization tools

  • WP Rocket Detected WP Rocket HTML comment · WP Rocket attributes (data-rocket-*)
Plugins referenced by asset paths

wp-rocket