Skip to report
Scan another site

Performance report

www.bakerita.com

Scanned www.bakerita.com

  • WordPress
  • PHP
  • Cloudflare

80 out of 100

Warp Score

B Good

TTFB — Goodserver response
26 ms
LCP — Poorlab
4.7 s
LCP — Goodlab
0.8 s
INP — Goodreal users
88 ms
CLS — Goodlab
0
CLS — Goodlab
0
Desktop — Needs improvementLighthouse
87
Mobile — Needs improvementLighthouse
77
Transfer
2.83 MB
Transfer
3.01 MB
Requests
154
Requests
161
Share on X Share on LinkedIn

Overview

Score breakdown

Performance

B

81 / 100

Lighthouse scored this page 77 on mobile and 87 on desktop.

Core Web Vitals

A+

96 / 100

Real visitors pass Core Web Vitals on this page, with a 75th-percentile LCP of 1.1 s.

Server & Cache

A+

100 / 100

HTML is served from cache by Cloudflare with a warm TTFB of 26 ms.

Assets

F

33 / 100

2.83 MB transferred in 154 requests, including 1.41 MB of JavaScript.

Delivery

A+

100 / 100

Delivered with HTTP/2, Brotli compression, Cloudflare.

Top improvements

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

    8 stylesheets and scripts block the first paint.

    Evidence

    • www.bakerita.com/wp-content/plugins/wp-…maker/dist/public-modern.css?ver=10.9.1 (819 ms)
    • www.bakerita.com/wp-content/themes/bakerita2022/style.css?ver=1.12 (819 ms)
    • www.bakerita.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (655 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. Reduce unused JavaScriptHigh impactPotential savings: 1.1 MB

    1.1 MB of downloaded JavaScript was never executed during page load.

    Evidence

    • blob:https://www.bakerita.com/c76d2b53-5f13-41ea-b9b8-d90a8630a901 (381 KB could be saved)
    • ads.adthrive.com/builds/core/05419b5/js…,internalScriptLogError,ld,marmaladeV2, (273 KB could be saved)
    • securepubads.g.doubleclick.net/pagead/m…ged/js/gpt/m202611100101/pubads_impl.js (163 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
  3. Optimize image deliveryHigh impactPotential savings: 477 KB

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

    Evidence

    • www.bakerita.com/wp-content/uploads/202…o-White-Bean-Stew-Recipe-15-528x704.jpg (157 KB could be saved)
    • www.bakerita.com/wp-content/uploads/2017/06/Chocolate-Beet-Donuts-4-528x704.jpg (59 KB could be saved)
    • www.bakerita.com/wp-content/uploads/202…-Peanut-Dense-Bean-Salad-13-348x464.jpg (56 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
  4. Reduce the impact of third-party codeHigh impact

    Scripts and resources from other companies account for 1.73 MB of this page.

    Evidence

    • Third-party code: 1.73 MB (61% of page weight) across 99 requests
    • ads.adthrive.com — 799 KB
    • www.googletagmanager.com — 306 KB
    • securepubads.g.doubleclick.net — 280 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. 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 more findings are listed in the other tabs.

Page weight

2.83 MB transferred · 154 requests · Mobile

  • JavaScript 1.41 MB 16 requests
  • Images 941 KB 41 requests
  • Other 304 KB 80 requests
  • HTML 101 KB 5 requests
  • Fonts 66 KB 5 requests
  • CSS 43 KB 7 requests

3.01 MB transferred · 161 requests · Desktop

  • JavaScript 1.41 MB 16 requests
  • Images 1.1 MB 49 requests
  • Other 302 KB 79 requests
  • HTML 101 KB 5 requests
  • Fonts 66 KB 5 requests
  • CSS 43 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

Passes Core Web Vitals

Mobile visitors · data for this page

LCP p75 — Good
1.1 s
INP p75 — Good
88 ms
CLS p75 — Good
0.01
TTFB p75 — Good
544 ms
FCP p75 — Good
1.0 s

Desktop visitors · data for this page

LCP p75 — Good
0.8 s
INP p75 — Good
70 ms
CLS p75 — Good
0.03
TTFB p75 — Good
396 ms
FCP p75 — Good
0.8 s

Lab test Google Lighthouse · simulated load

Mobile

Lighthouse — Needs improvement
77
LCP — Poor
4.7 s
FCP — Good
1.5 s
TBT — Needs improvement
264 ms
Speed Index — Good
3.2 s
CLS — Good
0

Desktop

Lighthouse — Needs improvement
87
LCP — Good
0.8 s
FCP — Good
0.3 s
TBT — Needs improvement
303 ms
Speed Index — Good
0.7 s
CLS — Good
0

Server & Cache

TTFB (server response)
26 ms
HTML cache
Cloudflare Confirmed
CDN
Cloudflare HTML caching: Confirmed
Compression
Brotli
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
67 ms
TCP
2 ms
TLS
17 ms
First-byte wait
32 ms
Total
51 ms
HTML size
62 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: 159184 (first request)
  • cf-cache-status: HIT (repeat request)
  • age: 159216 (repeat request)

Response headers (first request)

cache-control: public, max-age=0, must-revalidate
age: 159184
last-modified: Thu, 12 Nov 2026 18:16:45 GMT
vary: Accept, Accept-Encoding
server: cloudflare
content-type: text/html; charset=UTF-8
content-encoding: br
alt-svc: h3=":443"; ma=86400
strict-transport-security: max-age=31536000; includeSubdomains;
cf-cache-status: HIT
cf-ray: a5a6b435ef91574c-EWR
cdn-cache-control: max-age=31536000, stale-while-revalidate=60, stale-if-error=3600

Response headers (repeat request, 26 ms)

cache-control: public, max-age=0, must-revalidate
age: 159216
last-modified: Thu, 12 Nov 2026 18:16:45 GMT
vary: Accept, Accept-Encoding
server: cloudflare
content-type: text/html; charset=UTF-8
content-encoding: br
alt-svc: h3=":443"; ma=86400
strict-transport-security: max-age=31536000; includeSubdomains;
cf-cache-status: HIT
cf-ray: a5a6b4fd3e63e8c4-EWR
cdn-cache-control: max-age=31536000, stale-while-revalidate=60, stale-if-error=3600

Sampled static assets

Asset Cache lifetime Cache-Control
www.bakerita.com/wp-content/p…sbi-styles.min.css?ver=6.10.0 1 year public, immutable, max-age=31536000, stale-while-revalidate=86400, stale-if-error=604800
www.bakerita.com/wp-includes/…query/jquery.min.js?ver=3.7.1 1 year public, immutable, max-age=31536000, stale-while-revalidate=86400, stale-if-error=604800
www.bakerita.com/wp-content/t…mobile-header/logo-mobile.png 1 year public, immutable, max-age=31536000, stale-while-revalidate=86400, stale-if-error=604800
www.bakerita.com/wp-content/t…e-subset/css/all.css?ver=1.01 1 year public, immutable, max-age=31536000, stale-while-revalidate=86400, stale-if-error=604800
www.bakerita.com/wp-includes/…uery-migrate.min.js?ver=3.4.1 1 year public, immutable, max-age=31536000, stale-while-revalidate=86400, stale-if-error=604800
www.bakerita.com/wp-content/t…kerita2022/images/logo@2x.png 1 year public, immutable, max-age=31536000, stale-while-revalidate=86400, stale-if-error=604800
  • Improve static asset cache lifetimeLow impactPotential savings: 538 KB

    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 6 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.41 MB in 16 requests · 50% of page weight · Mobile

1.41 MB in 16 requests · 47% of page weight · Desktop

  • Eliminate render-blocking resourcesHigh impactPotential savings: 4.6 s

    8 stylesheets and scripts block the first paint.

    Evidence

    • www.bakerita.com/wp-content/plugins/wp-…maker/dist/public-modern.css?ver=10.9.1 (819 ms)
    • www.bakerita.com/wp-content/themes/bakerita2022/style.css?ver=1.12 (819 ms)
    • www.bakerita.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 (655 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 JavaScriptHigh impactPotential savings: 1.1 MB

    1.1 MB of downloaded JavaScript was never executed during page load.

    Evidence

    • blob:https://www.bakerita.com/c76d2b53-5f13-41ea-b9b8-d90a8630a901 (381 KB could be saved)
    • ads.adthrive.com/builds/core/05419b5/js…,internalScriptLogError,ld,marmaladeV2, (273 KB could be saved)
    • securepubads.g.doubleclick.net/pagead/m…ged/js/gpt/m202611100101/pubads_impl.js (163 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

43 KB in 7 requests · 1% of page weight · Mobile

43 KB in 7 requests · 1% of page weight · Desktop

  • Remove unused CSSLow impactPotential savings: 26 KB

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

    Evidence

    • .adthrive-act25-overlay{z-index:2147483…00%;height:100%;display:none; … } … (15 KB could be saved)
    • www.bakerita.com/wp-content/themes/bakerita2022/style.css?ver=1.12 (11 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
  • Minify CSSLow impactPotential savings: 2 KB

    CSS files are served unminified; minifying would save about 2 KB.

    Evidence

    • www.bakerita.com/wp-content/themes/bakerita2022/style.css?ver=1.12 (2 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

941 KB in 41 requests · 32% of page weight · Mobile

1.1 MB in 49 requests · 36% of page weight · Desktop

  • Optimize image deliveryHigh impactPotential savings: 477 KB

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

    Evidence

    • www.bakerita.com/wp-content/uploads/202…o-White-Bean-Stew-Recipe-15-528x704.jpg (157 KB could be saved)
    • www.bakerita.com/wp-content/uploads/2017/06/Chocolate-Beet-Donuts-4-528x704.jpg (59 KB could be saved)
    • www.bakerita.com/wp-content/uploads/202…-Peanut-Dense-Bean-Salad-13-348x464.jpg (56 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
  • Add width and height to imagesLow impact

    8 images have no explicit dimensions.

    Evidence

    • www.bakerita.com/wp-content/uploads/sb-…6052594_6660934434843598692_nthumb.webp
    • www.bakerita.com/wp-content/uploads/sb-…8052594_4831311483298668780_nthumb.webp
    • www.bakerita.com/wp-content/uploads/sb-…0301618_5827035347824565827_nthumb.webp

    Why it matters

    Without dimensions the browser cannot reserve space, so content jumps when the image arrives. That movement is measured as CLS.

    How to fix

    Set width and height attributes (or a CSS aspect-ratio) on every image.

    Related metric: CLS

    In Warp PerformanceWarp Performance → Media → Add Missing Dimensions

Fonts

66 KB in 5 requests · 2% of page weight · Mobile

66 KB in 5 requests · 2% of page weight · Desktop

  • Keep text visible while fonts loadLow impactPotential savings: 85 ms

    5 web fonts hide text until they have loaded.

    Evidence

    • www.bakerita.com/wp-content/themes/bake…me-subset/webfonts/fa-regular-400.woff2 (20 ms)
    • www.bakerita.com/wp-content/themes/bake…ome-subset/webfonts/fa-brands-400.woff2 (20 ms)
    • use.typekit.net/af/ebcd51/0000000000000…bbc383831fe2ea177f62257a9191&fvd=n7&v=3 (15 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.73 MB from other domains in 99 requests · 61% of page weight

Service Transfer size Requests Main-thread blocking
Google Analytics 307 KB 3 —
Google AdSense 57 KB 1 —
  • Reduce the impact of third-party codeHigh impact

    Scripts and resources from other companies account for 1.73 MB of this page.

    Evidence

    • Third-party code: 1.73 MB (61% of page weight) across 99 requests
    • ads.adthrive.com — 799 KB
    • www.googletagmanager.com — 306 KB
    • securepubads.g.doubleclick.net — 280 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
Enabled
Cache-Control
public, max-age=0, must-revalidate
Validators
ETag / Last-Modified present
Content-Type
text/html; charset=UTF-8
Vary
Accept, Accept-Encoding

No delivery issues found.

Technology

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

WordPress

Theme
bakerita2022
REST API
Not advertised
Plugins visible in the page
3 plugins

Optimization tools

  • WP Rocket Likely detected WP Rocket attributes (data-rocket-*)
Plugins referenced by asset paths

instagram-feed wp-recipe-maker bigscoots-cache