mkb.hu website review

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

6 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.3 s faster on a phone.

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

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

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

3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google/Doubleclick Ads), adding 573 KiB and 667 ms of main-thread time.

Google Tag Manager costs a phone 667 ms of main-thread work and 568 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.

About 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

A phone's processor spends 2.7 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 40.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MBH Otthon Start Lakáshitel kedvezményes kamattal 11.15-ig …”.

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

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

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

Scripts block taps and scrolling for 826 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 11.5 MB in 46 requests on a phone: images 8.4 MB (22), scripts 1.6 MB (6) and fonts 1.0 MB (4). Under 2 MB keeps phones on slow connections fast.

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

12 links have no text or label, so screen readers cannot say where they go.

Elements with role="dialog" or role="alertdialog" do not have accessible names. (4 elements).

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

Your title is only 8 characters: “MBH Bank”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There is no robots.txt at mbhbank.hu/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 148 pages on mkb.hu and 50 external pages.

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.

Your homepage links to https://www.mbhbank.hu/fiokkereso, https://www.mbhbank.hu/bankszunnap and https://www.mbhbank.hu/bankbiztonsag, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.mbhbank.hu/sajtoszoba and https://www.mbhbank.hu/fenntarthatosag-tarsadalmi-felelossegvallalas have no meta description, so Google writes the search snippet from whatever text it finds.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Chrome logged issues while loading the page (“Blocked by cross-origin policy”).

Large scripts ship without source maps.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 8,256 words of visible text.