Website review, no card needed
medicross.com website review
Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 84 checks
This review found 35 issues worth fixing on medicross.com, 14 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
77C- #61,430 of 109,350 reviewed websitesbeats 39%
- #39,793 of 61,859 online storesbeats 31%
- #37,892 of 56,401 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 194 ms |
| May 30, 2026 | 196 ms |
| Jun 6, 2026 | 196 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 195 ms |
| Jul 4, 2026 | 197 ms |
| Jul 11, 2026 | 202 ms |
| Jul 18, 2026 | 202 ms |
| Jul 25, 2026 | 199 ms |
| Aug 1, 2026 | 198 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 199 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 209 ms |
| Sep 19, 2026 | 205 ms |
| Sep 26, 2026 | 211 ms |
| Oct 3, 2026 | 216 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 219 ms |
| Oct 24, 2026 | 225 ms |
| Oct 31, 2026 | 229 ms |
| Nov 7, 2026 | 238 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
How it loaded on a phone
1.2 s
2.5 s
3.7 s
4.9 s
6.2 s
7.4 s
8.6 s
9.8 s
Speed
Use efficient cache lifetimes
3.6 s · 634 KiB18 files are served with short cache lifetimes, so returning visitors download them again (634 KiB).
Reduce unused JavaScript
3.5 s · 765 KiBAbout 765 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (posthog.com, Shopify and PayPal and others), adding 1.4 MB and 1.6 s of main-thread time.
posthog.com adds 907 ms
907 msposthog.com costs a phone 907 ms of main-thread work and 266 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused CSS
750 ms · 101 KiBAbout 101 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 578 ms. During a long task the page ignores taps.
Duplicated JavaScript
350 ms · 19 KiB19 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.
Shopify adds 253 ms
253 msShopify costs a phone 253 ms of main-thread work and 373 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
2,316 HTML elements
The page has 2,316 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
200 ms · 50 KiB1 image could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Render-blocking requests
250 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
Legacy JavaScript
150 ms · 39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 19.7 s
19.7 sThe page becomes fully interactive after 19.7 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 970 ms
970 msScripts block taps and scrolling for 970 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 239 ms
239 msReal visitors wait 239 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 194 ms to 238 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
6 checks passed
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 CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 487 ms
487 msReal visitors wait 487 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 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: 4.8 MB in 463 requests
4.8 MBYour homepage downloads 4.8 MB in 463 requests on a phone: scripts 1.9 MB (136), other files 1.3 MB (255) and images 1.0 MB (44). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
66 KiB3 images are downloaded at several times the size a phone draws them, for example KT_Deutsch-2.webp at 390 px wide, shown at 107 px. Resized copies would save about 66 KiB.
4 images in older formats
4 images (306 KiB) 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.
About 1.4 g of CO₂ per visit
1.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.35 g of CO₂e: 162.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
16 links without text
16 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
47 internal links, 7 external
The homepage links to 47 pages on medicross.com and 7 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Want to understand your body better? Take the lifestyle check with a hair sample: insights into micronutrients & your i…”.
One H1 headline
Your main headline reads: “Find out what's right for your well-being”.
Title: 43 characters
Your title is a healthy 43 characters: “Hair analysis for people & pets | Medicross”.
Canonical URL set
The canonical URL is https://www.medicross.com/en.
Structured data in place
Structured data found: FAQPage, 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://www.medicross.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (3,408 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.medicross.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://www.medicross.com/en/collections/shop/pet and https://www.medicross.com/en/collections/shop use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.medicross.com/en/products/combo-test-nutrition-counseling, https://www.medicross.com/en/products/nutrition-counseling and https://www.medicross.com/en/products/medicross-e-books have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
6 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.
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
9 third-party cookies
9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
7 small tap targets
7 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
About 1,016 words of copy
The homepage carries about 1,016 words of visible text.
6 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Shop”, “Learn more” and “Order”.
6 short forms
6 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 335 testimonial or review blocks, a star rating and “over 106,000 customers”.
Analytics in place
Analytics detected: PostHog.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 3 of them by other companies (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.
50 other companies contacted
Loading the homepage contacts 50 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 medicross.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;WooCommerce Checkout;WooCommerce Germanized
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on medicross.com, including 19 speed issues, 1 SEO issue and 1 conversion gap. 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.