Website review, no card needed

adamex.pl logo

adamex.pl website review

Visit site (opens in a new tab)Reviewed 17 November 202635 issues · 83 checks

This review found 35 issues worth fixing on adamex.pl, 9 of them high impact, across 83 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s953 msMay 30Nov 141.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.6 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.5 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Nov 14, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
108 ms95 msMay 30Nov 14103 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202697 ms
Jun 6, 202697 ms
Jun 13, 202697 ms
Jun 20, 202696 ms
Jun 27, 202697 ms
Jul 4, 202697 ms
Jul 11, 202697 ms
Jul 18, 202698 ms
Jul 25, 202698 ms
Aug 1, 2026100 ms
Aug 8, 2026102 ms
Aug 15, 2026102 ms
Aug 22, 2026102 ms
Aug 29, 2026102 ms
Sep 5, 2026103 ms
Sep 12, 2026104 ms
Sep 19, 2026105 ms
Sep 26, 2026106 ms
Oct 3, 2026104 ms
Oct 10, 2026103 ms
Oct 17, 2026104 ms
Oct 24, 2026103 ms
Oct 31, 2026104 ms
Nov 7, 2026104 ms
Nov 14, 2026103 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

Full-page screenshot of adamex.pl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adamex.pl at 0.4 s0.4 s
  2. adamex.pl at 0.8 s0.8 s
  3. adamex.pl at 1.1 s1.1 s
  4. adamex.pl at 1.5 s1.5 s
  5. adamex.pl at 1.9 s1.9 s
  6. adamex.pl at 2.3 s2.3 s
  7. adamex.pl at 2.6 s2.6 s
  8. adamex.pl at 3.0 s3.0 s

Speed

6 to fix69
  • Improve image delivery

    5.3 s · 2.4 MB

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

  • Render-blocking requests

    1.1 s

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

  • Reduce unused JavaScript

    890 ms · 174 KiB

    About 174 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 890 ms faster on a phone.

  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 231 ms

    231 ms

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

  • 1,510 HTML elements

    The page has 1,510 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, selly.pl and Google Fonts and others), adding 405 KiB and 238 ms of main-thread time.

  • Legacy JavaScript

    250 ms · 10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    9 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (9 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.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 348 ms of it running JavaScript. That is comfortably low.

  • Server response: 139 ms

    139 ms

    Your server sent the HTML in 139 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 13.0 s

    13.0 s

    Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “black friday 2026”.

  • Time to Interactive: 13.2 s

    13.2 s

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

  • Speed Index: 5.7 s

    5.7 s

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

  • 42 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 97 ms to 103 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.3 s

    1.3 s

    Real visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 103 ms

    103 ms

    Real visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 604 ms

    604 ms

    Real visitors wait 604 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 31% faster for real visitors

    -31%

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

  • Total Blocking Time: 103 ms

    103 ms

    Scripts block the page for only 103 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.034

    0.034

    The layout barely moves while loading (CLS 0.034, good is under 0.1).

Images and page weight

5 to fix40
  • 2 images over 500 KB

    2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    1.4 MB

    12 images are downloaded at several times the size a phone draws them, for example black_friday_2026_mobile.jpg at 1,333 px wide, shown at 390 px. Resized copies would save about 1.4 MB.

  • Page weight: 3.4 MB in 61 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 61 requests on a phone: images 2.8 MB (37), scripts 472 KiB (13) and fonts 57 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 12 images in older formats

    12 images (2.5 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

    bf_baner_mobile.jpg 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).

  • 2 images below the first screen load straight away

    2 images further down the page (142 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.95 g

    By 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.

Accessibility

6 to fixGoogle 9493
  • 9 text elements with low contrast

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

  • All page content should be contained by landmarks (15 elements)

    All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 5 form fields without a label

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

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 51 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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

5 to fixGoogle 10077
  • Title is short (17 characters)

    Your title is only 17 characters: “Sklep internetowy”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (12 characters)

    Your meta description is only 12 characters: “Sklep online”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://sklep.adamex.pl/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 223 internal links, 9 external

    The homepage links to 223 pages on adamex.pl and 9 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Adamex – wózki, foteliki i akcesoria dziecięce oraz rowerki i hulajnogi”.

  • Canonical URL set

    The canonical URL is https://sklep.adamex.pl/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://sklep.adamex.pl/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.

2 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,736 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://sklep.adamex.pl/koszyk.html 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://sklep.adamex.pl/ulubione.html, https://sklep.adamex.pl/szukaj.html, https://sklep.adamex.pl/wozki-2w1,c2.html, https://sklep.adamex.pl/wozki-spacerowe,c22.html, https://sklep.adamex.pl/foteliki,c3.html and https://sklep.adamex.pl/0-36-miesiecy,c23.html and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://sklep.adamex.pl/szukaj.html has 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 80 found) and read each the way a search engine does.

4 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 26 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 calls to action

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

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,606 words of copy

    The homepage carries about 1,606 words of visible text.

3 checks passed
  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 adamex.pl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cyber_Folks S.A.

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 adamex.pl, including 10 speed issues, 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25