Performance report
mechanicalkeyboard.net
- WordPress
- PHP
- Cloudflare
78 out of 100
Warp Score
C Fair
- TTFB — Needs improvementserver response
- 210 ms
- LCP — Poorlab
- 7.1 s
- LCP — Goodlab
- 1.2 s
- INP — Goodreal users
- 177 ms
- CLS — Goodlab
- 0.002
- CLS — Goodlab
- 0
- Desktop — GoodLighthouse
- 91
- Mobile — Needs improvementLighthouse
- 70
- Transfer
- 3.41 MB
- Transfer
- 3.79 MB
- Requests
- 123
- Requests
- 138
Overview
Score breakdown
Performance
C78 / 100
Lighthouse scored this page 70 on mobile and 91 on desktop.
Core Web Vitals
B87 / 100
Real visitors do not pass Core Web Vitals across the whole site. 75th-percentile LCP is 2.8 s.
Server & Cache
A+97 / 100
HTML is served from cache by Proxy cache with a warm TTFB of 210 ms.
Assets
F44 / 100
3.41 MB transferred in 123 requests, including 1.88 MB of JavaScript.
Delivery
A90 / 100
Delivered with HTTP/2, Zstandard compression, Cloudflare.
Top improvements
Eliminate render-blocking resources
21 stylesheets and scripts block the first paint.
Evidence
- mechanicalkeyboard.net/wp-content/cache…3396f51f0423a44eb448b5201.css?ver=2.7.7 (1.1 s)
- mechanicalkeyboard.net/wp-content/plugi…r/assets/css/frontend.min.css?ver=4.3.6 (631 ms)
- mechanicalkeyboard.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (631 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
903 KB of downloaded JavaScript was never executed during page load.
Evidence
- www.gstatic.com/recaptcha/releases/4i3aN5wAweL7i3ADI7BSX4B-/recaptcha__en.js (205 KB could be saved)
- www.gstatic.com/recaptcha/releases/4i3aN5wAweL7i3ADI7BSX4B-/recaptcha__en.js (183 KB could be saved)
- www.gstatic.com/recaptcha/releases/4i3aN5wAweL7i3ADI7BSX4B-/recaptcha__en.js (182 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 2.4 MB of this page.
Evidence
- Third-party code: 2.4 MB (70% of page weight) across 48 requests
- www.gstatic.com — 1.45 MB
- pagead2.googlesyndication.com — 336 KB
- www.googletagmanager.com — 180 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 JavaScriptOptimize image delivery
Images are larger than they need to be: resizing, recompressing or converting them would save about 115 KB.
Evidence
- i.ytimg.com/vi/wW9Zy83i4RM/maxresdefault.jpg (96 KB could be saved)
- mechanicalkeyboard.net/wp-content/uploa…_2026__06_21_50_PM-removebg-preview.png (19 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 ImagesRemove unused CSS
78 KB of CSS rules are not used by this page.
Evidence
- mechanicalkeyboard.net/wp-content/cache…3396f51f0423a44eb448b5201.css?ver=2.7.7 (59 KB could be saved)
- mechanicalkeyboard.net/wp-content/cache…06ffb9fc8ac52118ec8be0a06.css?ver=6.1.1 (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
5 more findings are listed in the other tabs.
Page weight
3.41 MB transferred · 123 requests · Mobile
- JavaScript 1.88 MB 39 requests
- Images 584 KB 29 requests
- Other 385 KB 13 requests
- Fonts 303 KB 7 requests
- CSS 219 KB 28 requests
- HTML 80 KB 7 requests
3.79 MB transferred · 138 requests · Desktop
- JavaScript 1.8 MB 39 requests
- Images 1.03 MB 44 requests
- Other 385 KB 13 requests
- Fonts 303 KB 7 requests
- CSS 219 KB 28 requests
- HTML 79 KB 7 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 VitalsMobile visitors · data for the whole site (not enough for this page alone)
- LCP p75 — Needs improvement
- 2.8 s
- INP p75 — Good
- 177 ms
- CLS p75 — Good
- 0.02
- TTFB p75 — Needs improvement
- 1.6 s
- FCP p75 — Needs improvement
- 2.6 s
Desktop visitors · data for the whole site (not enough for this page alone)
- LCP p75 — Good
- 2.1 s
- INP p75 — Good
- 53 ms
- CLS p75 — Good
- 0.08
- TTFB p75 — Needs improvement
- 1.3 s
- FCP p75 — Needs improvement
- 1.8 s
Lab test Google Lighthouse · simulated load
Mobile
- Lighthouse — Needs improvement
- 70
- LCP — Poor
- 7.1 s
- FCP — Good
- 1.7 s
- TBT — Needs improvement
- 209 ms
- Speed Index — Needs improvement
- 4.2 s
- CLS — Good
- 0.002
Desktop
- Lighthouse — Good
- 91
- LCP — Good
- 1.2 s
- FCP — Good
- 0.4 s
- TBT — Needs improvement
- 202 ms
- Speed Index — Good
- 0.9 s
- CLS — Good
- 0
Server & Cache
- TTFB (server response)
- 210 ms
- HTML cache
- Proxy cache Confirmed
- CDN
- Cloudflare HTML caching: Not detected
- Compression
- Zstandard
- HTTP version
- HTTP/2 (HTTP/3 advertised)
- Server
- cloudflare
- Redirects
- None
- Browser caching
- HTML is fetched fresh on each visit
- Static asset caching
- 6 of 6 sampled assets cached for 30 days or more
Connection timing from the scanner
- DNS
- 80 ms
- TCP
- 2 ms
- TLS
- 20 ms
- First-byte wait
- 362 ms
- Total
- 389 ms
- HTML size
- 31 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)
- x-cache: HIT (repeat request)
- cf-cache-status: BYPASS (first request)
- cf-cache-status: BYPASS (repeat request)
Response headers (first request)
vary: Accept-Encoding
server: cloudflare
content-type: text/html; charset=UTF-8
content-encoding: zstd
link: </sitemap_index.xml>; rel="sitemap", </llms.txt>; rel="describedby"; type="text/markdown", <https://mechanicalkeyboard.net/wp-json/>; rel="https://api.w.org/", <https://mechanicalkeyboard.net/wp-json/wp/v2/pages/3617>; rel="alternate"; title="JSON"; type="application/json", <https://mechanicalkeyboa
alt-svc: h3=":443"; ma=86400
x-cache: HIT
cf-cache-status: BYPASS
cf-ray: a5a97661dfec4f3a-EWR
Response headers (repeat request, 210 ms)
vary: Accept-Encoding
server: cloudflare
content-type: text/html; charset=UTF-8
content-encoding: zstd
link: </sitemap_index.xml>; rel="sitemap", </llms.txt>; rel="describedby"; type="text/markdown", <https://mechanicalkeyboard.net/wp-json/>; rel="https://api.w.org/", <https://mechanicalkeyboard.net/wp-json/wp/v2/pages/3617>; rel="alternate"; title="JSON"; type="application/json", <https://mechanicalkeyboa
alt-svc: h3=":443"; ma=86400
x-cache: HIT
cf-cache-status: BYPASS
cf-ray: a5a9774ba87141f3-EWR
Sampled static assets
| Asset | Cache lifetime | Cache-Control |
|---|---|---|
| mechanicalkeyboard.net/wp-con…6e61a95e3589f2.css?ver=6.2.17 | 10 years | public, max-age=315360000 |
| mechanicalkeyboard.net/wp-inc…query/jquery.min.js?ver=3.7.1 | 10 years | public, max-age=315360000 |
| mechanicalkeyboard.net/wp-con…21_50_PM-removebg-preview.png | 1 year | max-age=31536000 |
| mechanicalkeyboard.net/wp-con…bc09b8fd3f5f74ae4.css?ver=3.1 | 10 years | public, max-age=315360000 |
| mechanicalkeyboard.net/wp-inc…uery-migrate.min.js?ver=3.4.1 | 10 years | public, max-age=315360000 |
| mechanicalkeyboard.net/wp-con…ploads/2026/02/Light-Logo.png | 1 year | 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 4 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
1.88 MB in 39 requests · 55% of page weight · Mobile
1.8 MB in 39 requests · 47% of page weight · Desktop
Eliminate render-blocking resources
21 stylesheets and scripts block the first paint.
Evidence
- mechanicalkeyboard.net/wp-content/cache…3396f51f0423a44eb448b5201.css?ver=2.7.7 (1.1 s)
- mechanicalkeyboard.net/wp-content/plugi…r/assets/css/frontend.min.css?ver=4.3.6 (631 ms)
- mechanicalkeyboard.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (631 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
903 KB of downloaded JavaScript was never executed during page load.
Evidence
- www.gstatic.com/recaptcha/releases/4i3aN5wAweL7i3ADI7BSX4B-/recaptcha__en.js (205 KB could be saved)
- www.gstatic.com/recaptcha/releases/4i3aN5wAweL7i3ADI7BSX4B-/recaptcha__en.js (183 KB could be saved)
- www.gstatic.com/recaptcha/releases/4i3aN5wAweL7i3ADI7BSX4B-/recaptcha__en.js (182 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 JavaScriptMinify JavaScript
JavaScript files are served unminified; minifying would save about 12 KB.
Evidence
- mechanicalkeyboard.net/wp-content/themes/foxiz/assets/js/global.js?ver=2.7.7 (10 KB could be saved)
- mechanicalkeyboard.net/wp-content/plugins/foxiz-core/assets/core.js?ver=2.8.0 (2 KB could be saved)
Why it matters
Whitespace and long names add download and parse time without any benefit to visitors.
How to fix
Minify JavaScript as part of the build, or enable minification in your performance plugin.
In Warp PerformanceWarp Performance → JavaScript → Minify JavaScript
CSS
219 KB in 28 requests · 6% of page weight · Mobile
219 KB in 28 requests · 6% of page weight · Desktop
Remove unused CSS
78 KB of CSS rules are not used by this page.
Evidence
- mechanicalkeyboard.net/wp-content/cache…3396f51f0423a44eb448b5201.css?ver=2.7.7 (59 KB could be saved)
- mechanicalkeyboard.net/wp-content/cache…06ffb9fc8ac52118ec8be0a06.css?ver=6.1.1 (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
584 KB in 29 requests · 17% of page weight · Mobile
1.03 MB in 44 requests · 27% of page weight · Desktop
Optimize image delivery
Images are larger than they need to be: resizing, recompressing or converting them would save about 115 KB.
Evidence
- i.ytimg.com/vi/wW9Zy83i4RM/maxresdefault.jpg (96 KB could be saved)
- mechanicalkeyboard.net/wp-content/uploa…_2026__06_21_50_PM-removebg-preview.png (19 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 ImagesLoad the LCP image sooner
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
303 KB in 7 requests · 9% of page weight · Mobile
303 KB in 7 requests · 8% 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
2.4 MB from other domains in 48 requests · 70% of page weight
| Service | Transfer size | Requests | Main-thread blocking |
|---|---|---|---|
| Google reCAPTCHA | 1.48 MB | 12 | — |
| Google AdSense | 336 KB | 6 | — |
| Google Analytics | 181 KB | 2 | — |
| Google Fonts | 154 KB | 5 | — |
| YouTube | 124 KB | 1 | — |
| Google Ads | 9 KB | 2 | — |
Reduce the impact of third-party code
Scripts and resources from other companies account for 2.4 MB of this page.
Evidence
- Third-party code: 2.4 MB (70% of page weight) across 48 requests
- www.gstatic.com — 1.45 MB
- pagead2.googlesyndication.com — 336 KB
- www.googletagmanager.com — 180 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
- None
- Content-Type
- text/html; charset=UTF-8
- Vary
- Accept-Encoding
Reduce total page weight
The page transfers 3.41 MB, well above the 1.6 MB that keeps mobile loads fast.
Evidence
- Total transferred: 3.41 MB in 123 requests
- www.gstatic.com/recaptcha/releases…AweL7i3ADI7BSX4B-/recaptcha__en.js — 352 KB
- www.gstatic.com/recaptcha/releases…AweL7i3ADI7BSX4B-/recaptcha__en.js — 352 KB
- www.gstatic.com/recaptcha/releases…AweL7i3ADI7BSX4B-/recaptcha__en.js — 352 KB
Why it matters
Heavy pages are slow on mobile networks and costly for visitors on metered data.
How to fix
Start with the largest files listed here: compress or resize media and remove code that is not used.
Technology
-
WordPress Detected
- Asset paths under /wp-content/
- Asset paths under /wp-includes/
- REST API discovery link (api.w.org)
- Generator meta tag: WordPress
- link: </sitemap_index.xml>; rel="sitemap", </llms.txt>; rel="describedby"; type="text/markdown", <https://mechanicalkeyboar…
-
PHP Detected
- Implied by WordPress
-
Cloudflare Detected
- cf-ray: a5a97661dfec4f3a-EWR
- cf-cache-status: BYPASS
- server: cloudflare
WordPress
- Theme
- foxiz
- REST API
- Advertised
- Plugins visible in the page
- 4 plugins
Optimization tools
- Autoptimize Detected Assets under /cache/autoptimize/
Plugins referenced by asset paths
elementor
fluentform
foxiz-core
mp3-music-player-by-sonaar