Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

facto.ru

Ключевые новости Воронежа и Воронежской области — De Facto

Page Load Speed

4.7 sec in total

First Response

1.1 sec

Resources Loaded

3.2 sec

Page Rendered

474 ms

facto.ru screenshot

About Website

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

Узнавайте каждый день о важнейших новостях Воронежа и Воронежской области — медиагруппа De Facto собирает главное по всем ключевым СМИ и реально экономит ваше время

Visit facto.ru

Key Findings

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

Performance Metrics

facto.ru performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

36/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.096

90/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

facto.ru

1104 ms

kernel_main.css

122 ms

template_22ed54371ecff351a5885bd025f9102b.css

225 ms

kernel_main.js

455 ms

template_d465af24fd0596c8d26728009119a76f.js

625 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 65% of them (43 requests) were addressed to the original Facto.ru, 8% (5 requests) were made to Mc.yandex.ru and 6% (4 requests) were made to W.uptolike.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Facto.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 801.3 kB (48%)

Content Size

1.7 MB

After Optimization

861.3 kB

In fact, the total size of Facto.ru main page is 1.7 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. 40% of websites need less resources to load. Javascripts take 816.1 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 34.9 kB

  • Original 50.0 kB
  • After minification 46.4 kB
  • After compression 15.1 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 34.9 kB or 70% of the original size.

Image Optimization

-6%

Potential reduce by 44.2 kB

  • Original 687.4 kB
  • After minification 643.2 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. Facto images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 628.9 kB

  • Original 816.1 kB
  • After minification 666.5 kB
  • After compression 187.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 628.9 kB or 77% of the original size.

CSS Optimization

-85%

Potential reduce by 93.3 kB

  • Original 109.1 kB
  • After minification 97.6 kB
  • After compression 15.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. Facto.ru needs all CSS files to be minified and compressed as it can save up to 93.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (40%)

Requests Now

60

After Optimization

36

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

Accessibility Review

facto.ru accessibility score

81

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facto.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Facto.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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