Tools & Wizards About Us
evo-wiki.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

evo-wiki.com

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

Page Load Speed

3.5 sec in total

First Response

847 ms

Resources Loaded

2.4 sec

Page Rendered

210 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 847 ms and then it took 2.6 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

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value990 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.264

46/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

evo-wiki.com

847 ms

reset.css

113 ms

defaults.css

130 ms

style.css

127 ms

avatars.css

150 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 73% of them (46 requests) were addressed to the original Evo-wiki.com, 8% (5 requests) were made to Youtube.com and 5% (3 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (847 ms) belongs to the original domain Evo-wiki.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.5 kB (10%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Evo-wiki.com main page is 1.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 939.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 49.0 kB

  • Original 62.2 kB
  • After minification 59.9 kB
  • After compression 13.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 49.0 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 49.3 kB

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

JavaScript Optimization

-15%

Potential reduce by 38.8 kB

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

CSS Optimization

-3%

Potential reduce by 3.3 kB

  • Original 101.5 kB
  • After minification 101.5 kB
  • After compression 98.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. Evo-wiki.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (61%)

Requests Now

59

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 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 19 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

evo-wiki.com

evo-wiki.com

847 ms

reset.css

reset.css

113 ms

defaults.css

defaults.css

130 ms

style.css

style.css

127 ms

avatars.css

avatars.css

150 ms

imgareaselect.css

imgareaselect.css

150 ms

dashicons.min.css

dashicons.min.css

394 ms

thickbox.css

thickbox.css

215 ms

color-picker.min.css

color-picker.min.css

236 ms

magnific.css

magnific.css

244 ms

responsive-tooltip.css

responsive-tooltip.css

252 ms

lightbox.min.css

lightbox.min.css

324 ms

wp-paginate.css

wp-paginate.css

348 ms

jquery.min.js

jquery.min.js

9 ms

jquery-migrate.min.js

jquery-migrate.min.js

368 ms

superfish.js

superfish.js

372 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

491 ms

jquery.imgareaselect.min.js

jquery.imgareaselect.min.js

468 ms

thickbox.js

thickbox.js

517 ms

error_notification.js

error_notification.js

490 ms

comment-reply.min.js

comment-reply.min.js

517 ms

cir_andzoom.min.js

cir_andzoom.min.js

481 ms

responsive-tooltip.js

responsive-tooltip.js

592 ms

wp-lightbox-2.min.js

wp-lightbox-2.min.js

651 ms

hoverIntent.min.js

hoverIntent.min.js

605 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

467 ms

clash-wiki-banner_en.gif

clash-wiki-banner_en.gif

393 ms

logo

logo

530 ms

background.jpg

background.jpg

121 ms

logo.png

logo.png

118 ms

twitter.png

twitter.png

392 ms

facebook.png

facebook.png

393 ms

gplus.png

gplus.png

394 ms

vk.png

vk.png

529 ms

rss.png

rss.png

500 ms

email.png

email.png

501 ms

about01_en_icon.jpg

about01_en_icon.jpg

502 ms

about02_en_icon.jpg

about02_en_icon.jpg

501 ms

about03_en_icon.jpg

about03_en_icon.jpg

502 ms

about04_en_icon.jpg

about04_en_icon.jpg

502 ms

about05_en_icon.jpg

about05_en_icon.jpg

503 ms

about06_en_icon.jpg

about06_en_icon.jpg

529 ms

app-store-en.png

app-store-en.png

528 ms

google-play-en.png

google-play-en.png

529 ms

1zhUYC_uQ2U

1zhUYC_uQ2U

113 ms

menu-primary-bg.png

menu-primary-bg.png

521 ms

menu-secondary-bg.png

menu-secondary-bg.png

521 ms

search.png

search.png

652 ms

hit

hit

520 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

88 ms

base.js

base.js

113 ms

evo-wiki.com

evo-wiki.com

458 ms

loadingAnimation.gif

loadingAnimation.gif

676 ms

ad_status.js

ad_status.js

158 ms

RAiHx6Z8aI87xfn3BcPOACt6MzvCMtPfFa8gMAvLcEc.js

RAiHx6Z8aI87xfn3BcPOACt6MzvCMtPfFa8gMAvLcEc.js

130 ms

embed.js

embed.js

54 ms

hit

hit

556 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

127 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

128 ms

id

id

24 ms

Create

Create

83 ms

GenerateIT

GenerateIT

14 ms

Accessibility Review

evo-wiki.com accessibility score

71

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

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

75

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

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

evo-wiki.com

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: