Website review, no card needed
jtbanka.sk website review
Visit site (opens in a new tab)Reviewed 22 October 202640 issues · 85 checks
This review found 40 issues worth fixing on jtbanka.sk, 20 of them high impact, across 85 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 163 ms |
| May 9, 2026 | 165 ms |
| May 16, 2026 | 166 ms |
| May 23, 2026 | 167 ms |
| May 30, 2026 | 167 ms |
| Jun 6, 2026 | 167 ms |
| Jun 13, 2026 | 165 ms |
| Jun 20, 2026 | 161 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 169 ms |
| Jul 18, 2026 | 173 ms |
| Jul 25, 2026 | 175 ms |
| Aug 1, 2026 | 176 ms |
| Aug 8, 2026 | 176 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 177 ms |
| Aug 29, 2026 | 177 ms |
| Sep 5, 2026 | 177 ms |
| Sep 12, 2026 | 175 ms |
| Sep 19, 2026 | 175 ms |
| Sep 26, 2026 | 174 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 174 ms |
| Oct 17, 2026 | 172 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
How it loaded on a phone
1.7 s
3.3 s
5.0 s
6.7 s
8.3 s
10.0 s
11.7 s
13.3 s
Speed
Use efficient cache lifetimes
2.2 s · 6.8 MB35 files are served with short cache lifetimes, so returning visitors download them again (6.8 MB).
Render-blocking requests
9.2 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.2 s.
Reduce unused CSS
5.0 s · 1.4 MBAbout 1.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Reduce unused JavaScript
3.6 s · 940 KiBAbout 940 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Font display
1.4 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).
Mobile performance score: 26
26/100Your mobile performance score is 26 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
4.7 MB6 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 393 ms
393 msGoogle Tag Manager costs a phone 393 ms of main-thread work and 506 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 347 ms. During a long task the page ignores taps.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Analytics), adding 508 KiB and 393 ms of main-thread time.
Minify JavaScript
106 KiB106 KiB could be saved by minifying JavaScript.
Document request latency
46 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Phones get a much slower page than desktops
Desktop scores 54 but mobile only 26. 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.
1 checks passed
Server response: 224 ms
224 msYour server sent the HTML in 224 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.
First Contentful Paint: 10.7 s
10.7 sThe first text or image appears after 10.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 14.7 s
14.7 sYour largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Radi by sme Vám poskytli čo najlepšie skúsenosti s našou we…”.
Speed Index: 20.7 s
20.7 sVisually, the page fills in at 20.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 25.1 s
25.1 sThe page becomes fully interactive after 25.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.267
0.267The layout shifts by 0.267 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 606 ms
606 msScripts block taps and scrolling for 606 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 163 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 181 ms
181 msReal visitors wait 181 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 TTFB: 665 ms
665 msReal visitors wait 665 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 10.4 MB in 53 requests
10.4 MBYour homepage downloads 10.4 MB in 53 requests on a phone: images 6.1 MB (14), scripts 1.9 MB (19) and stylesheets 1.5 MB (3). Under 2 MB keeps phones on slow connections fast.
About 3.0 g of CO₂ per visit
2.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.96 g of CO₂e: 354.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail 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.
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate 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 1 image in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
113 internal links, 6 external
The homepage links to 113 pages on jtbanka.sk and 6 external pages.
6 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “J&T BANKA — Pomáhame zhodnotiť Váš majetok, uspokojíme potreby najnáročnejších klientov. Investičné a termínované vklad…”.
Title: 32 characters
Your title is a healthy 32 characters: “Expert na investície | J&T BANKA”.
Canonical URL set
The canonical URL is https://www.jtbanka.sk/.
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://www.jtbanka.sk/sitemap.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://www.jtbanka.sk/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 (811 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.jtbanka.sk/domov 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.
2 pages share a title
/ and https://www.jtbanka.sk/domov all use the title “Expert na investície | J&T BANKA”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.jtbanka.sk/en, https://www.jtbanka.sk/investicie, https://www.jtbanka.sk/vklady and https://www.jtbanka.sk/ucty have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.jtbanka.sk/en, https://www.jtbanka.sk/domov, https://www.jtbanka.sk/investicie, https://www.jtbanka.sk/vklady and https://www.jtbanka.sk/ucty 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 59 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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
73 of 73 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 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 1,078 words of copy
The homepage carries about 1,078 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: 4 phone links and 0 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
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.
4 other companies contacted
Loading the homepage contacts 4 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 jtbanka.sk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Redakčný systém WebJET - www.interway.sk
- Framework
- jQuery
- 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 40 issues on jtbanka.sk, including 21 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.