Performance report
jumptoweb.com
- WordPress
- nginx
- PHP
85 out of 100
Warp Score
B Good
- TTFB — Goodserver response
- 63 ms
- LCP — Poorlab
- 6.2 s
- LCP — Goodlab
- 0.8 s
- INPno field data
- —
- CLS — Goodlab
- 0
- CLS — Goodlab
- 0
- Desktop — GoodLighthouse
- 99
- Mobile — Needs improvementLighthouse
- 69
- Transfer
- 1.03 MB
- Transfer
- 1019 KB
- Requests
- 64
- Requests
- 64
Overview
Since the previous scan (Oct 6, 2026 · 20:43 UTC)
| Metric | Previous | Current | Change |
|---|---|---|---|
| Warp Score | 82 | 85 | +3 (improved) |
| LCP (mobile lab) | 4.3 s | 6.2 s | +1.9 s (regressed) |
| TTFB | 68 ms | 63 ms | −5 ms (improved) |
| CLS (mobile lab) | 0 | 0 | ±0 (no change) |
| Transfer size | 1.04 MB | 1.03 MB | −9 KB (improved) |
| Desktop Lighthouse | 97 | 99 | +2 (improved) |
| Mobile Lighthouse | 55 | 69 | +14 (improved) |
Score breakdown
Performance
B81 / 100
Lighthouse scored this page 69 on mobile and 99 on desktop.
Core Web Vitals
— not scored
Not enough Chrome UX Report data is available for this URL.
Server & Cache
A+100 / 100
HTML is served from cache by Proxy cache with a warm TTFB of 63 ms.
Assets
C71 / 100
1.03 MB transferred in 64 requests, including 360 KB of JavaScript.
Delivery
A93 / 100
Delivered with HTTP/2, Gzip compression, no CDN detected.
Top improvements
Eliminate render-blocking resources
22 stylesheets and scripts block the first paint.
Evidence
- jumptowebcom7b408.zapwp.com/wp-content/…utomatic-css/automatic.css?icv=faf0c589 (2.1 s)
- jumptowebcom7b408.zapwp.com/wp-content/…t-awesome-6-08b76f455f.css?icv=ff75df35 (1.7 s)
- jumptowebcom7b408.zapwp.com/wp-content/…ontend-light-layer.min.css?icv=f180f3b2 (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 JavaScriptKeep text visible while fonts load
2 web fonts hide text until they have loaded.
Evidence
- jumptowebcom7b408.zapwp.com/wp-content/…ts/fonts/fontawesome/fa-solid-900.woff2 (190 ms)
- jumptowebcom7b408.zapwp.com/wp-content/…ricks/assets/fonts/themify/themify.woff (145 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 SwapReduce unused JavaScript
176 KB of downloaded JavaScript was never executed during page load.
Evidence
- app.usercentrics.eu/browser-ui/3.113.0/index.module.js (54 KB could be saved)
- jumptoweb.com/wp-content/themes/bricks/assets/js/bricks.min.js?ver=1793207961 (51 KB could be saved)
- jumptoweb.com/wp-content/uploads/wpc-as…delay-v3-loader-7.30.00-cbd783b4.min.js (39 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 JavaScriptOptimize image delivery
Images are larger than they need to be: resizing, recompressing or converting them would save about 143 KB.
Evidence
- jumptoweb.com/wp-content/uploads/antigua-about-us-768x3298.webp (43 KB could be saved)
- jumptoweb.com/wp-content/uploads/Home-768x2970.webp (39 KB could be saved)
- jumptoweb.com/wp-content/uploads/Riverwalk-Ranch-Home-768x3379.webp (36 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 ImagesReduce the impact of third-party code
Scripts and resources from other companies account for 612 KB of this page.
Evidence
- Third-party code: 612 KB (58% of page weight) across 49 requests
- jumptowebcom7b408.zapwp.com — 353 KB
- app.usercentrics.eu — 208 KB
- privacy-proxy.usercentrics.eu — 31 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
5 more findings are listed in the other tabs.
Page weight
1.03 MB transferred · 64 requests · Mobile
- JavaScript 360 KB 17 requests
- Images 324 KB 14 requests
- Fonts 210 KB 2 requests
- CSS 106 KB 22 requests
- HTML 32 KB 1 request
- Other 19 KB 8 requests
1019 KB transferred · 64 requests · Desktop
- JavaScript 360 KB 17 requests
- Images 293 KB 14 requests
- Fonts 210 KB 2 requests
- CSS 104 KB 22 requests
- HTML 32 KB 1 request
- Other 19 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
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
- 69
- LCP — Poor
- 6.2 s
- FCP — Needs improvement
- 2.9 s
- TBT — Good
- 3 ms
- Speed Index — Needs improvement
- 5.4 s
- CLS — Good
- 0
Desktop
- Lighthouse — Good
- 99
- LCP — Good
- 0.8 s
- FCP — Good
- 0.6 s
- TBT — Good
- 0 ms
- Speed Index — Good
- 0.8 s
- CLS — Good
- 0
Server & Cache
- TTFB (server response)
- 63 ms
- HTML cache
- Proxy cache Confirmed
- 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
- 85 ms
- TCP
- 37 ms
- TLS
- 42 ms
- First-byte wait
- 73 ms
- Total
- 166 ms
- HTML size
- 32 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
- x-cache: HIT (first request)
- age: 16593 (first request)
- x-cache: HIT (repeat request)
- age: 16619 (repeat request)
Response headers (first request)
age: 16593
last-modified: Mon, 02 Nov 2026 15:33:45 GMT
vary: Accept-Encoding
server: nginx
content-type: text/html; charset=utf-8
content-encoding: gzip
content-length: 32742
x-cache: HIT
Response headers (repeat request, 63 ms)
age: 16619
last-modified: Mon, 02 Nov 2026 15:33:45 GMT
vary: Accept-Encoding
server: nginx
content-type: text/html; charset=utf-8
content-encoding: gzip
content-length: 32742
x-cache: HIT
Sampled static assets
| Asset | Cache lifetime | Cache-Control |
|---|---|---|
| jumptoweb.com/wp-content/them…/bricks.min.js?ver=1793207961 | 1 year | public, max-age=31536000 |
| jumptoweb.com/wp-content/uploads/website_mockups.webp | 1 year | public, max-age=31536000 |
| jumptoweb.com/wp-content/uplo…sets/wpc-body-297c451f3b75.js | 1 year | public, max-age=31536000 |
| jumptoweb.com/wp-content/uploads/Home-scaled.webp | 1 year | public, max-age=31536000 |
| jumptoweb.com/wp-content/uplo…oader-7.30.00-cbd783b4.min.js | 1 year | public, max-age=31536000 |
| jumptoweb.com/wp-content/uplo…/antigua-about-us-scaled.webp | 1 year | public, max-age=31536000 |
Improve static asset cache lifetime
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 27 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
360 KB in 17 requests · 34% of page weight · Mobile
360 KB in 17 requests · 35% of page weight · Desktop
Eliminate render-blocking resources
22 stylesheets and scripts block the first paint.
Evidence
- jumptowebcom7b408.zapwp.com/wp-content/…utomatic-css/automatic.css?icv=faf0c589 (2.1 s)
- jumptowebcom7b408.zapwp.com/wp-content/…t-awesome-6-08b76f455f.css?icv=ff75df35 (1.7 s)
- jumptowebcom7b408.zapwp.com/wp-content/…ontend-light-layer.min.css?icv=f180f3b2 (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 JavaScriptReduce unused JavaScript
176 KB of downloaded JavaScript was never executed during page load.
Evidence
- app.usercentrics.eu/browser-ui/3.113.0/index.module.js (54 KB could be saved)
- jumptoweb.com/wp-content/themes/bricks/assets/js/bricks.min.js?ver=1793207961 (51 KB could be saved)
- jumptoweb.com/wp-content/uploads/wpc-as…delay-v3-loader-7.30.00-cbd783b4.min.js (39 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 11 KB of polyfills and transpiled code targets browsers that no longer need it.
Evidence
- app.usercentrics.eu/browser-ui/3.113.0/VirtualServiceItem-e06b8d01.js (11 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
106 KB in 22 requests · 10% of page weight · Mobile
104 KB in 22 requests · 10% of page weight · Desktop
Remove unused CSS
33 KB of CSS rules are not used by this page.
Evidence
- jumptowebcom7b408.zapwp.com/wp-content/…utomatic-css/automatic.css?icv=faf0c589 (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 CSSMinify CSS
CSS files are served unminified; minifying would save about 5 KB.
Evidence
- jumptowebcom7b408.zapwp.com/wp-content/…utomatic-css/automatic.css?icv=faf0c589 (5 KB could be saved)
Why it matters
Smaller stylesheets download faster and unblock rendering sooner.
How to fix
Minify CSS as part of the build, or enable minification in your performance plugin.
In Warp PerformanceWarp Performance → CSS → Minify CSS
Images
324 KB in 14 requests · 31% of page weight · Mobile
293 KB in 14 requests · 29% of page weight · Desktop
Optimize image delivery
Images are larger than they need to be: resizing, recompressing or converting them would save about 143 KB.
Evidence
- jumptoweb.com/wp-content/uploads/antigua-about-us-768x3298.webp (43 KB could be saved)
- jumptoweb.com/wp-content/uploads/Home-768x2970.webp (39 KB could be saved)
- jumptoweb.com/wp-content/uploads/Riverwalk-Ranch-Home-768x3379.webp (36 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
210 KB in 2 requests · 20% of page weight · Mobile
210 KB in 2 requests · 21% of page weight · Desktop
Keep text visible while fonts load
2 web fonts hide text until they have loaded.
Evidence
- jumptowebcom7b408.zapwp.com/wp-content/…ts/fonts/fontawesome/fa-solid-900.woff2 (190 ms)
- jumptowebcom7b408.zapwp.com/wp-content/…ricks/assets/fonts/themify/themify.woff (145 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
612 KB from other domains in 49 requests · 58% of page weight
| Service | Transfer size | Requests | Main-thread blocking |
|---|---|---|---|
| YouTube | Referenced in the page; not measured during the test | ||
| Vimeo | Referenced in the page; not measured during the test | ||
Reduce the impact of third-party code
Scripts and resources from other companies account for 612 KB of this page.
Evidence
- Third-party code: 612 KB (58% of page weight) across 49 requests
- jumptowebcom7b408.zapwp.com — 353 KB
- app.usercentrics.eu — 208 KB
- privacy-proxy.usercentrics.eu — 31 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
- Not set
- Validators
- ETag / Last-Modified present
- Content-Type
- text/html; charset=utf-8
- Vary
- Accept-Encoding
Consider a CDN
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
- bricks
- REST API
- Advertised
- Plugins visible in the page
- 4 plugins
Optimization tools
- Breeze Detected Breeze HTML comment
Plugins referenced by asset paths
bricksextras
automaticcss-plugin
wp-compress-image-optimizer
web-concierge-ai