Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

evo-wiki.com

Evolution: Battle for Utopia / Эволюция: Битва за Утопию

Page Load Speed

3.4 sec in total

First Response

599 ms

Resources Loaded

2.4 sec

Page Rendered

392 ms

evo-wiki.com screenshot

About Website

Visit evo-wiki.com now to see the best up-to-date Evo Wiki content for Russia and also check out these interesting facts you probably never knew about evo-wiki.com

Evolution: Battle for Utopia — a new multi-genre game blockbuster. Unprecedented Action, RPG and Strategy in one game! Эволюция: Битва за Утопию – это

Visit evo-wiki.com

Key Findings

We analyzed Evo-wiki.com page load time and found that the first response time was 599 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

evo-wiki.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

34/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value28,380 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.511

15/100

15%

TTI (Time to Interactive)

Value40.1 s

0/100

10%

Network Requests Diagram

evo-wiki.com

599 ms

dY5hCsIwDEYv1JpN5hn0FpK1cRaTdjTZ1NtbJggi_kq-771AOjgVO6KQ-v15EOA0QlCFSkrmuj800gUXNv0R1J5MrgeM0XMJyB5XNKzwHuoGSDJhJVRiCvad3AEi6jWFknUnKTfbWrqN5fFZ3H32GBvcHgmFS_VzQ1S3i75VIpTNJ8GJdLNmXqaUXw.css

407 ms

TYxBDsIwDAQ_hLHKj1K6DZacOIpdoLweWkDqbTQ72oE7vFl1uYOKjaKguQvqpCuFmYa0Y_JTp4EfjVTyLUZ70oU9VoXz35yL1G_TUpaaAkf-LDNSLB0TSUkZ9DIrfHXnDWg_ewM.css

277 ms

09dPzEqs0EvPz0_PSU0syCzWS87PBYvp52QmFetnFZamFlXqG0IZermZeXpZxTrGUD6coZubmV6UWJIKUgAA.js

827 ms

dczBDYAgDADAhcSqcQfdwoCpWEIBKX24vTqA_8uNsGdmTM0QW48CQaBE9ZR6ptQNsOa2WEYx0zYzRHKfEC1YD5LzD4RLsd49Z0cR314f.js

291 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 53% of them (29 requests) were addressed to the original Evo-wiki.com, 9% (5 requests) were made to Pagead2.googlesyndication.com and 7% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Evo-wiki.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 694.0 kB (38%)

Content Size

1.8 MB

After Optimization

1.1 MB

In fact, the total size of Evo-wiki.com 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. 65% of websites need less resources to load. Images take 858.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 46.9 kB

  • Original 60.2 kB
  • After minification 58.2 kB
  • After compression 13.3 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 46.9 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 6.9 kB

  • Original 858.6 kB
  • After minification 851.7 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. Evo Wiki images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 394.6 kB

  • Original 567.4 kB
  • After minification 526.4 kB
  • After compression 172.8 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 394.6 kB or 70% of the original size.

CSS Optimization

-76%

Potential reduce by 245.6 kB

  • Original 323.9 kB
  • After minification 322.7 kB
  • After compression 78.3 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. Evo-wiki.com needs all CSS files to be minified and compressed as it can save up to 245.6 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (49%)

Requests Now

51

After Optimization

26

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evo Wiki. 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 as a result speed up the page load time.

Accessibility Review

evo-wiki.com accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

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

Best Practices

evo-wiki.com 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

evo-wiki.com SEO score

97

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Evo-wiki.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Evo-wiki.com 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 description is not detected on the main page of Evo Wiki. 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: