Magento store health checkSample report

www.yourdomain.com

Measured November 18, 2026 · Public pages only

This is a sample. The store and its findings are illustrative.

The store is in good shape. Real visitors get pages that load and respond within Google's targets, and the store passes Core Web Vitals on mobile and desktop. The pages are heavier than they need to be: oversized banner images and video players loaded on page open. Product data covers the basics but misses shipping details and product identifiers. One of five AI crawlers is blocked at the firewall, although robots.txt allows it.

3 needs attention1 good

Fix first

  1. Serve banner images at the size they are shown. This is the largest part of the page weight.
  2. Add shipping details and product identifiers to the product markup, so Google can show delivery cost and match your products.
  3. Load video players only when a visitor clicks play.
5 fixes in the plan 4 medium1 low $710 total for all fixes See the fix plan →
01

Speed for real visitors

!Passes Core Web Vitals, pages are heavyRoom to improve

Fixes in the plan: #1 #3 #5

Chrome UX Report data: what real Chrome users experienced on the whole site over the last 28 days, at the 75th percentile, as Google measures it.

MetricTargetMobileDesktop
LCPCore Web Vitalmain content visible 2.5 s or less ✓2.3 s ✓1.9 s
INPCore Web Vitalresponse to taps and clicks 200 ms or less ✓160 ms ✓120 ms
CLSCore Web Vitallayout shift 0.1 or less ✓0.06 ✓0.04
TTFBfirst byte from server 0.8 s or less !0.9 s ✓0.7 s
FCPfirst content 1.8 s or less ✓1.7 s ✓1.3 s

LCP, INP and CLS are the three Core Web Vitals. All three are good on mobile and desktop, so the store passes. Mobile LCP is 2.3 s against a limit of 2.5 s, so heavier pages could push it over.

What makes the pages heavy

  1. Home page banners are stored at full size. A 2400 px wide image is sent to a slot about 800 px wide, on phones too.
  2. Two embedded videos load the full YouTube player as soon as the page opens, before anyone presses play.
  3. The address without www. first redirects to www., which adds a round trip before the page starts loading.

Lab test

Google's lab test (PageSpeed Insights, home page) simulates a mid-range phone on a slow connection. Its scores are harsher than real visits, but it shows what makes the page heavy.

FindingMeasured
Total page weight7.8 MB
Banner images larger than shown, for example 2400 px wide in an 800 px slotabout 1.2 MB extra on mobile
YouTube players loaded on page open (2 embedded videos)about 0.5 MB of player script each
Redirect from yourdomain.com to www.0.4 s on mobile
↑ Back to summary
02

Magento and PHP versions

✓Magento 2.4.7, supported until May 2027Supported

What we see

  • Magento Open Source 2.4.7-p6, the release you named in your order. Public signals match release line 2.4.
  • PHP version: not exposed by the server. That is good practice.
  • Theme: Luma-based custom theme.

Why it matters

  • Magento 2.4.7 gets security fixes until May 31, 2027, so there is no rush.
  • Plan the move to 2.4.8 for 2027, so it does not land in your next peak season.
  • Share your composer.lock and we will check every extension for 2.4.8.
Magento releasePHPSecurity support
2.4.68.1, 8.2✕Ended August 11, 2026
2.4.78.2, 8.3✓May 31, 2027
2.4.88.3, 8.4May 31, 2028
2.4.98.5May 31, 2029

Dates from Adobe's Magento lifecycle page and php.net. Extended support exists only for paid Adobe Commerce, not for Open Source.

↑ Back to summary
03

Product structured data

!Good basics, two gapsNeeds attention

Fixes in the plan: #2

We read the product page markup the way Google reads it from the HTML. Sample page: /sample-product.html.

FieldStatusWhy it matters
Product, name, image, description, SKU✓PresentBasis for Google Shopping and product rich results
Price and currency✓PresentPrice shown in search results
Availability✓Present"In stock" in results
Brand✓PresentProduct identifier for Google
Shipping and return policy!MissingWithout it Google cannot show delivery cost and returns in results
GTIN or MPN!MissingWith brand, a GTIN or MPN makes the product easier to match
One product description per page✓One foundGoogle reads a single product description, nothing to choose between
Review rating–Not foundAdd it only if reviews are shown on the page. That is Google's rule

Home page: meta description and canonical link are present.

↑ Back to summary
04

AI crawler access

!1 of 5 blocked, robots.txt says allowInconsistent

Fixes in the plan: #4

We requested the home page from a US address under the names of five AI crawlers and compared the answer with your robots.txt.

CrawlerUsed forrobots.txtServer answer
OAI-SearchBotChatGPT search resultsNo rule, allowed✓200 served
ChatGPT-UserChatGPT opening a page for a userNo rule, allowed✓200 served
PerplexityBotPerplexity answersNo rule, allowed✓200 served
GPTBotOpenAI model trainingNo rule, allowed✓200 served
ClaudeBotAnthropic model trainingNo rule, allowed✕403 blocked

AI search tools can reach the store. One training crawler is blocked by the firewall before the request reaches Magento, while robots.txt allows it. Blocking training crawlers is a fair business choice. The point is to make it a decision, set in one place.

The test identifies itself by crawler name only. Firewalls and CDNs also check whether a request really comes from the crawler's published addresses, so real crawlers may be treated differently. Confirm in your firewall or CDN bot settings.

robots.txt

  • One group for all crawlers closes checkout, customer account and search result URLs. That is a clean setup.
  • No crawl-delay, so crawlers that follow robots.txt are not slowed down.
  • The sitemap is listed and answers normally.
↑ Back to summary
05

Upgrade estimate

Not included in this report

The estimate needs your composer.lock file, which lists every installed extension and its version. Without it we can name only what is visible from outside: the theme and a few extensions.

With the file you get: your exact Magento release, every extension marked as compatible, needs a vendor update, or needs code changes, and an approximate cost of the upgrade. The upgrade itself is a separate package.

↑ Back to summary
06

Fix plan

5 fixes4 medium1 low

Ranked by impact. Each item has a fixed price. Order any of them from us, or hand this plan to your own developer.

2 quick fixes: settings or one file

#FixImpactQuick fixPrice
1 Serve banner images at the size they are shown 01Speed mediumabout 1.2 MB lighter After: theme code $190
2 Add shipping, return policy and GTIN or MPN to the product markup 03Product data medium After: theme code $190
3 Load YouTube players on click instead of on page open 01Speed mediumlighter page After: theme code $150
4 Align AI crawler access between the firewall and robots.txt 04AI crawlers medium Yes: settings only $90
5 Remove the extra redirect: one rule, links and ads to www. 01Speed lowabout 0.4 s Yes: settings only $90
All fixes$710

"Quick fix" marks changes that touch only settings or one file. Theme code changes are safer outside your busiest season, unless they are tested on a staging copy first.

↑ Back to summary

Use this plan your way

  • Hand it to your developer.

    Every fix is ranked by impact. Quick fixes can go first, theme code after your sales peak.

  • Or have us do it.

    Order any item at its fixed price, one at a time or all together.

    Order the health check

Either way, the report is yours. You don't need to buy anything else.

How to check it yourself

  • Speed for real visitors: PageSpeed Insights, section "Discover what your real users are experiencing". It updates over 28 days after a fix. pagespeed.web.dev
  • Product data: Rich Results Test with a product page address. search.google.com
  • robots.txt: Google Search Console, Settings, robots.txt report.

Method

  • Only public pages were requested, from a US address: the home page, robots.txt, the sitemap and one product page. No admin, server or checkout access.
  • Real-visitor data comes from Google's Chrome UX Report through PageSpeed Insights, measured November 18, 2026.
  • Lab results describe one simulated visit and vary from run to run. Real-visitor data has priority.
  • One product page was reviewed. Other product types may differ.