xSpeed Cache is officially live! Get 50% OFF during Launch Week — Lifetime starts at just $79Lifetime from $79 — 50% OFF, Launch Week! See Plans →

See Plans →
Get Plugin xSpeed Hub
All features Cloudflare EnterpriseAdd-on

By what you run

WooCommerce storesAgencies & freelancersBlogs & publishersElementor & page buildersMembership & LMSAI & agents

By your business

Home & trade services 3 Food & hospitality 4 Health & wellness 5 Professional services 5 Retail & ecommerce 5 Creative & events 4 Publishing & media 4 Learning & community 4 Tech & agencies 3 With your AI agent All use cases & industries
xSpeed Hub Pricing Docs Blog Scan
Free vs Pro Compare Showcase Coverage Support Community
Appearance
Get Plugin
76of 100

mohaiminul-islam.vercel.app

Scanned Tue, 22 Sep 2026 08:19:29 GMT · https://mohaiminul-islam.vercel.app/

CLevel 4 · Fast
AstroVercel Edge
Scan a different site ›
Desktop view of mohaiminul-islam.vercel.app at scan time. Click for full size
As Lighthouse saw it · click to enlarge
209msTTFB
97Lighthouse desktop · graded
92Lighthouse mobile
642msLCP
0.00CLS
brCompression
HITCache

Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 70 (C) —

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 70 (C) against 76 (C) 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).

Lab performance (Lighthouse)A+99 5/5 checks passed · 39.5/40 pts Jump to section ↓ Server response & cachingB80 4/6 checks passed · 24/30 pts Jump to section ↓ Asset optimizationF13 0/4 checks passed · 2/16 pts Jump to section ↓

Astro what actually works on this platform

Astro ships no JavaScript unless you ask for it, so a slow Astro site is almost always one of two things: islands hydrating when they do not need to, or the HTML being built per request when it could have been built once.

  • The HTML came back from a cache — the build is not being repeated per visit, so look at what the page ships rather than at the server.
  • A crawler reads about 3,946 characters of text from your HTML — healthy, which is what Astro is good at.
  • Served through Vercel Edge.
  1. Check your client: directives before anything else. client:load hydrates an island immediately and costs the visitor JavaScript on first paint. client:visible defers it until the component scrolls into view and client:idle until the browser is free; most islands want one of those. A page full of client:load is the usual reason an Astro site feels heavy.
  2. Know whether each route is static or server-rendered. Astro can output a static file, render per request, or mix the two per route. A page with no per-visitor content that is rendered per request pays for it on every visit. Prerender the ones that can be, and let the CDN serve them.
  3. Use astro:assets for images. It emits modern formats at the sizes actually used and reserves the space so the layout does not shift. Raw <img> tags are usually the largest remaining payload on an otherwise lean Astro site.
  4. Watch what a shared layout pulls in. An import in a layout is charged to every page that uses it. One heavy component or icon set there outweighs anything you will save on an individual route.

The full instruction set, and a machine-readable copy of this report, live at mohaiminul-islam.vercel.app.md — paste that URL into your AI builder's chat and it can work straight from these measurements.

Top fixes ranked by points recovered · desktop

This is an Astro site — act on the report with your AI assistant

  1. ✓Platform detectedAstro — every check below links the official guideline for the fix in this stack.
  2. →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.
  3. →Check the originHosting sets the floor on TTFB. xCloud hosts any stack — agent/MCP access built in, bring-your-own-server pricing.

xSpeed is a WordPress plugin, so it can't automate Astro fixes — and that's fine. 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 (6 checks name a concrete remediation):

Read the speed report at https://xspeedcache.com/scan/r/tinyurl-com-46b1bc8923.md — it lists every failing check with evidence and the official guideline for the fix. Produce a prioritized fix plan for my Astro site, apply what you can, then re-test by POSTing {"url":"https://mohaiminul-islam.vercel.app/"} to https://xspeedcache.com/api/scan and compare the scores.
How the checks are graded Scan another site
Hosting is half of every score. Whatever the stack — Astro included, 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 →

Connect this scanner to your AI assistant

Free. No API key, no sign-up. Scan any public site and get the same graded report as this one, with the fix for every failing check.

Endpoint

https://xspeedcache.com/scan/mcp

Claude Code — one command

claude mcp add --transport http xspeed-scan https://xspeedcache.com/scan/mcp

Claude Desktop, Cursor, or any MCP client — add to your config

{ "mcpServers": { "xspeed-scan": { "type": "http", "url": "https://xspeedcache.com/scan/mcp" } } }
  • run_speed_scan Scan any public URL and return this whole graded report.
  • get_speed_scan Read a scan already run, by its id.
Read the MCP documentation →
A+

Lab performance (Lighthouse)

5/5 checks passed · 39.5/40 pts earned
99/100
Pass
Lighthouse performance score (desktop) 17.5/18 pts
97/100 (Lighthouse 13.5.0, desktop)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 642ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Cumulative Layout Shift ≤ 0.1 5/5 pts
CLS 0.001
Guidelines: web.dev — Cumulative Layout Shift
Pass
Total Blocking Time ≤ 200ms 5/5 pts
TBT 0ms
Guidelines: web.dev — Total Blocking Time
Pass
First Contentful Paint ≤ 1.8s 4/4 pts
FCP 326ms
Guidelines: web.dev — First Contentful Paint
B

Server response & caching

4/6 checks passed · 24/30 pts earned
80/100
Partial
Time to first byte ≤ 200ms 4/8 pts
TTFB 209ms 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 3ms from its own network — the gap between the two numbers is distance, not your server.
The server rebuilds the page on every request. A page cache answers in 5–15ms.
xSpeed Free Page Cache
AI promptUsing my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.
Guidelines: web.dev — Time to First Byte
Pass
Page served from cache 7/7 pts
Cache HIT evidence in response headers
Guidelines: MDN — HTTP caching
Pass
HTML compression (Brotli/GZIP) 5/5 pts
Content-Encoding: br
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Pass
Efficient cache policy on static assets 5/5 pts
Passes the Lighthouse cache-policy audit
Guidelines: Lighthouse — Efficient cache policy
Pass
CDN / edge network 3/3 pts
Vercel Edge detected
Guidelines: web.dev — Content delivery networks
Fail
Clean redirect chain 0/2 pts
3 redirect(s) before the final URL: 301→https://redirect.viglink.com?u=http%3A%2F%2Fmohaiminul-islam.vercel.app&key=a7e37b5f6ff1de9cb410158b1013e54a&prodOvrd=RAC&opt=false , 302→http://mohaiminul-islam.vercel.app , 308→https://mohaiminul-islam.vercel.app/
Each redirect adds a full round-trip before the page can even start.
Guidelines: Lighthouse — Avoid redirects
F

Asset optimization

0/5 checks passed · 2/16 pts earned
13/100
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 2 files: revamp.css, styles.css · ~50ms of first paint
CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
xSpeed Pro Critical CSS + Unused CSS removal
AI promptUsing my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.
Guidelines: Lighthouse — Render-blocking resources
Fail
Minified CSS and JavaScript 0/4 pts
Fails the Lighthouse audit — 1 file: revamp.css
Ship minified assets — whitespace and comments are pure transfer waste.
xSpeed Free HTML/CSS/JS Minify
AI promptUsing my site's xSpeed MCP connection: enable HTML, CSS and JS minification, purge the cache, and re-test.
Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Partial
Modern, optimized image formats 2/4 pts
Lighthouse audit score 50% — 8 files: be3e0ca8021b2b32addbbb8e216066b6cf4362eb-1080x1080.png (cdn.sanity.io), 3f6da9e8b1a74eb8cf661d234e7557a96a8dda62-24x24.svg (cdn.sanity.io), 0a76c5964a2f191c787bfed7e959bde7b0e4734c-1080x1080.png (cdn.sanity.io)…
Every image flagged here is served from another host (cdn.sanity.io), so converting them is not yours to do — the fix is to host them yourself, or load fewer.
xSpeed Pro Image Converter (WebP/AVIF)
AI promptUsing my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.
Guidelines: Lighthouse — Modern image formats
Info
LCP image discoverable early —
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Free Resource Hints (preload) + Lazy Load exclusions
AI promptUsing my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.
Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Fail
Total page weight ≤ 1.5MB 0/3 pts
4.6MB transferred
Heavy pages are slow on every connection — compress, lazy-load, and trim.
xSpeed Free Minify + 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.
Guidelines: Lighthouse — Total byte weight

Share your score a card for X, LinkedIn, Slack — anywhere

Every check here has a one-click fix in xSpeed Cache

Page caching, compression, image optimization and a built-in MCP server, so your AI assistant can run this playbook for you.

Get xSpeed Cache Scan another site
Scan tinyurl-com-46b1bc8923 · rubric v2026.09.5 · 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 mohaiminul-islam.vercel.app and would rather this report were not public? Email support@wpdeveloper.com and we will remove it.