Website review, no card needed
lymphoria.co website review
Visit site (opens in a new tab)Reviewed 11 October 202626 issues · 80 checks
This review found 26 issues worth fixing on lymphoria.co, 5 of them high impact, across 80 checks. The most urgent: page weight: 5.6 MB in 60 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
92A- #896 of 119,740 reviewed websitesbeats 99%
- #349 of 67,889 online storesbeats 99%
- #330 of 61,876 Shopify storesbeats 99%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.3 s |
| Apr 25, 2026 | 1.4 s |
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 162 ms |
| Apr 25, 2026 | 162 ms |
| May 2, 2026 | 154 ms |
| May 9, 2026 | 154 ms |
| May 16, 2026 | 161 ms |
| May 23, 2026 | 169 ms |
| May 30, 2026 | 179 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 198 ms |
| Jun 20, 2026 | 203 ms |
| Jun 27, 2026 | 205 ms |
| Jul 4, 2026 | 203 ms |
| Jul 11, 2026 | 193 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 164 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 177 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 185 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 186 ms |
| Oct 3, 2026 | 181 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
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Improve image delivery
286 KiB10 images could be 286 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 156 ms
156 msGoogle Tag Manager costs a phone 156 ms of main-thread work and 308 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Shopify and others), adding 522 KiB and 156 ms of main-thread time.
Reduce unused JavaScript
138 KiBAbout 138 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 116 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
13 KiB6 files are served with short cache lifetimes, so returning visitors download them again (13 KiB).
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.
3 checks passed
Mobile performance score: 96
96/100Your mobile performance score is 96 (desktop: 99). That is in Google's “good” band (90 and up).
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 163 ms of it running JavaScript. That is comfortably low.
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
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.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 162 ms to 181 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 135 ms
135 msReal visitors wait 135 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 658 ms
658 msReal visitors wait 658 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.
Speed Index: 2.3 s
2.3 sVisually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Total Blocking Time: 33 ms
33 msScripts block the page for only 33 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.6 MB in 60 requests
5.6 MBYour homepage downloads 5.6 MB in 60 requests on a phone: media 3.9 MB (2), images 803 KiB (16) and scripts 598 KiB (27). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (336 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.
1 image below the first screen load straight away
1 image further down the page (61 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 191.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (73 characters)
Your title is 73 characters, so Google will cut it off around 60: “Lymphatic Cleanse & Detox | Lymph Drainage Supplement Support – Lymphoria”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
21 internal links, 0 external
The homepage links to 21 pages on lymphoria.co and 0 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Feel lighter with lymph detox and lymphatic support. Use lymphatic drainage supplements to help drain the lymphatic sys…”.
One H1 headline
Your main headline reads: “Lymphoria® Lymphatic Drainage Drops”.
Canonical URL set
The canonical URL is https://lymphoria.co/.
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://lymphoria.co/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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 (1,658 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://lymphoria.co/llms.txt (4 KiB, 5 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://lymphoria.co/a/loop_subscriptions/get-subscription-link, which answers with an error. Visitors hit a dead end and search engines drop it.
8 pages without a meta description
https://lymphoria.co/blogs/lymphoria-blogs, https://lymphoria.co/blogs/lymphoria-blogs/how-to-support-lymphatic-drainage-naturally-7-daily-habits-1, https://lymphoria.co/blogs/lymphoria-blogs/lymphoria-lymphatic-drainage-drops-what-they-are-and-how-they-work, https://lymphoria.co/policies/refund-policy, https://lymphoria.co/policies/shipping-policy and https://lymphoria.co/policies/privacy-policy and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://lymphoria.co/apps/parcelpanel, https://lymphoria.co/pages/contact, https://lymphoria.co/blogs/lymphoria-blogs, https://lymphoria.co/blogs/lymphoria-blogs/how-to-support-lymphatic-drainage-naturally-7-daily-habits-1 and https://lymphoria.co/blogs/lymphoria-blogs/lymphoria-lymphatic-drainage-drops-what-they-are-and-how-they-work have no <h1> headline, so visitors and search engines get no clear main topic.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
4 checks passed
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 14 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_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,143 words of copy
The homepage carries about 1,143 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Track Order” and “Contact”.
11 calls to action
The homepage has 11 calls to action, for example “Track Order”, “Contact” and “Try Lymphoria Risk-Free”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 204 testimonial or review blocks and “14,753+ reviews”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
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 Klaviyo (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
11 other companies contacted
Loading the homepage contacts 11 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 lymphoria.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on lymphoria.co, including 7 speed issues, 2 SEO issues and 3 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.