Performance report
oradeanul.com
- LiteSpeed
- WordPress
- PHP
- Cloudflare
77 out of 100
Warp Score
C Fair
- TTFB — Goodserver response
- 26 ms
- LCP — Poorlab
- 9.2 s
- LCP — Goodlab
- 0.8 s
- INPno field data
- —
- CLS — Goodlab
- 0
- CLS — Goodlab
- 0
- Desktop — GoodLighthouse
- 99
- Mobile — PoorLighthouse
- 55
- Transfer
- 1.68 MB
- Transfer
- 2.24 MB
- Requests
- 41
- Requests
- 43
Overview
Score breakdown
Performance
C73 / 100
Lighthouse scored this page 55 on mobile and 99 on desktop.
Core Web Vitals
— not scored
Not enough Chrome UX Report data is available for this URL.
Server & Cache
B80 / 100
HTML is served from cache by Cloudflare with a warm TTFB of 26 ms.
Assets
D67 / 100
1.68 MB transferred in 41 requests, including 797 KB of JavaScript.
Delivery
A+100 / 100
Delivered with HTTP/2, Zstandard compression, Cloudflare.
Top improvements
Eliminate render-blocking resources
9 stylesheets and scripts block the first paint.
Evidence
- oradeanul.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (976 ms)
- oradeanul.com/wp-content/litespeed/js/e…d06cf39092c9fdfa35ad0eb7d4.js?ver=b42f9 (651 ms)
- oradeanul.com/wp-content/litespeed/css/…820f460c6a2929d3f92cd77a1.css?ver=450d5 (651 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 JavaScriptReduce unused JavaScript
332 KB of downloaded JavaScript was never executed during page load.
Evidence
- www.gstatic.com/recaptcha/releases/0lEGiwO4Qwx5R9ArxUy0mBpf/recaptcha__en.js (166 KB could be saved)
- www.gstatic.com/recaptcha/releases/0lEGiwO4Qwx5R9ArxUy0mBpf/recaptcha__en.js (166 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 JavaScriptReduce the impact of third-party code
Scripts and resources from other companies account for 1.15 MB of this page.
Evidence
- Third-party code: 1.15 MB (69% of page weight) across 14 requests
- www.gstatic.com — 1.07 MB
- www.google.com — 36 KB
- fonts.gstatic.com — 35 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 JavaScriptImprove static asset cache lifetime
Some CSS, JavaScript or image files tell browsers to cache them only briefly, or not at all.
Evidence
- 6 of 6 sampled static assets have a cache lifetime under 30 days
- oradeanul.com/wp-content/litespeed…8e554412344f09e07705.css?ver=3799c — 4 hours
- oradeanul.com/wp-content/litespeed…39092c9fdfa35ad0eb7d4.js?ver=b42f9 — 4 hours
- oradeanul.com/wp-content/uploads/2026/07/pegas-made-in-ro.jpg — 12 hours
- oradeanul.com/wp-content/litespeed…b7883e0525feb3d500a4.css?ver=3dc18 — 4 hours
- oradeanul.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 — 4 hours
- oradeanul.com/wp-content/uploads/2026/07/rockna.jpg — 12 hours
- Lighthouse flagged 26 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.
Optimize image delivery
Images are larger than they need to be: resizing, recompressing or converting them would save about 120 KB.
Evidence
- oradeanul.com/wp-content/uploads/2026/07/pegas-made-in-ro-768x432.jpg (49 KB could be saved)
- oradeanul.com/wp-content/uploads/2026/07/rockna-768x432.jpg (38 KB could be saved)
- oradeanul.com/wp-content/uploads/2026/0…ei-revolverul-arhanghelului-768x434.jpg (25 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 more findings are listed in the other tabs.
Page weight
1.68 MB transferred · 41 requests · Mobile
- JavaScript 797 KB 17 requests
- Images 425 KB 9 requests
- Other 359 KB 5 requests
- HTML 55 KB 2 requests
- CSS 49 KB 7 requests
- Fonts 35 KB 1 request
2.24 MB transferred · 43 requests · Desktop
- Images 1002 KB 11 requests
- JavaScript 797 KB 17 requests
- Other 358 KB 5 requests
- HTML 55 KB 2 requests
- CSS 49 KB 7 requests
- Fonts 35 KB 1 request
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 — Poor
- 55
- LCP — Poor
- 9.2 s
- FCP — Poor
- 6.5 s
- TBT — Needs improvement
- 250 ms
- Speed Index — Poor
- 6.5 s
- CLS — Good
- 0
Desktop
- Lighthouse — Good
- 99
- LCP — Good
- 0.8 s
- FCP — Good
- 0.3 s
- TBT — Good
- 27 ms
- Speed Index — Good
- 0.9 s
- CLS — Good
- 0
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 may be reused for 2 hours
- Static asset caching
- 0 of 6 sampled assets cached for 30 days or more
Connection timing from the scanner
- DNS
- 26 ms
- TCP
- 3 ms
- TLS
- 27 ms
- First-byte wait
- 26 ms
- Total
- 56 ms
- HTML size
- 26 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: 6385 (first request)
- cf-cache-status: HIT (repeat request)
- age: 6412 (repeat request)
- x-litespeed-cache: miss (first request)
- x-litespeed-cache: miss (repeat request)
Response headers (first request)
cache-control: max-age=7200
age: 6385
vary: accept, content-type,Accept-Encoding
server: cloudflare
content-type: text/html; charset=UTF-8
content-encoding: zstd
link: <https://oradeanul.com/wp-json/>; rel="https://api.w.org/"
alt-svc: h3=":443"; ma=86400
server-timing: cfCacheStatus;desc="HIT", cfEdge;dur=17,cfOrigin;dur=0
cf-cache-status: HIT
cf-ray: a59c28d6189b7dc7-EWR
x-litespeed-cache: miss
x-litespeed-cache-control: public,max-age=60480
x-litespeed-tag: c43_home,c43_URL.6666cd76f96956469e7be39d750cc7d9,c43_F,c43_
x-turbo-charged-by: LiteSpeed
Response headers (repeat request, 35 ms)
cache-control: max-age=7200
age: 6412
vary: accept, content-type,Accept-Encoding
server: cloudflare
content-type: text/html; charset=UTF-8
content-encoding: zstd
link: <https://oradeanul.com/wp-json/>; rel="https://api.w.org/"
alt-svc: h3=":443"; ma=86400
server-timing: cfCacheStatus;desc="HIT", cfEdge;dur=26,cfOrigin;dur=0
cf-cache-status: HIT
cf-ray: a59c297eac1142d8-EWR
x-litespeed-cache: miss
x-litespeed-cache-control: public,max-age=60480
x-litespeed-tag: c43_home,c43_URL.6666cd76f96956469e7be39d750cc7d9,c43_F,c43_
x-turbo-charged-by: LiteSpeed
Sampled static assets
| Asset | Cache lifetime | Cache-Control |
|---|---|---|
| oradeanul.com/wp-content/lite…412344f09e07705.css?ver=3799c | 4 hours | public, max-age=13600 |
| oradeanul.com/wp-content/lite…c9fdfa35ad0eb7d4.js?ver=b42f9 | 4 hours | public, max-age=13600 |
| oradeanul.com/wp-content/uplo…/2026/07/pegas-made-in-ro.jpg | 12 hours | public, max-age=43200 |
| oradeanul.com/wp-content/lite…e0525feb3d500a4.css?ver=3dc18 | 4 hours | public, max-age=13600 |
| oradeanul.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 4 hours | public, max-age=13600 |
| oradeanul.com/wp-content/uploads/2026/07/rockna.jpg | 12 hours | public, max-age=43200 |
Improve static asset cache lifetime
Some CSS, JavaScript or image files tell browsers to cache them only briefly, or not at all.
Evidence
- 6 of 6 sampled static assets have a cache lifetime under 30 days
- oradeanul.com/wp-content/litespeed…8e554412344f09e07705.css?ver=3799c — 4 hours
- oradeanul.com/wp-content/litespeed…39092c9fdfa35ad0eb7d4.js?ver=b42f9 — 4 hours
- oradeanul.com/wp-content/uploads/2026/07/pegas-made-in-ro.jpg — 12 hours
- oradeanul.com/wp-content/litespeed…b7883e0525feb3d500a4.css?ver=3dc18 — 4 hours
- oradeanul.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 — 4 hours
- oradeanul.com/wp-content/uploads/2026/07/rockna.jpg — 12 hours
- Lighthouse flagged 26 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
797 KB in 17 requests · 46% of page weight · Mobile
797 KB in 17 requests · 35% of page weight · Desktop
Eliminate render-blocking resources
9 stylesheets and scripts block the first paint.
Evidence
- oradeanul.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (976 ms)
- oradeanul.com/wp-content/litespeed/js/e…d06cf39092c9fdfa35ad0eb7d4.js?ver=b42f9 (651 ms)
- oradeanul.com/wp-content/litespeed/css/…820f460c6a2929d3f92cd77a1.css?ver=450d5 (651 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 JavaScriptReduce unused JavaScript
332 KB of downloaded JavaScript was never executed during page load.
Evidence
- www.gstatic.com/recaptcha/releases/0lEGiwO4Qwx5R9ArxUy0mBpf/recaptcha__en.js (166 KB could be saved)
- www.gstatic.com/recaptcha/releases/0lEGiwO4Qwx5R9ArxUy0mBpf/recaptcha__en.js (166 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 JavaScriptStop sending legacy JavaScript to modern browsers
About 20 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)
- oradeanul.com/wp-content/litespeed/js/b…b1a5fe496edc9106f3d4551882.js?ver=12ed8 (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
49 KB in 7 requests · 3% of page weight · Mobile
49 KB in 7 requests · 2% of page weight · Desktop
Remove unused CSS
33 KB of CSS rules are not used by this page.
Evidence
- www.gstatic.com/recaptcha/releases/0lEGiwO4Qwx5R9ArxUy0mBpf/styles__ltr.css (33 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
425 KB in 9 requests · 25% of page weight · Mobile
1002 KB in 11 requests · 44% of page weight · Desktop
Optimize image delivery
Images are larger than they need to be: resizing, recompressing or converting them would save about 120 KB.
Evidence
- oradeanul.com/wp-content/uploads/2026/07/pegas-made-in-ro-768x432.jpg (49 KB could be saved)
- oradeanul.com/wp-content/uploads/2026/07/rockna-768x432.jpg (38 KB could be saved)
- oradeanul.com/wp-content/uploads/2026/0…ei-revolverul-arhanghelului-768x434.jpg (25 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
Fonts
35 KB in 1 requests · 2% of page weight · Mobile
35 KB in 1 requests · 2% of page weight · Desktop
Keep text visible while fonts load
1 web font hides text until it has loaded.
Evidence
- fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2 (5 ms)
Why it matters
Visitors see blank space where text should be until the font arrives, which delays FCP and can delay LCP.
How to fix
Use font-display: swap (or optional) so text renders immediately in a fallback font.
Related metric: FCP
In Warp PerformanceWarp Performance → Fonts → Font Display Swap
Third Parties
1.15 MB from other domains in 14 requests · 69% of page weight
| Service | Transfer size | Requests | Main-thread blocking |
|---|---|---|---|
| Google reCAPTCHA | 1.11 MB | 10 | — |
| Google Fonts | 35 KB | 1 | — |
Reduce the impact of third-party code
Scripts and resources from other companies account for 1.15 MB of this page.
Evidence
- Third-party code: 1.15 MB (69% of page weight) across 14 requests
- www.gstatic.com — 1.07 MB
- www.google.com — 36 KB
- fonts.gstatic.com — 35 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=7200
- Validators
- None
- Content-Type
- text/html; charset=UTF-8
- Vary
- accept, content-type,Accept-Encoding
No delivery issues found.
Technology
-
LiteSpeed Detected
- x-litespeed-cache: miss
- x-turbo-charged-by: LiteSpeed
-
WordPress Detected
- Asset paths under /wp-content/
- Asset paths under /wp-includes/
- REST API discovery link (api.w.org)
- Generator meta tag: WordPress
- link: <https://oradeanul.com/wp-json/>; rel="https://api.w.org/"
-
PHP Detected
- Implied by WordPress
-
Cloudflare Detected
- cf-ray: a59c28d6189b7dc7-EWR
- cf-cache-status: HIT
- server: cloudflare
WordPress
- Theme
- generatepress
- REST API
- Advertised
- Plugins visible in the page
- 1 plugin
Optimization tools
- LiteSpeed Cache Detected LiteSpeed Cache HTML comment · Assets under /wp-content/litespeed/
Plugins referenced by asset paths
cookie-law-info