Website review, no card needed
ceo.org.pl website review
Visit site (opens in a new tab)Reviewed 19 October 202633 issues · 75 checks
This review found 33 issues worth fixing on ceo.org.pl, 15 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 122 ms |
| May 9, 2026 | 123 ms |
| May 16, 2026 | 121 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 116 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 119 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 131 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 185 ms |
| Aug 29, 2026 | 180 ms |
| Sep 5, 2026 | 176 ms |
| Sep 12, 2026 | 168 ms |
| Sep 19, 2026 | 147 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 141 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 149 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
4.8 s · 1.6 MB44 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Render-blocking requests
5.3 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.3 s.
Reduce unused JavaScript
1.9 s · 557 KiBAbout 557 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Reduce unused CSS
1.4 s · 223 KiBAbout 223 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 47
47/100Your mobile performance score is 47 (desktop: 76). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and userway.org and others), adding 881 KiB and 577 ms of main-thread time.
Google Tag Manager adds 327 ms
327 msGoogle Tag Manager costs a phone 327 ms of main-thread work and 312 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 286 ms. During a long task the page ignores taps.
Document request latency
108 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Improve image delivery
82 KiB4 images could be 82 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 76 but mobile only 47. 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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 596 ms of it running JavaScript. That is comfortably low.
Server response: 270 ms
270 msYour server sent the HTML in 270 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.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.4 s
10.4 sYour largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Programy, szkolenia i kursy dla nauczycieli Od 30 lat tworz…”.
First Contentful Paint: 7.1 s
7.1 sThe first text or image appears after 7.1 s on a phone. Good is under 1.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 10.6 s
10.6 sThe page becomes fully interactive after 10.6 s. Good is under 3.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 122 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 388 ms
388 msScripts block taps and scrolling for 388 ms in total while the page loads. Good is under 200 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user INP: 142 ms
142 msReal visitors wait 142 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.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 2.4 MB in 71 requests
2.4 MBYour homepage downloads 2.4 MB in 71 requests on a phone: scripts 1.1 MB (16), images 677 KiB (25) and stylesheets 283 KiB (13). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (554 KiB) 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.
4 images below the first screen load straight away
4 images further down the page (261 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.68 g of CO₂e: 81.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Orphan list items
Some list items are not inside a list.
All page content should be contained by landmarks (33 elements)
All page content should be contained by landmarks: 33 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
43 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: 43 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
68 internal links, 68 external
The homepage links to 68 pages on ceo.org.pl and 68 external pages.
8 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Od ponad 30 lat tworzymy programy, które inspirują do zmian w szkołach. Korzysta z nich 40 000 nauczycieli i dyrektorów…”.
One H1 headline
Your main headline reads: “Programy, szkolenia i kursy dla nauczycieli”.
Title: 39 characters
Your title is a healthy 39 characters: “Szkolenia i kursy dla nauczycieli | CEO”.
Canonical URL set
The canonical URL is https://ceo.org.pl/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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://ceo.org.pl/sitemap_index.xml.
AI search readiness
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://ceo.org.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,096 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://ceo.org.pl/wspieraj is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://ceo.org.pl/wspieraj, https://ceo.org.pl/wydarzenia and https://ceo.org.pl/kategorie/inne have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://ceo.org.pl/wspieraj and https://ceo.org.pl/kategorie/inne have 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 28 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 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
46 of 50 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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 683 words of copy
The homepage carries about 683 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
14 other companies contacted
Loading the homepage contacts 14 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 ceo.org.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
- Analytics
- Google Analytics | Google Tag Manager
Company
- Employees
- 70
- Founded
- 1994
- Headquarters
- Warsaw
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on ceo.org.pl, including 20 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.