Website review, no card needed
bnipolska.pl website review
Visit site (opens in a new tab)Reviewed 30 October 202617 issues · 77 checks
This review found 17 issues worth fixing on bnipolska.pl, 3 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
93AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.9 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 136 ms |
| May 16, 2026 | 132 ms |
| May 23, 2026 | 134 ms |
| May 30, 2026 | 124 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 127 ms |
| Aug 22, 2026 | 121 ms |
| Oct 10, 2026 | 170 ms |
| Oct 17, 2026 | 170 ms |
| Oct 24, 2026 | 173 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
Speed
Use efficient cache lifetimes
500 ms · 2.2 MB7 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Render-blocking requests
750 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
1,627 HTML elements
The page has 1,627 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
128 KiBAbout 128 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
94 KiB2 images could be 94 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 68 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Cloudflare and cloudflareinsights.com), adding 11 KiB and 27 ms of main-thread time.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
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.
3 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92. That is in Google's “good” band (90 and up).
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 625 ms of it running JavaScript. That is comfortably low.
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 136 ms to 173 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 60% slower for real visitors
+60%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.3 s
3.3 sYour largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ujęcia ze spotkań i wydarzeń BNI Polska: rozmowy przedsiębi…”.
9 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 179 ms
179 msReal visitors wait 179 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 3.3 s
3.3 sThe page is fully interactive after 3.3 s.
Speed Index: 2.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Total Blocking Time: 18 ms
18 msScripts block the page for only 18 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.3 MB in 78 requests
3.3 MBYour homepage downloads 3.3 MB in 78 requests on a phone: media 2.0 MB (1), scripts 451 KiB (27) and images 327 KiB (8). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
image 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.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 111.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
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.
18 links without text
18 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.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
126 internal links, 16 external
The homepage links to 126 pages on bnipolska.pl and 16 external pages.
8 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Czym jest BNI? Największa na świecie organizacja rekomendacji biznesowych — 355 000 Członków w 78 krajach, w Polsce bli…”.
One H1 headline
Your main headline reads: “BNI to największa na świecie organizacja rekomendacji biznesowych.”.
Title: 49 characters
Your title is a healthy 49 characters: “BNI Polska — organizacja rekomendacji biznesowych”.
Canonical URL set
The canonical URL is https://bnipolska.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://bnipolska.pl/sitemap.xml.
AI search readiness
No llms.txt
There is no https://bnipolska.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,328 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page slow to respond
https://bnipolska.pl/zostan-czlonkiem took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 33 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was 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
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 697 words of copy
The homepage carries about 697 words of visible text.
3 checks passed
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 bnipolska.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
- Next.js
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 17 issues on bnipolska.pl, including 8 speed issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.