Website review, no card needed
endymed.com website review
Visit site (opens in a new tab)Reviewed 18 October 202647 issues · 92 checks
This review found 47 issues worth fixing on endymed.com, 20 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.0 s |
| May 2, 2026 | 3.0 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 5.2 s |
| Oct 3, 2026 | 5.7 s |
| Oct 10, 2026 | 5.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 137 ms |
| May 2, 2026 | 116 ms |
| May 9, 2026 | 115 ms |
| May 16, 2026 | 119 ms |
| May 23, 2026 | 107 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 125 ms |
| Aug 1, 2026 | 157 ms |
| Aug 8, 2026 | 172 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 142 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 140 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 126 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
Reduce unused JavaScript
4.8 s · 601 KiBAbout 601 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 122 KiBAbout 122 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Render-blocking requests
650 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
5 third-party services on the page
5 third-party services load with your homepage (user-a.co.il, Google CDN and Other Google APIs/SDKs and others), adding 1.0 MB and 522 ms of main-thread time.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
Google CDN adds 229 ms
229 msGoogle CDN costs a phone 229 ms of main-thread work and 733 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,829 HTML elements
The page has 2,829 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
user-a.co.il adds 252 ms
252 msuser-a.co.il costs a phone 252 ms of main-thread work and 154 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.
Minify JavaScript
150 ms · 32 KiB32 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 18 KiB18 KiB could be saved by minifying CSS.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 145 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
32 KiB9 files are served with short cache lifetimes, so returning visitors download them again (32 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.
1 checks passed
Server response: 117 ms
117 msYour server sent the HTML in 117 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.
Real-user LCP: 5.7 s
5.7 sReal visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.8 s
4.8 sReal visitors see the first content after 4.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.2 s
4.2 sReal visitors wait 4.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 16.4 s
16.4 sYour largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The ultimate aesthetic solution for the surgical, medical a…”. Most of its time is element render delay (8.3 s).
Speed Index: 16.1 s
16.1 sVisually, the page fills in at 16.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.0 s
17.0 sThe page becomes fully interactive after 17.0 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 90% slower for real visitors
+90%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.0 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 137 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 118 ms
118 msReal visitors wait 118 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Total Blocking Time: 123 ms
123 msScripts block the page for only 123 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.05
0.05The layout barely moves while loading (CLS 0.05, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 162 requests
3.4 MBYour homepage downloads 3.4 MB in 162 requests on a phone: scripts 1.4 MB (53), images 735 KiB (10) and fonts 547 KiB (10). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (413 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.0 g of CO₂ per visit
0.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 114.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
20 tap targets too small
20 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (18 elements)
Interactive controls must not be nested: 18 elements on the page fail this check, rated serious by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (8 elements).
ARIA role should be appropriate for the element (10 elements)
ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (8 elements).
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 12 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.
Title is short (14 characters)
Your title is only 14 characters: “HOME - ENDYMED”. Between 30 and 65 characters leaves room to say what you do and for whom.
134 internal links, 6 external
The homepage links to 134 pages on endymed.com and 6 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Welcome to ENDYMED”.
Canonical URL set
The canonical URL is https://endymed.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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.
XML sitemap found
Your XML sitemap is reachable at https://endymed.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://endymed.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
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 (1,879 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://endymed.com/jawline-neck-tightening, which answers with an error. Visitors hit a dead end and search engines drop it.
1 linked page hidden from search
https://endymed.com/products/pure-laser is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
13 pages without a meta description
https://endymed.com/products, https://endymed.com/endymed-pure, https://endymed.com/fsr-applicator, https://endymed.com/newa, https://endymed.com/intensif-applicator and https://endymed.com/tc-applicators and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages slow to respond
https://endymed.com/products, https://endymed.com/products/pro-max, https://endymed.com/endymed-pure, https://endymed.com/fsr-applicator, https://endymed.com/newa and https://endymed.com/intensif-applicator and 8 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 101 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 “Cannot read properties of null (reading 'addEventListener')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 12-field form
Your longest form asks for 12 fields (5 required). Every extra field lowers completion.
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 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 613 words of copy
The homepage carries about 613 words of visible text.
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “CONTACT”, “Contact Us” and “Subscribe”.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
24 other companies contacted
Loading the homepage contacts 24 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 endymed.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on endymed.com, including 19 speed issues, 2 SEO issues and 4 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.