Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

zeos.in

DataLife Engine

Page Load Speed

4.1 sec in total

First Response

321 ms

Resources Loaded

3.2 sec

Page Rendered

572 ms

zeos.in screenshot

About Website

Welcome to zeos.in homepage info - get ready to check Zeos best content for Russia right away, or after learning these important things about zeos.in

Демонстраційна версія DataLife Engine

Visit zeos.in

Key Findings

We analyzed Zeos.in page load time and found that the first response time was 321 ms and then it took 3.8 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

zeos.in performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

zeos.in

321 ms

zeos.in

569 ms

index.php

128 ms

index.php

255 ms

main.css

365 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 97% of them (89 requests) were addressed to the original Zeos.in, 2% (2 requests) were made to Dle-news.ru and 1% (1 request) were made to Get.mycounter.ua. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Zeos.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.4 kB (6%)

Content Size

1.8 MB

After Optimization

1.7 MB

In fact, the total size of Zeos.in main page is 1.8 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. 35% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 56.3 kB

  • Original 68.2 kB
  • After minification 64.3 kB
  • After compression 11.9 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 56.3 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 44.6 kB

  • Original 1.7 MB
  • After minification 1.7 MB

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

JavaScript Optimization

-21%

Potential reduce by 5.6 kB

  • Original 27.2 kB
  • After minification 27.2 kB
  • After compression 21.6 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 5.6 kB or 21% of the original size.

CSS Optimization

-37%

Potential reduce by 4.8 kB

  • Original 13.1 kB
  • After minification 13.1 kB
  • After compression 8.2 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. Zeos.in needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (60%)

Requests Now

80

After Optimization

32

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

Accessibility Review

zeos.in accessibility score

45

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.

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

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

Form elements do not have associated labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

zeos.in best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

zeos.in SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zeos.in 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 Zeos.in 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 Zeos. 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: