odeabank.com.tr website review

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

3 files are served with short cache lifetimes, so returning visitors download them again (111 KiB).

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

About 245 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

4 third-party services load with your homepage (efilli.com, Google Tag Manager and dataroid.com and others), adding 661 KiB and 501 ms of main-thread time.

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

The page has 2,194 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

9 images could be 183 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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.

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “alt=”. Most of its time is resource load delay (4.2 s).

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

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

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

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

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

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

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

5 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-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 image is downloaded at several times the size a phone draws it, for example GalleryImage-Image-1340-2x.png at 502 px wide, shown at 133 px. Resized copies would save about 26 KiB.

1 image (232 KiB) is 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.

2 images further down the page (110 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

8 elements use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

3 dropdowns have no label.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements must only use permitted ARIA attributes: 8 elements on the page fail this check, rated serious by axe-core.

6 elements have a tabindex above 0, which scrambles the keyboard order.

Some list items are not inside a list.

1 tap target is too small or too close together to hit reliably with a finger.

31 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

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

14 links have no real href, so search engines can't follow them.

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

The homepage links to 149 pages on odeabank.com.tr and 7 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.

https://www.odeabank.com.tr/kampanyalar/aylik-299dan-baslayan-faiz-orani-ile-ihtiyac-kredisi-odeada-30349 and https://www.odeabank.com.tr/kampanyalar/oksijen-hesap-paraniza-deger-veren-hesap-23135 use the same meta description. A description written for each page earns more clicks.

https://www.odeabank.com.tr/kampanyalar/aylik-299dan-baslayan-faiz-orani-ile-ihtiyac-kredisi-odeada-30349, https://www.odeabank.com.tr/kampanyalar/oksijen-hesap-paraniza-deger-veren-hesap-23135, https://www.odeabank.com.tr/kampanyalar/yakinini-odeaya-davet-et-kampanyasi-26791, https://www.odeabank.com.tr/kampanyalar, https://www.odeabank.com.tr/bireysel and https://www.odeabank.com.tr/bireysel/yatirim and 3 others took over 3 s to send their HTML from our server.

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

8 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Your longest form asks for 23 fields (0 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 587 words of visible text.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.