Website review, no card needed

tuplex.pl logo

tuplex.pl website review

Visit site (opens in a new tab)Reviewed 22 October 202644 issues · 86 checks

This review found 44 issues worth fixing on tuplex.pl, 24 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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 s1.3 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
105 ms98 msMay 2Oct 17101 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026102 ms
May 9, 2026102 ms
May 16, 2026101 ms
May 23, 2026100 ms
May 30, 2026101 ms
Jun 6, 2026100 ms
Jun 13, 2026100 ms
Jun 20, 2026102 ms
Jun 27, 2026101 ms
Jul 4, 2026102 ms
Jul 11, 2026103 ms
Jul 18, 2026103 ms
Jul 25, 2026103 ms
Aug 1, 2026102 ms
Aug 8, 2026101 ms
Aug 15, 202699 ms
Aug 22, 2026101 ms
Aug 29, 2026102 ms
Sep 5, 2026101 ms
Sep 12, 2026102 ms
Sep 19, 2026102 ms
Sep 26, 2026104 ms
Oct 3, 2026104 ms
Oct 10, 2026103 ms
Oct 17, 2026101 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 tuplex.pl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tuplex.pl at 1.1 s1.1 s
  2. tuplex.pl at 2.1 s2.1 s
  3. tuplex.pl at 3.2 s3.2 s
  4. tuplex.pl at 4.3 s4.3 s
  5. tuplex.pl at 5.3 s5.3 s
  6. tuplex.pl at 6.4 s6.4 s
  7. tuplex.pl at 7.5 s7.5 s
  8. tuplex.pl at 8.5 s8.5 s

Speed

15 to fix42
  • Render-blocking requests

    4.7 s

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

  • Reduce unused CSS

    3.6 s · 745 KiB

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

  • Minify CSS

    2.7 s · 561 KiB

    561 KiB could be saved by minifying CSS.

  • Reduce initial server response time

    2.5 s

    Reduce initial server response time. Google estimates savings of 2.5 s on a phone.

  • Document request latency

    2.5 s

    The HTML itself could arrive about 2.5 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Improve image delivery

    1.4 s · 540 KiB

    9 images could be 540 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 5.0 s

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

  • 3,865 HTML elements

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

  • Server response: 2.6 s

    2.6 s

    Your server takes 2.6 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Klaviyo and cloudfront.net and others), adding 654 KiB and 936 ms of main-thread time.

  • Google Tag Manager adds 745 ms

    745 ms

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

  • 14 long tasks on the main thread

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

  • Minify JavaScript

    40 ms · 291 KiB

    291 KiB could be saved by minifying JavaScript.

  • Reduce unused JavaScript

    279 KiB

    About 279 KiB of JavaScript is downloaded but never used on this page.

  • Legacy JavaScript

    18 KiB

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

  • Use efficient cache lifetimes

    12 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 71 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Core Web Vitals

9 to fix100
  • 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.

  • Largest Contentful Paint: 7.8 s

    7.8 s

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

  • Time to Interactive: 17.5 s

    17.5 s

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

  • Speed Index: 10.6 s

    10.6 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Total Blocking Time: 616 ms

    616 ms

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

  • Largest content (LCP) got 22% slower for real visitors

    +22%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 965 ms

    965 ms

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

  • Tap response (INP) held steady for real visitors

    0%

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

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 129 ms

    129 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.3 MB in 253 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 253 requests on a phone: scripts 1.3 MB (209), images 1.1 MB (15) and stylesheets 760 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Reklama2026-Kafel.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).

  • About 0.9 g of CO₂ per visit

    0.93 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9393
  • 3 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • <svg> elements with an img or image role must have alternative text (1 element)

    <svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 46 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7771
  • No H1 headline

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

  • Title is long (141 characters)

    Your title is 141 characters, so Google will cut it off around 60: “Lider w branży tworzyw sztucznych! Plexi, poliwęglan, PCW, HPL, folie i tkaniny do zadruk…”.

  • Meta description is long (176 characters)

    Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

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

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 343 internal links, 3 external

    The homepage links to 343 pages on tuplex.pl and 3 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://tuplex.pl/.

  • Structured data in place

    Structured data found: 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.

AI search readiness

100
  • No llms.txt

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

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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,247 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://tuplex.pl/sklep-internetowy/tworzywa and https://tuplex.pl/sklep-internetowy/tworzywa/kompozyt-reklamowy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://tuplex.pl/szkolenie-bostik-2026 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 198 found) and read each the way a search engine does.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://tuplex.pl/elasticsuite/tracker/hit/image/h.png?page[store_id]=1&page[cms][identifier]=home&page[cms][title]=Home%20page&page[type][identifier]=cms_index_index&page[type][label]=Strona%20g%C5%8.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    74 of 74 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 507 words of copy

    The homepage carries about 507 words of visible text.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 21 cookies set on arrival

    21

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

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Magento
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on tuplex.pl, including 24 speed issues, 6 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