Website review, no card needed

kibar.com logo

kibar.com website review

Visit site (opens in a new tab)Reviewed 1 November 202635 issues · 82 checks

This review found 35 issues worth fixing on kibar.com, 13 of them high impact, across 82 checks. The most urgent: mobile performance score: 47. 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
1.0 s827 msMay 9Oct 24989 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026876 ms
May 16, 2026868 ms
May 23, 2026855 ms
May 30, 2026886 ms
Jun 6, 2026852 ms
Jun 13, 2026854 ms
Jun 20, 2026861 ms
Jun 27, 2026871 ms
Jul 4, 2026927 ms
Jul 11, 2026890 ms
Jul 18, 2026859 ms
Jul 25, 2026866 ms
Aug 1, 2026897 ms
Aug 8, 2026952 ms
Aug 15, 2026995 ms
Aug 22, 2026972 ms
Aug 29, 2026946 ms
Sep 5, 2026935 ms
Sep 12, 2026920 ms
Sep 19, 2026956 ms
Sep 26, 2026990 ms
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 2026990 ms
Oct 24, 2026989 ms
Real-visitor tap response (INP)75th percentile, phones
125 ms90 msMay 9Oct 24107 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026121 ms
May 16, 2026120 ms
May 23, 2026112 ms
May 30, 2026110 ms
Jun 6, 2026100 ms
Jun 13, 202694 ms
Jun 20, 202698 ms
Jun 27, 2026100 ms
Jul 4, 2026102 ms
Jul 11, 202697 ms
Jul 18, 202696 ms
Jul 25, 202694 ms
Aug 1, 202695 ms
Aug 8, 202699 ms
Aug 15, 2026107 ms
Aug 22, 2026105 ms
Aug 29, 2026108 ms
Sep 5, 2026111 ms
Sep 12, 2026107 ms
Sep 19, 2026110 ms
Sep 26, 2026113 ms
Oct 3, 2026108 ms
Oct 10, 2026110 ms
Oct 17, 2026111 ms
Oct 24, 2026107 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 kibar.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kibar.com at 0.4 s0.4 s
  2. kibar.com at 0.8 s0.8 s
  3. kibar.com at 1.2 s1.2 s
  4. kibar.com at 1.7 s1.7 s
  5. kibar.com at 2.1 s2.1 s
  6. kibar.com at 2.5 s2.5 s
  7. kibar.com at 2.9 s2.9 s
  8. kibar.com at 3.3 s3.3 s

Speed

7 to fix47
  • Mobile performance score: 47

    47/100

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

  • Render-blocking requests

    900 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.

  • Improve image delivery

    150 ms · 657 KiB

    5 images could be 657 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 JavaScript

    460 ms · 135 KiB

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

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • 1,817 HTML elements

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

  • Cloudflare CDN adds 3 ms

    3 ms

    Cloudflare CDN costs a phone 3 ms of main-thread work and 295 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 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and Cloudflare CDN and others), adding 680 KiB and 209 ms of main-thread time.

  • Use efficient cache lifetimes

    50 ms · 44 KiB

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    48 KiB

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

  • Forced reflow

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 333 ms of it running JavaScript. That is comfortably low.

  • Server response: 150 ms

    150 ms

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

Core Web Vitals

8 to fix67
  • 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 CLS: 1.05

    1.05

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

  • Cumulative Layout Shift: 1.639

    1.639

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

  • Largest Contentful Paint: 7.1 s

    7.1 s

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

  • 50 images without width and height

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

  • Time to Interactive: 7.1 s

    7.1 s

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

  • Speed Index: 4.5 s

    4.5 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

6 checks passed
  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 136 ms

    136 ms

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 417 ms

    417 ms

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

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

  • Total Blocking Time: 36 ms

    36 ms

    Scripts block the page for only 36 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix55
  • 1 image over 500 KB

    sur-rapor-lacp-odul-2026.jpg weighs 631 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    559 KiB

    1 image is downloaded at several times the size a phone draws it, for example sur-rapor-lacp-odul-2026.jpg at 3,475 px wide, shown at 390 px. Resized copies would save about 559 KiB.

  • 4 images in older formats

    4 images (761 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 0.5 g of CO₂ per visit

    0.49 g

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

2 checks passed
  • Page weight: 1.7 MB in 44 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 44 requests on a phone: images 808 KiB (14), fonts 452 KiB (8) and scripts 408 KiB (13). That is a lean page.

  • Images load when needed

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

Accessibility

6 to fixGoogle 7891
  • 27 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 73 links without text

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

  • Headings should not be empty (15 elements)

    Headings should not be empty: 15 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 7779
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 132 internal links, 11 external

    The homepage links to 132 pages on kibar.com and 11 external pages.

5 checks passed
  • Title: 34 characters

    Your title is a healthy 34 characters: “Kibar Holding A.Ş. - Kibar Holding”.

  • Canonical URL set

    The canonical URL is https://www.kibar.com/tr-tr/.

  • Structured data in place

    Structured data found: Corporation.

  • 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://www.kibar.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.kibar.com/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.

3 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,189 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 4 pages share a title

    https://www.kibar.com/tr-tr, /, https://www.kibar.com/en and https://www.kibar.com/de-de all use the title “Kibar Holding A.Ş. - Kibar Holding”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    /, https://www.kibar.com/en, https://www.kibar.com/de-de, https://www.kibar.com/tr-tr/holding/yonetim-kurulu, https://www.kibar.com/tr-tr/holding/ust-yonetim and https://www.kibar.com/tr-tr/holding/tarihce have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.kibar.com/tr-tr. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    /, https://www.kibar.com/en and https://www.kibar.com/de-de have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    85 of 89 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 risk reducer

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

  • About 1,228 words of copy

    The homepage carries about 1,228 words of visible text.

3 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 and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 7 cookies set on arrival

    7

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

  • 5 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Ictbulut Ict Bulut Bilisim A.S.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on kibar.com, including 15 speed issues, 3 SEO issues and 3 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