Website review, no card needed

cellfast.com.pl logo

cellfast.com.pl website review

Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 84 checks

This review found 36 issues worth fixing on cellfast.com.pl, 12 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
3.2 s1.1 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.6 s
Aug 1, 20261.7 s
Aug 8, 20261.4 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.4 s
Nov 7, 20261.5 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
104 ms91 msMay 30Nov 1493 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202699 ms
Jun 6, 202698 ms
Jun 13, 2026100 ms
Jun 20, 202699 ms
Jun 27, 2026102 ms
Jul 4, 2026101 ms
Jul 11, 202699 ms
Jul 18, 202699 ms
Jul 25, 202698 ms
Aug 1, 202697 ms
Aug 8, 202697 ms
Aug 15, 202696 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202693 ms
Sep 12, 202693 ms
Sep 19, 202694 ms
Sep 26, 202696 ms
Oct 3, 202696 ms
Oct 10, 202696 ms
Oct 17, 202695 ms
Oct 24, 202694 ms
Oct 31, 202693 ms
Nov 7, 202692 ms
Nov 14, 202693 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 cellfast.com.pl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cellfast.com.pl at 0.7 s0.7 s
  2. cellfast.com.pl at 1.4 s1.4 s
  3. cellfast.com.pl at 2.2 s2.2 s
  4. cellfast.com.pl at 2.9 s2.9 s
  5. cellfast.com.pl at 3.6 s3.6 s
  6. cellfast.com.pl at 4.3 s4.3 s
  7. cellfast.com.pl at 5.1 s5.1 s
  8. cellfast.com.pl at 5.8 s5.8 s

Speed

12 to fix61
  • Use efficient cache lifetimes

    1.8 s · 32.1 MB

    79 files are served with short cache lifetimes, so returning visitors download them again (32.1 MB).

  • Reduce unused JavaScript

    4.2 s · 608 KiB

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

  • Render-blocking requests

    2.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and cellfastgroup.com and others), adding 34.2 MB and 681 ms of main-thread time.

  • cellfastgroup.com adds 141 ms

    141 ms

    cellfastgroup.com costs a phone 141 ms of main-thread work and 33.0 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.

  • Mobile performance score: 61

    61/100

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

  • Reduce unused CSS

    600 ms · 116 KiB

    About 116 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.

  • Font display

    700 ms

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

  • Google CDN adds 274 ms

    274 ms

    Google CDN costs a phone 274 ms of main-thread work and 742 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.

  • Improve image delivery

    287 KiB

    6 images could be 287 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 219 ms

    219 ms

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

  • Main-thread work: 2.1 s

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

  • 6 long tasks on the main thread

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

  • Duplicated JavaScript

    23 KiB

    23 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 13.5 s

    13.5 s

    Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Używamy niezbędnych plików cookie, aby zapewnić prawidłowe …”. Most of its time is element render delay (5.8 s).

  • Speed Index: 10.2 s

    10.2 s

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

  • Time to Interactive: 13.8 s

    13.8 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

9 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: 2.3 s

    2.3 s

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

  • Real-user INP: 106 ms

    106 ms

    Real visitors wait 106 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.

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 623 ms

    623 ms

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

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

    -47%

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

  • Total Blocking Time: 123 ms

    123 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix63
  • Page weight: 34.6 MB in 119 requests

    34.6 MB

    Your homepage downloads 34.6 MB in 119 requests on a phone: media 31.7 MB (1), scripts 1.3 MB (27) and images 933 KiB (68). Under 2 MB keeps phones on slow connections fast.

  • 8 images below the first screen load straight away

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

  • About 9.8 g of CO₂ per visit

    9.82 g

    By the Sustainable Web Design model, a visit to your homepage emits about 9.82 g of CO₂e: 1177.8 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

8 to fixGoogle 8889
  • Invalid ARIA attributes

    5 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 16 text elements with low contrast

    16 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 (35 elements)

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

  • 4 form fields without a label

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

  • 3 links without text

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

  • Alternative text of images should not be repeated as text (10 elements)

    Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 6 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8593
  • Invalid hreflang

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

  • One H1 headline

    Your <h1> is empty.

  • 185 internal links, 24 external

    The homepage links to 185 pages on cellfast.com.pl and 24 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Cellfast to polski lider w produkcji węży ogrodowych, systemów nawadniania, narzędzi ogrodowych i rynien. Innowacyjne r…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Cellfast | systemy nawadniania, narzędzia i akcesoria ogrodowe”.

  • Canonical URL set

    The canonical URL is https://cellfast.com.pl/akcesoria-ogrodowe-2/.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://cellfast.com.pl/wp-sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://cellfast.com.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: 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,227 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    / and https://cellfast.com.pl/cz all use the title “Cellfast | systemy nawadniania, narzędzia i akcesoria ogrodowe”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://cellfast.com.pl/en, https://cellfast.com.pl/fr, https://cellfast.com.pl/sk, https://cellfast.com.pl/it and https://cellfast.com.pl/ru have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages slow to respond

    https://cellfast.com.pl/fr, https://cellfast.com.pl/sk, https://cellfast.com.pl/it, https://cellfast.com.pl/ru and https://cellfast.com.pl/cz took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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

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

  • 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: 2 trust badges. 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 515 words of copy

    The homepage carries about 515 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.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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 cellfast.com.pl, 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
E-commerce
WooCommerce
Analytics
Google Tag Manager
Hosting
LH.pl Sp. z o.o.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on cellfast.com.pl, including 17 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

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