bta.ee website review

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

About 673 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.

3 images could be 334 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

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

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

trengo.eu costs a phone 162 ms of main-thread work and 406 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.

7 third-party services load with your homepage (Google Tag Manager, trengo.eu and bunny.net and others), adding 782 KiB and 341 ms of main-thread time.

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

22 KiB could be saved by minifying CSS.

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

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 visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.

Your largest element takes 16.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Real visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

11 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 156 ms to 172 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 4.6 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.1 MB in 192 requests on a phone: media 2.3 MB (2), scripts 1.9 MB (96) and images 535 KiB (10). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example media-2026-Banners-10-casco-edit-2.png.webp at 1,546 px wide, shown at 350 px. Resized copies would save about 241 KiB.

3 images further down the page (441 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 1.44 g of CO₂e: 173.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to 32 pages on bta.ee and 0 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.

There is no /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.

/era/kaskokindlustus, /era/kodukindlustus, /era/reisikindlustus, /era/onnetusjuhtumikindlustus and /era/vaikelaeva-kindlustus all use the title “Radware Block Page”. Search engines can't tell which page to show for a search, so each competes with the others.

/bta-st/blog/esimest-korda-vigi-ajaloos-toimus-kontserni-tegevjuhtide-konverents-baltikumis, /bta-st/blog/bta-kutsub-inimesi-kindlustusele-teisiti-vaatama-vahem-hirmu-rohkem-elamist, /era/kaskokindlustus, /era/kodukindlustus, /era/reisikindlustus and /era/onnetusjuhtumikindlustus and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/era/kaskokindlustus, /era/kodukindlustus, /era/reisikindlustus, /era/onnetusjuhtumikindlustus and /era/vaikelaeva-kindlustus have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/bta-st/uudised/mida-saab-tootaja-tegelikult-400-euro-eest-boonus-tervise-ja-spordihuve-voi-ravikindlustus, /bta-st/uudised/eesti-paases-kergemalt-augustitorm-toi-latis-ja-leedus-kaasa-miljonitesse-eurodesse-ulatuvad-kahjud, /bta-st/blog/kas-sinu-reisiraha-on-kaitstud-kui-lennufirma-laheb-pankrotti and /bta-st/blog/suvel-autoga-valismaale-6-asja-mida-enne-reisi-kontrollida took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistration') https://www.bta.ee/:3:6757”.

Large scripts ship without source maps.

Your certificate from Sectigo Limited · Sectigo Public Server Authentication CA DV R36 expires in 1 day. If it doesn't renew automatically, visitors get a security warning.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

bta.ee has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 19 cookies (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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.