Tools & Wizards About Us
f2.kz screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

f2.kz

Форум налогоплательщиков и бухгалтеров Казахстана

Page Load Speed

3.6 sec in total

First Response

771 ms

Resources Loaded

2.6 sec

Page Rendered

201 ms

f2.kz screenshot

About Website

Visit f2.kz now to see the best up-to-date F 2 content for Kazakhstan and also check out these interesting facts you probably never knew about f2.kz

Казахстанскому бухгалтеру и налогоплательщику: ЭФНО, СГДС и другие налоговые программы Новые версии программ и обновления другие вопросы волнующие налогоплательщиков РК

Visit f2.kz

Key Findings

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

Performance Metrics

f2.kz performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

f2.kz

771 ms

www.f2.kz

797 ms

urchin.js

22 ms

style-const.css

784 ms

ddmenuv2009030701.css

782 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 12% of them (2 requests) were addressed to the original F2.kz, 71% (12 requests) were made to Img1.f2.kz and 12% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (801 ms) relates to the external source Img1.f2.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.7 kB (79%)

Content Size

133.0 kB

After Optimization

27.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 41.2 kB

  • Original 52.4 kB
  • After minification 50.3 kB
  • After compression 11.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 41.2 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 37 B

  • Original 396 B
  • After minification 359 B

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. F 2 images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 971 B

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.9 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 971 B or 14% of the original size.

CSS Optimization

-87%

Potential reduce by 63.5 kB

  • Original 73.3 kB
  • After minification 53.1 kB
  • After compression 9.8 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. F2.kz needs all CSS files to be minified and compressed as it can save up to 63.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (71%)

Requests Now

14

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

f2.kz

f2.kz

771 ms

www.f2.kz

www.f2.kz

797 ms

urchin.js

urchin.js

22 ms

style-const.css

style-const.css

784 ms

ddmenuv2009030701.css

ddmenuv2009030701.css

782 ms

__utm.gif

__utm.gif

11 ms

tree_split.gif

tree_split.gif

754 ms

tree_leaf.gif

tree_leaf.gif

754 ms

tree_expand.gif

tree_expand.gif

801 ms

tree_end.gif

tree_end.gif

801 ms

six_0a.gif

six_0a.gif

131 ms

six_1a.gif

six_1a.gif

132 ms

corners_left.png

corners_left.png

135 ms

corners_right.png

corners_right.png

133 ms

six_0.gif

six_0.gif

130 ms

arrow.gif

arrow.gif

132 ms

hit

hit

252 ms

Accessibility Review

f2.kz accessibility score

51

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[accesskey] values are not unique

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

f2.kz best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

f2.kz SEO score

62

Search Engine Optimization Advices

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

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

f2.kz

Open Graph description is not detected on the main page of F 2. 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: