Website review, no card needed
primabanka.sk website review
Visit site (opens in a new tab)Reviewed 20 November 202638 issues · 82 checks
This review found 38 issues worth fixing on primabanka.sk, 14 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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 30, 2026 | 882 ms |
| Jun 6, 2026 | 880 ms |
| Jun 13, 2026 | 882 ms |
| Jun 20, 2026 | 875 ms |
| Jun 27, 2026 | 874 ms |
| Jul 4, 2026 | 878 ms |
| Jul 11, 2026 | 883 ms |
| Jul 18, 2026 | 894 ms |
| Jul 25, 2026 | 898 ms |
| Aug 1, 2026 | 908 ms |
| Aug 8, 2026 | 909 ms |
| Aug 15, 2026 | 908 ms |
| Aug 22, 2026 | 913 ms |
| Aug 29, 2026 | 910 ms |
| Sep 5, 2026 | 909 ms |
| Sep 12, 2026 | 911 ms |
| Sep 19, 2026 | 906 ms |
| Sep 26, 2026 | 895 ms |
| Oct 3, 2026 | 889 ms |
| Oct 10, 2026 | 907 ms |
| Oct 17, 2026 | 922 ms |
| Oct 24, 2026 | 939 ms |
| Oct 31, 2026 | 953 ms |
| Nov 7, 2026 | 929 ms |
| Nov 14, 2026 | 908 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 125 ms |
| Oct 10, 2026 | 127 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 129 ms |
| Nov 7, 2026 | 127 ms |
| Nov 14, 2026 | 126 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.8 s · 563 KiBAbout 563 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 622 KiB32 files are served with short cache lifetimes, so returning visitors download them again (622 KiB).
Render-blocking requests
1.3 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Font display
850 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).
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 531 KiB and 645 ms of main-thread time.
Google Tag Manager adds 645 ms
645 msGoogle Tag Manager costs a phone 645 ms of main-thread work and 529 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 391 ms. During a long task the page ignores taps.
Minify JavaScript
300 ms · 76 KiB76 KiB could be saved by minifying JavaScript.
Improve image delivery
150 ms · 57 KiB4 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 585 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.4 s
9.4 sYour largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 10.1 s
10.1 sThe page becomes fully interactive after 10.1 s. Good is under 3.8 s.
Total Blocking Time: 526 ms
526 msScripts block taps and scrolling for 526 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 120 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 253 ms
253 msReal visitors wait 253 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.046
0.046The layout barely moves while loading (CLS 0.046, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.40 g of CO₂e: 47.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.4 MB in 78 requests
1.4 MBYour homepage downloads 1.4 MB in 78 requests on a phone: scripts 1.1 MB (20), images 214 KiB (37) and stylesheets 72 KiB (15). That is a lean page.
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
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (1 element).
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 6 failed. 1 more 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.
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 (175 characters)
Your meta description is 175 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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
3 links crawlers can't follow
3 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 incomplete here.
64 internal links, 6 external
The homepage links to 64 pages on primabanka.sk and 6 external pages.
3 checks passed
Title: 36 characters
Your title is a healthy 36 characters: “Prima banka - Jediná v každom okrese”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://primabanka.sk/sitemap.php.
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.primabanka.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.
1 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.
Other pages
1 linked page is broken
Your homepage links to https://www.primabanka.sk/osobny-ucet-odmena-za-platby-kartou, which answers with an error. Visitors hit a dead end and search engines drop it.
10 pages share a title
/, https://www.primabanka.sk/nastavenia-cookies, https://www.primabanka.sk/sadzobnik-poplatkov/sadzobnik-poplatkov, https://www.primabanka.sk/kariera/volne-pracovne-pozicie, https://www.primabanka.sk/o-banke and https://www.primabanka.sk/kontakt/centrala and 4 others all use the title “Prima banka - Jediná v každom okrese”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages share a meta description
https://www.primabanka.sk/nastavenia-cookies, https://www.primabanka.sk/pobocky-a-bankomaty, https://www.primabanka.sk/sadzobnik-poplatkov/sadzobnik-poplatkov, https://www.primabanka.sk/kariera/volne-pracovne-pozicie, https://www.primabanka.sk/o-banke and https://www.primabanka.sk/kontakt/centrala and 4 others use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.primabanka.sk/pre-biznis and https://www.primabanka.sk/pre-samospravy have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://www.primabanka.sk/nastavenia-cookies, https://www.primabanka.sk/pobocky-a-bankomaty, https://www.primabanka.sk/kalkulacky/hypokalkulacka, https://www.primabanka.sk/sadzobnik-poplatkov/sadzobnik-poplatkov, https://www.primabanka.sk/hypoteka-pre-mladych and https://www.primabanka.sk/terminovany-vklad took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
1 checks passed
Tap targets are thumb-sized
35 of 41 tappable elements near the top are at least 24 px.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 146 words
The homepage has only about 146 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.
2 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.
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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
3 other companies contacted
Loading the homepage contacts 3 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 primabanka.sk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Slovak Telekom, a.s.
Company
- Founded
- 1993
- Headquarters
- Žilina
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on primabanka.sk, including 13 speed issues, 6 SEO issues and 5 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.