Access dataland.ru. ???????

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

dataland.ru

808 ms

core.css

225 ms

ajax.css

229 ms

style.css

229 ms

style.css

236 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 93% of them (52 requests) were addressed to the original Dataland.ru, 2% (1 request) were made to Code.jquery.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (808 ms) belongs to the original domain Dataland.ru.

Content Size

615.7 kB

After Optimization

453.9 kB

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

HTML Optimization

-90%

Potential reduce by 123.5 kB

Original 137.6 kB
After minification 109.6 kB
After compression 14.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. This page needs HTML code to be minified as it can gain 28.0 kB, which is 20% 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 123.5 kB or 90% of the original size.

Image Optimization

-7%

Potential reduce by 8.9 kB

Original 132.9 kB
After minification 124.0 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. Dataland images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 25.1 kB

Original 323.0 kB
After minification 322.2 kB
After compression 297.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. This website has mostly compressed JavaScripts.

CSS Optimization

-20%

Potential reduce by 4.3 kB

Original 22.2 kB
After minification 21.9 kB
After compression 17.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. Dataland.ru needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 20% of the original size.

Requests Now

After Optimization

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dataland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 15 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 the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

High

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

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

Image elements do not have [alt] attributes

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

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dataland.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Dataland.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

dataland.ru

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

Report Summary

Performance

Accessibility

Best Practices

SEO

???????

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

dataland.ru

core.css

ajax.css

style.css

style.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

dataland.ru

core.css

ajax.css

style.css

style.css

style.css

style.css

style.css

style.css

template_styles.css

core.js

core_ajax.js

session.js

ajax.js

script.js

script.js

bootstrap-grid.css

owl.carousel.css

styles1.css

left_menu.css

jquery-1.10.2.min.js

jquery.mousewheel-3.0.6.pack.js

jquery.session.js

jquery.cookie.js

jquery.nicescroll.js

owl.carousel.js

new_lmenu.js

submit.js

superfish.js

api.js

fotorama.css

fotorama.js

reset.css

recaptcha__en.js

download.png

vk.jpg

logo.png

basket.png

41a9b4090017ffeee041e345e0b28ac2.jpeg

cded38771c0a07e26eda1e44154ea99c.jpeg

71473f551ec0c8f58331edd15f6c092d.jpeg

69dc90e784f57076e8931d592556ef40.jpeg

cbc0989fa114f6883e6dee52139717c5.jpeg