Website review, no card needed

ekookna.pl logo

ekookna.pl website review

Visit site (opens in a new tab)Reviewed 28 October 202642 issues · 86 checks

This review found 42 issues worth fixing on ekookna.pl, 19 of them high impact, across 86 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
2.6 s2.2 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.3 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
114 ms98 msMay 9Oct 24106 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026100 ms
May 16, 2026101 ms
May 23, 2026101 ms
May 30, 2026102 ms
Jun 6, 2026101 ms
Jun 13, 2026102 ms
Jun 20, 2026102 ms
Jun 27, 2026103 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026104 ms
Jul 25, 2026104 ms
Aug 1, 2026103 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026105 ms
Aug 29, 2026106 ms
Sep 5, 2026106 ms
Sep 12, 2026109 ms
Sep 19, 2026111 ms
Sep 26, 2026112 ms
Oct 3, 2026112 ms
Oct 10, 2026111 ms
Oct 17, 2026112 ms
Oct 24, 2026106 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 ekookna.pl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ekookna.pl at 0.7 s0.7 s
  2. ekookna.pl at 1.4 s1.4 s
  3. ekookna.pl at 2.1 s2.1 s
  4. ekookna.pl at 2.8 s2.8 s
  5. ekookna.pl at 3.5 s3.5 s
  6. ekookna.pl at 4.2 s4.2 s
  7. ekookna.pl at 4.9 s4.9 s
  8. ekookna.pl at 5.6 s5.6 s

Speed

7 to fix34
  • Use efficient cache lifetimes

    18.0 s · 8.5 MB

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

  • Render-blocking requests

    6.8 s

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

  • Reduce unused CSS

    2.1 s · 399 KiB

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

  • Reduce unused JavaScript

    2.1 s · 305 KiB

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

  • Mobile performance score: 34

    34/100

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

  • Minify JavaScript

    770 ms · 119 KiB

    119 KiB could be saved by minifying JavaScript.

  • Minify CSS

    600 ms · 107 KiB

    107 KiB could be saved by minifying CSS.

  • 4 third-party services on the page

    4 third-party services load with your homepage (consentmanager.net, Google Tag Manager and Google Fonts and others), adding 383 KiB and 278 ms of main-thread time.

  • Improve image delivery

    174 KiB

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

  • 2 long tasks on the main thread

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

  • Document request latency

    41 KiB

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

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 260 ms

    260 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 36.2 s

    36.2 s

    Your largest element takes 36.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Black Weeks w Eko-Oknach: Nawet do -5% na nowe zamówienia S…”.

  • Time to Interactive: 37.3 s

    37.3 s

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

  • First Contentful Paint: 7.3 s

    7.3 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Cumulative Layout Shift: 0.578

    0.578

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

  • 41 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

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

    0.01

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 633 ms

    633 ms

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

  • Total Blocking Time: 24 ms

    24 ms

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

Images and page weight

4 to fix33
  • Page weight: 8.9 MB in 113 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 113 requests on a phone: images 7.6 MB (71), scripts 673 KiB (15) and stylesheets 460 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • 17 images far larger than shown

    1.4 MB

    17 images are downloaded at several times the size a phone draws them, for example gealan-kolory-aktualnosc.jpg at 1,200 px wide, shown at 330 px. Resized copies would save about 1.4 MB.

  • 24 images in older formats

    24 images (4.9 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.

  • 26 images below the first screen load straight away

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

  • About 2.5 g of CO₂ per visit

    2.51 g

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

Accessibility

10 to fixGoogle 8385
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 60 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

6 to fixGoogle 10070
  • No H1 headline

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

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (223 characters)

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://ekookna.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.

  • 148 internal links, 41 external

    The homepage links to 148 pages on ekookna.pl and 41 external pages.

2 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “Windows, doors, roller shutters, gates – Eko-Okna S.A.”.

  • robots.txt in place

    robots.txt is in place.

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://ekookna.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 (845 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix71
  • 1 page points its canonical at the homepage

    https://ekookna.pl/wirtualny_spacer/index.php declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://ekookna.pl/ekoen/page-menu/for-business and https://ekookna.pl/ekoen/page-menu/e-mail-quoteukekooknacom all use the title “Windows, doors, roller shutters, gates – Eko-Okna S.A.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://ekookna.pl/ekoen/about-company, https://ekookna.pl/ekoen/about-company/mission-and-vision, https://ekookna.pl/ekoen/about-company/our-strengths, https://ekookna.pl/ekoen/about-company/the-companys-history, https://ekookna.pl/ekoen/about-company/awards and https://ekookna.pl/ekoen/about-company/warranty and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://ekookna.pl/ekoen/page-menu/for-business and https://ekookna.pl/ekoen/page-menu/e-mail-quoteukekooknacom use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://ekookna.pl/ekoen/page-menu/for-business and https://ekookna.pl/ekoen/page-menu/e-mail-quoteukekooknacom have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://ekookna.pl/ekoen/page-menu/for-business and https://ekookna.pl/ekoen/page-menu/e-mail-quoteukekooknacom took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Only about 181 words

    The homepage has only about 181 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Download”, “Contact” and “Where to buy”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

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

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: consentmanager

    A consent management tool (consentmanager) loads with the page.

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 ekookna.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
OVHcloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on ekookna.pl, including 13 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