Tools & Wizards About Us
fatum.ru screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fatum.ru

Беспроводной Интернет в Казани | Провайдер интернет-услуг «Фатум»

Page Load Speed

5.5 sec in total

First Response

1.4 sec

Resources Loaded

3.6 sec

Page Rendered

442 ms

fatum.ru screenshot

About Website

Welcome to fatum.ru homepage info - get ready to check Fatum best content for Russia right away, or after learning these important things about fatum.ru

Компания «Фатум» предлагает подключение беспроводного Интернета в Казани по выгодной цене. Установка необходимого оборудования, доступный высокоскоростной Интернет. Беспроводной Интернет в Казани | Пр...

Visit fatum.ru

Key Findings

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

Performance Metrics

fatum.ru performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

93/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

fatum.ru

1381 ms

bootstrap.min.css

302 ms

styls.css

287 ms

jquery.min.js

19 ms

bootstrap.min.js

291 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 83% of them (24 requests) were addressed to the original Fatum.ru, 7% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Portal.fatum.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 161.7 kB (41%)

Content Size

396.8 kB

After Optimization

235.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fatum.ru main page is 396.8 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. 25% of websites need less resources to load. HTML takes 186.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 140.7 kB

  • Original 186.4 kB
  • After minification 180.9 kB
  • After compression 45.7 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 140.7 kB or 75% of the original size.

Image Optimization

-18%

Potential reduce by 11.1 kB

  • Original 63.0 kB
  • After minification 51.9 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. Obviously, Fatum needs image optimization as it can save up to 11.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-8%

Potential reduce by 9.8 kB

  • Original 126.8 kB
  • After minification 126.8 kB
  • After compression 117.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 147 B

  • Original 20.5 kB
  • After minification 20.5 kB
  • After compression 20.4 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. Fatum.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (15%)

Requests Now

27

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fatum.ru

fatum.ru

1381 ms

bootstrap.min.css

bootstrap.min.css

302 ms

styls.css

styls.css

287 ms

jquery.min.js

jquery.min.js

19 ms

bootstrap.min.js

bootstrap.min.js

291 ms

logo.png

logo.png

579 ms

uslugi1.gif

uslugi1.gif

593 ms

uslugi2.gif

uslugi2.gif

597 ms

uslugi3.gif

uslugi3.gif

709 ms

bnr2.gif

bnr2.gif

1159 ms

ok.png

ok.png

447 ms

eldorado_logo.gif

eldorado_logo.gif

595 ms

banks.gif

banks.gif

725 ms

equant.gif

equant.gif

742 ms

lorien.gif

lorien.gif

743 ms

pfubiley.gif

pfubiley.gif

746 ms

rr_logo.gif

rr_logo.gif

850 ms

mak_logo.gif

mak_logo.gif

869 ms

tvt_logo.gif

tvt_logo.gif

889 ms

ugibdd.gif

ugibdd.gif

890 ms

ippodrom.gif

ippodrom.gif

894 ms

background_1.gif

background_1.gif

944 ms

bnr.gif

bnr.gif

1116 ms

background2.gif

background2.gif

1002 ms

HelveticaLight.otf

HelveticaLight.otf

668 ms

analytics.js

analytics.js

19 ms

loader_1_n8otjo.js

loader_1_n8otjo.js

1851 ms

collect

collect

14 ms

js

js

48 ms

Accessibility Review

fatum.ru accessibility score

95

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

fatum.ru 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fatum.ru SEO score

90

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fatum.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Fatum.ru 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

fatum.ru

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