adamed.com website review

13 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.0 s faster on a phone.

About 910 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.

About 156 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).

Your mobile performance score is 24 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

7 third-party services load with your homepage (YouTube, Google Tag Manager and Optanon and others), adding 1.8 MB and 827 ms of main-thread time.

YouTube costs a phone 428 ms of main-thread work and 1.2 MB 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.

3 files are served with short cache lifetimes, so returning visitors download them again (54 KiB).

Google Tag Manager costs a phone 331 ms of main-thread work and 455 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.

A phone's processor spends 2.9 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

11 long tasks block the main thread while loading, the longest for 163 ms. During a long task the page ignores taps.

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 33.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

The page becomes fully interactive after 33.9 s. Good is under 3.8 s.

The layout shifts by 1.008 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Visually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 4.0 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 382 ms in total while the page loads. Good is under 200 ms.

13 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 101 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.4 MB in 98 requests on a phone: images 3.7 MB (48), scripts 1.7 MB (20) and fonts 581 KiB (5). Under 2 MB keeps phones on slow connections fast.

10 images (1.3 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.

8 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

6 images are downloaded at several times the size a phone draws them, for example 1507957 at 870 px wide, shown at 99 px. Resized copies would save about 484 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.82 g of CO₂e: 218.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

24 images have no alt text, which hurts accessibility and image search.

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

3 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. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.adamed.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 121 pages on adamed.com and 16 external pages.

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.

There is no /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.

/produkty, /leki-na-recepte, /leki-bez-recepty, /suplementy-diety, /dermokosmetyki and /wyroby-medyczne all use the title “Produkty | Adamed”. Search engines can't tell which page to show for a search, so each competes with the others.

/aktualnosci has no meta description, so Google writes the search snippet from whatever text it finds.

/firma-adamed/rada-nadzorcza-adamed-pharma-s-a, /firma-adamed/misja-i-wartosci, /adamed-dla-rodziny and /etyka-i-compliance use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example /leki-na-recepte, whose canonical is /produkty. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/adamed-dla-rodziny, /aktualnosci, /produkty, /leki-na-recepte, /leki-bez-recepty and /suplementy-diety and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.

8 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://www.google.com/rmkt/collect/647020454/?random=1792531531883&cv=11&fst=1792531531883&fmt=8&bg=fff…”.

A form field blocks pasting, which frustrates password managers and people on phones.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

HSTS is set, but max-age is 7 days; one year is the recommended minimum.

5 links go through two or more redirects, for example https://www.adamed.com/en/.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

adamed.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

adamed.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 511 words of visible text.

DMARC is set to p=none, so mail pretending to be adamed.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 5 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.