Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ffin.kz

Freedom Broker Казахстан | Инвестиционная компания Freedom Broker

Page Load Speed

8.3 sec in total

First Response

1.4 sec

Resources Loaded

5.5 sec

Page Rendered

1.4 sec

ffin.kz screenshot

About Website

Welcome to ffin.kz homepage info - get ready to check Ffin best content for Kazakhstan right away, or after learning these important things about ffin.kz

Freedom Broker Казахстан ✔️ Более 13 лет на рынке ценных бумаг ✔️ Собственный капитал более $508 млн ✔️ Более 479 тысяч клиентских счетов

Visit ffin.kz

Key Findings

We analyzed Ffin.kz page load time and found that the first response time was 1.4 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

ffin.kz performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value21.9 s

0/100

25%

SI (Speed Index)

Value55.0 s

0/100

10%

TBT (Total Blocking Time)

Value35,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value63.7 s

0/100

10%

Network Requests Diagram

ffin.kz

1386 ms

k2.css

244 ms

menu-866aa62ff6c16fcab414a76f625ee345.css

613 ms

grid-responsive.css

530 ms

bootstrap.css

739 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 80% of them (45 requests) were addressed to the original Ffin.kz, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ffin.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 576.9 kB (49%)

Content Size

1.2 MB

After Optimization

601.3 kB

In fact, the total size of Ffin.kz main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 438.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 54.8 kB

  • Original 64.9 kB
  • After minification 39.3 kB
  • After compression 10.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 25.6 kB, which is 39% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 54.8 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 20.6 kB

  • Original 438.4 kB
  • After minification 417.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Ffin images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 258.2 kB

  • Original 385.7 kB
  • After minification 377.2 kB
  • After compression 127.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 258.2 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 243.3 kB

  • Original 289.2 kB
  • After minification 257.3 kB
  • After compression 45.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Ffin.kz needs all CSS files to be minified and compressed as it can save up to 243.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (59%)

Requests Now

51

After Optimization

21

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ffin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

ffin.kz accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ffin.kz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ffin.kz SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ffin.kz can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Ffin.kz main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Ffin. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: