Real visitors (Chrome UX Report)
Not enough Chrome traffic for field data on this page or its site, so only the lab run above is available.
Why is this different from the score in my browser?
The graded score is the desktop run. Lighthouse 13.5.0 runs at Google
through the PageSpeed Insights API on a desktop profile with no CPU or network throttling
— close to what Chrome DevTools on a laptop, GTmetrix's default test and the PageSpeed
API (which defaults to desktop) all measure, so this is the number you should be able to
reproduce: run it yourself on PageSpeed Insights.
Google ranks on mobile. That run happens too, on an emulated mid-range
Android with a 4× CPU slowdown and a throttled connection, and the same page routinely
scores 30–50 points lower there. Neither number is wrong — they are different tests.
On this page the mobile run scored 52 (F) against
69 (D) here —
to see every check graded on that run.
Lighthouse also varies a few points run to run on the same URL. Treat a trend across
several scans as the signal, never a single digit.
Lab data: Google PageSpeed Insights (Lighthouse, desktop).
Server probes (TTFB, compression, cache, headers) are measured separately from
Vilnius, Lithuania (EU).
Real visitors (Chrome UX Report)
Not enough Chrome traffic for field data on this page or its site, so only the lab run above is available.
Why is this different from the score in my browser?
This view grades the mobile run. Lighthouse 13.5.0 runs at Google
through the PageSpeed Insights API on an emulated mid-range Android with a 4× CPU
slowdown and a throttled connection. Chrome DevTools on your own machine, on the Desktop
preset, applies almost none of that, and the same page routinely scores 30–50 points
higher there. Neither number is wrong — they are different tests.
Mobile is what Google ranks on, so this is the number that affects your
search performance. On this page the desktop run scored 69 (D) against
52 (F) here —
to see every check graded on that run. To reproduce it, open the same run on PageSpeed Insights,
or pass strategy=mobile to the PageSpeed API — it defaults to desktop.
Lighthouse also varies a few points run to run on the same URL. Treat a trend across
several scans as the signal, never a single digit.
Lab data: Google PageSpeed Insights (Lighthouse, mobile).
Server probes (TTFB, compression, cache, headers) are measured separately from
Vilnius, Lithuania (EU).
✓Platform detectedNot conclusively identified — every check below links the official guideline for its fix, valid on any stack.
→Act on it with your AIThe machine-readable twin of this report gives an agent every failing check with its evidence, remediation and guideline link.
→Check the originHosting sets the floor on TTFB. xCloud hosts any stack — agent/MCP access built in, bring-your-own-server pricing.
This does not look like a WordPress site, so xSpeed cannot automate the fixes directly — but Every check below links its official guideline, and the machine-readable twin of this report gives an AI everything it needs to plan the work (8 checks name a concrete remediation):
Read the speed report at https://xspeedcache.com/scan/r/www-forever-promises-com-78c69206a5.md — it lists every failing check with evidence and the official guideline for the fix. Produce a prioritized fix plan for my stack, apply what you can, then re-test by POSTing {"url":"https://www.forever-promises.com/"} to https://xspeedcache.com/api/scan and compare the scores.
Hosting is half of every score.Whatever the stack, the server behind it sets the floor on TTFB. xCloud — from the team behind xSpeed — hosts any platform (this site's own scanner runs on it), with agent/MCP access built in and bring-your-own-server pricing.Explore xCloud.host →
Run this scan without the form
Plug xSpeed Scan into your agent stack, or test any site from a chat.
Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
xSpeed FreePage Cache + Preloader (Critical CSS in Pro)AI promptUsing my site's xSpeed MCP connection: enable page caching, start the preloader, and (on Pro) generate critical CSS for this page; then re-test LCP.
TTFB 116ms measured from Vilnius, Lithuania (EU) (best of 2 requests). This includes the network round trips between us and your origin, not just server time. Google measured your server responding in 6ms from its own network — the gap between the two numbers is distance, not your server.
Served as gzip: 38KB. The same page as Brotli is 32KB — 5.2KB smaller on every uncached view.
Your server can produce a much smaller Brotli response but serves gzip. Prefer Brotli for HTML.
xSpeed FreeGZIP (Brotli in Pro)AI promptUsing my site's xSpeed MCP connection: check how the HTML is compressed, make sure the served encoding is the smaller of gzip and Brotli, then confirm the response size.
Every asset with a short cache lifetime here is served by another host (cdn.prod.website-files.com, cdn.fontshare.com, api.fontshare.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
xSpeed FreeBrowser CacheAI promptUsing my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.
Fails the Lighthouse audit — 4 files: foreverpromises.webflow.shared.7ec283daf.min.css (cdn.prod.website-files.com), css (api.fontshare.com), css2 (fonts.googleapis.com)… · ~450ms of first paint
Everything blocking first paint here is loaded from another host (cdn.prod.website-files.com, api.fontshare.com, fonts.googleapis.com). You cannot inline or minify those — the fix is to defer them, or load fewer of them.
xSpeed ProCritical CSS + Unused CSS removalAI promptUsing my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.
Fails the Lighthouse audit — 8 files: 6a51742b4e9c9c7370221b20_AM_dinner_engagement.webp (cdn.prod.website-files.com), 67b6d3995717f015c06e039f_Beach_proposal_marriage.avif (cdn.prod.website-files.com), 6832f3d3f233131a073d615a_JL_dinner_proposal_Bali-p-1600.webp (cdn.prod.website-files.com)… · ~200ms of first paint
Every image flagged here is served from another host (cdn.prod.website-files.com), so converting them is not yours to do — the fix is to host them yourself, or load fewer.
xSpeed ProImage Converter (WebP/AVIF)AI promptUsing my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.
xSpeed FreeResource Hints (preload) + Lazy Load exclusionsAI promptUsing my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.
Total page weight (≤ 350KB for full marks) 0/3 pts
28.7MB transferred — over 1,500KB
Page weight is what decides mobile LCP once the server is fast. Resize images to the size they display at, lazy-load below the fold, and drop scripts the page does not use.
xSpeed FreeMinify + Lazy Load + Image Converter (Pro)AI promptUsing my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.
Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
xSpeed FreePage Cache + Preloader (Critical CSS in Pro)AI promptUsing my site's xSpeed MCP connection: enable page caching, start the preloader, and (on Pro) generate critical CSS for this page; then re-test LCP.
TTFB 116ms measured from Vilnius, Lithuania (EU) (best of 2 requests). This includes the network round trips between us and your origin, not just server time. Google measured your server responding in 5ms from its own network — the gap between the two numbers is distance, not your server.
Served as gzip: 38KB. The same page as Brotli is 32KB — 5.2KB smaller on every uncached view.
Your server can produce a much smaller Brotli response but serves gzip. Prefer Brotli for HTML.
xSpeed FreeGZIP (Brotli in Pro)AI promptUsing my site's xSpeed MCP connection: check how the HTML is compressed, make sure the served encoding is the smaller of gzip and Brotli, then confirm the response size.
Every asset with a short cache lifetime here is served by another host (cdn.prod.website-files.com, cdn.fontshare.com, api.fontshare.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
xSpeed FreeBrowser CacheAI promptUsing my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.
Fails the Lighthouse audit — 4 files: css (api.fontshare.com), foreverpromises.webflow.shared.7ec283daf.min.css (cdn.prod.website-files.com), css2 (fonts.googleapis.com)… · ~1.6s of first paint
Everything blocking first paint here is loaded from another host (api.fontshare.com, cdn.prod.website-files.com, fonts.googleapis.com). You cannot inline or minify those — the fix is to defer them, or load fewer of them.
xSpeed ProCritical CSS + Unused CSS removalAI promptUsing my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.
Fails the Lighthouse audit — 4 files: 67b6d3995717f015c06e039f_Beach_proposal_marriage-p-800.jpg (cdn.prod.website-files.com), 68dc89ef58f904eca59058e4_Couple_just_engaged_bali-p-800.webp (cdn.prod.website-files.com), 66d5b346bde6ad05c72b0c62_hhh.png (cdn.prod.website-files.com)… · ~600ms of first paint
Every image flagged here is served from another host (cdn.prod.website-files.com), so converting them is not yours to do — the fix is to host them yourself, or load fewer.
xSpeed ProImage Converter (WebP/AVIF)AI promptUsing my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.
xSpeed FreeResource Hints (preload) + Lazy Load exclusionsAI promptUsing my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.
Total page weight (≤ 350KB for full marks) 0/3 pts
24.7MB transferred — over 1,500KB
Page weight is what decides mobile LCP once the server is fast. Resize images to the size they display at, lazy-load below the fold, and drop scripts the page does not use.
xSpeed FreeMinify + Lazy Load + Image Converter (Pro)AI promptUsing my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.
Scan www-forever-promises-com-78c69206a5 · rubric v2026.10.1 · Lab data: Google PageSpeed Insights (Lighthouse 13.5.0), graded on the desktop run; the mobile run is graded on its tab · Server probes from xspeedcache.com.
Scores vary run to run; treat trends, not single digits, as the signal.
Markdown for AI agents · JSON Own www.forever-promises.com and would rather this report were not public? Email
support@wpdeveloper.com and we will remove it.