Website review, no card needed
medusajs.com website review
Visit site (opens in a new tab)Reviewed 22 October 202627 issues · 76 checks
This review found 27 issues worth fixing on medusajs.com, 11 of them high impact, across 76 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 206 ms |
| May 9, 2026 | 209 ms |
| May 16, 2026 | 195 ms |
| May 23, 2026 | 187 ms |
| May 30, 2026 | 184 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 184 ms |
| Jun 27, 2026 | 184 ms |
| Jul 4, 2026 | 182 ms |
| Jul 11, 2026 | 174 ms |
| Jul 18, 2026 | 168 ms |
| Jul 25, 2026 | 160 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 160 ms |
| Aug 15, 2026 | 158 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 158 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 157 ms |
| Sep 19, 2026 | 157 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 159 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 159 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Improve image delivery
8.3 s · 8.5 MB8 images could be 8.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.3 s faster on a phone.
Reduce unused JavaScript
2.8 s · 568 KiBAbout 568 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.
Mobile performance score: 46
46/100Your mobile performance score is 46 (desktop: 53). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
750 ms · 118 KiB3 files are served with short cache lifetimes, so returning visitors download them again (118 KiB).
Render-blocking requests
400 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 361 ms. During a long task the page ignores taps.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
200 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
150 ms · 34 KiBAbout 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, reo.dev and Segment and others), adding 319 KiB and 137 ms of main-thread time.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 42.1 s
42.1 sYour largest element takes 42.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “commerce stack”.
Time to Interactive: 44.0 s
44.0 sThe page becomes fully interactive after 44.0 s. Good is under 3.8 s.
Speed Index: 13.4 s
13.4 sVisually, the page fills in at 13.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 491 ms
491 msScripts block taps and scrolling for 491 ms in total while the page loads. Good is under 200 ms.
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 180 ms
180 msReal visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 670 ms
670 msReal visitors wait 670 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 206 ms to 159 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 13.9 MB in 75 requests
13.9 MBYour homepage downloads 13.9 MB in 75 requests on a phone: images 9.5 MB (25), media 3.1 MB (2) and scripts 1.1 MB (27). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 9.1 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.4 MB2 images are downloaded at several times the size a phone draws them, for example cloud.069d6e31.png at 6,144 px wide, shown at 1,125 px. Resized copies would save about 1.4 MB.
5 images in older formats
5 images (9.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
1 image below the first screen load straight away
1 image further down the page (136 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.9 g of CO₂ per visit
3.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.94 g of CO₂e: 473.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 69 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (62 characters)
Your meta description is only 62 characters: “The most flexible commerce platform for agents and developers.”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“Open-Source Agentic Commerce Platform” and “Build and operate your commerce stack with agents”). One clear main headline is easier for people and search engines.
53 internal links, 43 external
The homepage links to 53 pages on medusajs.com and 43 external pages.
6 checks passed
Title: 46 characters
Your title is a healthy 46 characters: “Medusa - Open-Source Agentic Commerce Platform”.
Canonical URL set
The canonical URL is https://medusajs.com/index.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://medusajs.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (706 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://medusajs.com/llms.txt (21 KiB, 94 links), a plain-text guide to the site for AI tools.
Other pages
9 pages share a meta description
https://medusajs.com/enterprise, https://medusajs.com/modules, https://medusajs.com/framework, https://medusajs.com/starters, https://medusajs.com/integrations and https://medusajs.com/cloud and 3 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
12 of 14 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 417 words of copy
The homepage carries about 417 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start for free” and “Contact sales”.
11 calls to action
The homepage has 11 calls to action, for example “Pricing”, “View demo” and “Start for free”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 3 customer or partner logos.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Segment (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at medusajs.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on medusajs.com, including 12 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.