Website review, no card needed
animus-medicus.com website review
Visit site (opens in a new tab)Reviewed 11 November 202632 issues · 82 checks
This review found 32 issues worth fixing on animus-medicus.com, 15 of them high impact, across 82 checks. The most urgent: page weight: 6.9 MB in 360 requests. 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
86B- #10,818 of 109,103 reviewed websitesbeats 86%
- #6,650 of 61,799 online storesbeats 85%
- #6,456 of 56,377 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 116 ms |
| Jul 18, 2026 | 118 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 108 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 108 ms |
| Oct 31, 2026 | 113 ms |
| Nov 7, 2026 | 117 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
0.9 s
1.9 s
2.8 s
3.7 s
4.7 s
5.6 s
6.5 s
7.5 s
Speed
6,203 HTML elements
The page has 6,203 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
3.4 MB68 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (loox.io, Clarity and TikTok and others), adding 738 KiB and 718 ms of main-thread time.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 266 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 37 KiBAbout 37 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.
Reduce unused JavaScript
86 KiBAbout 86 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
77 KiB8 files are served with short cache lifetimes, so returning visitors download them again (77 KiB).
Legacy JavaScript
44 KiBPolyfills for old browsers add 44 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
14 KiB14 KiB JavaScript is shipped twice across bundles.
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: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 9.6 s
9.6 sThe page becomes fully interactive after 9.6 s. Good is under 3.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 624 ms
624 msScripts block taps and scrolling for 624 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 112 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 116 ms
116 msReal visitors wait 116 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 459 ms
459 msReal visitors wait 459 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-11-07, 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).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.9 MB in 360 requests
6.9 MBYour homepage downloads 6.9 MB in 360 requests on a phone: images 4.5 MB (78), other files 1.3 MB (183) and scripts 689 KiB (81). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
884 KiB7 images are downloaded at several times the size a phone draws them, for example 5er-paket-chalk-edition-bestseller-animus-medicus-gmbh-1.web at 780 px wide, shown at 167 px. Resized copies would save about 884 KiB.
21 images in older formats
21 images (4.8 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.
An image on the first screen is lazy-loaded
Praxis_Header_1x1_9c9b90af-c733-41e7-b677-2b8792acb9aa.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 2.0 g of CO₂ per visit
1.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.96 g of CO₂e: 235.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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 (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
99 internal links, 2 external
The homepage links to 99 pages on animus-medicus.com and 2 external pages.
6 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “animus-medicus.com – Animus Medicus US”.
Canonical URL set
The canonical URL is https://animus-medicus.com/.
Structured data in place
Structured data found: OnlineStore, 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://animus-medicus.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (340 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://animus-medicus.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://animus-medicus.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://animus-medicus.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
6 pages without a meta description
https://animus-medicus.com/collections/single-posters, https://animus-medicus.com/customer_authentication/redirect, https://animus-medicus.com/collections/save-50-on-all-posters, https://animus-medicus.com/pages/reviews, https://animus-medicus.com/collections/bundles and https://animus-medicus.com/collections/bundles-for-practice have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://animus-medicus.com/customer_authentication/redirect and https://animus-medicus.com/pages/reviews have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://animus-medicus.com/customer_authentication/redirect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.
3 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “this.loadingEl.remove is not a function”.
2 checks passed
Tap targets are thumb-sized
62 of 74 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 357 words of copy
The homepage carries about 357 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Black Friday”.
1 call to action
The homepage has 1 call to action, for example “Shop Black Friday”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 28 testimonial or review blocks and “Over 100,000+ happy customers”.
Analytics in place
Analytics detected: Microsoft Clarity and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
33 other companies contacted
Loading the homepage contacts 33 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 animus-medicus.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Triplewhale · gelato.tech · loox.io · cloudfront.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on animus-medicus.com, including 11 speed issues and 2 SEO issues. 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.