Access lifedata.ru.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

146 ms

lifedata.ru

584 ms

manifest.3a3a04ed93f3a7a6f850.js

236 ms

head-scripts.2ff7329da5c555107564.js

359 ms

design-system.e37fb26f5769a4208584.js

605 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lifedata.ru, 6% (4 requests) were made to Files.reg.ru and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (994 ms) relates to the external source Reg.ru.

Content Size

448.7 kB

After Optimization

200.7 kB

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

HTML Optimization

-86%

Potential reduce by 232.4 kB

Original 269.9 kB
After minification 205.8 kB
After compression 37.5 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 64.1 kB, which is 24% 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 232.4 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 1.3 kB

Original 31.2 kB
After minification 29.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. Lifedata images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 43 B

Original 86.8 kB
After minification 86.8 kB
After compression 86.7 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

-23%

Potential reduce by 14.2 kB

Original 60.8 kB
After minification 60.8 kB
After compression 46.6 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. Lifedata.ru needs all CSS files to be minified and compressed as it can save up to 14.2 kB or 23% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Page is blocked from indexing

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/).

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

Open Graph data is detected on the main page of Lifedata. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: