Website review, no card needed

beeline.kz logo

beeline.kz website review

Visit site (opens in a new tab)Reviewed 3 November 202651 issues · 90 checks

This review found 51 issues worth fixing on beeline.kz, 25 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.0 s3.0 sAug 8Oct 313.6 s
Show as table
DateReal-visitor load time (LCP)
Aug 8, 20263.2 s
Aug 15, 20263.9 s
Aug 22, 20263.8 s
Aug 29, 20263.6 s
Sep 5, 20263.4 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Oct 24, 20263.4 s
Oct 31, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
401 ms374 msAug 8Oct 31398 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026380 ms
Aug 15, 2026378 ms
Aug 22, 2026377 ms
Aug 29, 2026379 ms
Sep 5, 2026381 ms
Sep 12, 2026386 ms
Sep 19, 2026390 ms
Sep 26, 2026393 ms
Oct 3, 2026391 ms
Oct 10, 2026387 ms
Oct 17, 2026387 ms
Oct 24, 2026391 ms
Oct 31, 2026398 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

Full-page screenshot of beeline.kz (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beeline.kz at 1.1 s1.1 s
  2. beeline.kz at 2.2 s2.2 s
  3. beeline.kz at 3.3 s3.3 s
  4. beeline.kz at 4.4 s4.4 s
  5. beeline.kz at 5.5 s5.5 s
  6. beeline.kz at 6.6 s6.6 s
  7. beeline.kz at 7.7 s7.7 s
  8. beeline.kz at 8.8 s8.8 s

Speed

11 to fix21
  • Reduce unused JavaScript

    6.3 s · 1.9 MB

    About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.

  • Use efficient cache lifetimes

    2.2 s · 807 KiB

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

  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    1.5 s · 394 KiB

    About 394 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 21

    21/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.9 MB and 1.7 s of main-thread time.

  • Google Tag Manager adds 864 ms

    864 ms

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

  • Improve image delivery

    745 KiB

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

  • TikTok adds 377 ms

    377 ms

    TikTok costs a phone 377 ms of main-thread work and 313 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.

  • Main-thread work: 3.5 s

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

  • Facebook adds 259 ms

    259 ms

    Facebook costs a phone 259 ms of main-thread work and 344 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.

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    133 KiB

    133 KiB could be saved by minifying JavaScript.

  • Document request latency

    104 KiB

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

  • Legacy JavaScript

    51 KiB

    Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need.

  • 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

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 579 ms

    579 ms

    Your server sent the HTML in 579 ms, well inside Google's 600 ms guideline.

Core Web Vitals

13 to fix0
  • 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.

  • Real-user LCP: 6.3 s

    6.3 s

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

  • Real-user FCP: 4.8 s

    4.8 s

    Real visitors see the first content after 4.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 3.4 s

    3.4 s

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

  • First Contentful Paint: 7.8 s

    7.8 s

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

  • Largest Contentful Paint: 48.8 s

    48.8 s

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

  • Speed Index: 19.9 s

    19.9 s

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

  • Time to Interactive: 49.2 s

    49.2 s

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

  • Total Blocking Time: 860 ms

    860 ms

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

  • Cumulative Layout Shift: 0.276

    0.276

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

  • Real-user INP: 405 ms

    405 ms

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

  • Real-user CLS: 0.14

    0.14

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

  • 40 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

Images and page weight

4 to fix25
  • Page weight: 11.1 MB in 176 requests

    11.1 MB

    Your homepage downloads 11.1 MB in 176 requests on a phone: images 7.0 MB (54), scripts 2.8 MB (52) and other files 613 KiB (58). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 6.2 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    689 KiB

    5 images are downloaded at several times the size a phone draws them, for example km_3392_1180x290_kz_1_4b20907ed1.svg at 1,180 px wide, shown at 366 px. Resized copies would save about 689 KiB.

  • 9 images in older formats

    9 images (894 KiB) are 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.

  • About 3.1 g of CO₂ per visit

    3.14 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

7 to fix69
  • 39 images without alt text

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

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    2 dropdowns have no label.

  • 20 links without text

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

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • 4 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

  • SVG elements with an img role do not have an accessible text alternative

    SVG elements with an img role do not have an accessible text alternative (2 elements).

SEO

5 to fixGoogle 8572
  • No H1 headline

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

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Beeline-ды таңдасаңыз — таңдайтыныңыз… №1 ТҰРАҚТЫ-МОБИЛДІ интернет”.

  • No structured data

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

  • Meta description is short (35 characters)

    Your meta description is only 35 characters: “билайн оператор, байланыс операторы”. 70 to 160 characters is enough to sell the click.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 62 internal links, 47 external

    The homepage links to 62 pages on beeline.kz and 47 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://beeline.kz/kk.

  • 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://beeline.kz/sitemap.xml.

AI search readiness

1 to fix83
  • 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://beeline.kz/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

3 to fix86
  • 6 pages share a title

    https://beeline.kz/kk/products/tariffs, https://beeline.kz/kk/rouming, https://beeline.kz/kk/entertainment, https://beeline.kz/kk/offices, https://beeline.kz/kk/map and https://beeline.kz/kk/fraud all use the title “Beeline Казахстан - официальный сайт оператора Beeline в Казахстане”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://beeline.kz/kk/products/tariffs, https://beeline.kz/kk/rouming, https://beeline.kz/kk/entertainment, https://beeline.kz/kk/offices, https://beeline.kz/kk/map and https://beeline.kz/kk/fraud use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://beeline.kz/kk/products/tariffs, https://beeline.kz/kk/rouming, https://beeline.kz/kk/mfs, https://beeline.kz/kk/entertainment, https://beeline.kz/kk/offices and https://beeline.kz/kk/map and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://beeline.kz/kk/products/tariffs, https://beeline.kz/kk/internet-home-tv-mobile, https://beeline.kz/kk/mfs, https://beeline.kz/kk/entertainment, https://beeline.kz/kk/offices and https://beeline.kz/kk/map and 3 others 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.

  • 7 pages slow to respond

    https://beeline.kz/kk/products/tariffs, https://beeline.kz/kk/internet-home-tv-mobile, https://beeline.kz/kk/rouming, https://beeline.kz/kk/mfs, https://beeline.kz/kk/entertainment and https://beeline.kz/kk/offices and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    10 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 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 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    43 of 53 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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.

  • Only about 93 words

    The homepage has only about 93 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

  • 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
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel and 1 more (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.

  • 29 cookies set on arrival

    29

    Opening the homepage sets 29 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.

  • 27 other companies contacted

    Loading the homepage contacts 27 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 beeline.kz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Analytics
Google Tag Manager
Hosting
Kar-Tel LLC

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on beeline.kz, including 24 speed issues, 5 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25