Tools & Wizards About Us
wotafaq.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

wotafaq.com

WOTaFAQ - ответы на часто задаваемые вопросы по игре World of tanks

Page Load Speed

7.6 sec in total

First Response

564 ms

Resources Loaded

6.5 sec

Page Rendered

580 ms

wotafaq.com screenshot

About Website

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

Независимый проект - Ответы на часто задаваемые вопросы по игре World of tanks. Узнай все и про все из мира WOT.

Visit wotafaq.com

Key Findings

We analyzed Wotafaq.com page load time and found that the first response time was 564 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

wotafaq.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value2,330 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.166

71/100

15%

TTI (Time to Interactive)

Value28.6 s

0/100

10%

Network Requests Diagram

wotafaq.com

564 ms

wotafaq.com

2075 ms

qa-styles.css

854 ms

slick.css

27 ms

slick-theme.css

45 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 49% of them (34 requests) were addressed to the original Wotafaq.com, 12% (8 requests) were made to Vk.com and 10% (7 requests) were made to St6-21.vk.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Wotafaq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.5 kB (18%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wotafaq.com main page is 1.5 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 664.0 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 211.9 kB

  • Original 239.0 kB
  • After minification 190.7 kB
  • After compression 27.2 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 48.3 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 211.9 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 185 B

  • Original 664.0 kB
  • After minification 663.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. WOTaFAQ images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 33.6 kB

  • Original 277.0 kB
  • After minification 277.0 kB
  • After compression 243.3 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 33.6 kB or 12% of the original size.

CSS Optimization

-7%

Potential reduce by 24.8 kB

  • Original 348.3 kB
  • After minification 348.3 kB
  • After compression 323.5 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. Wotafaq.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (62%)

Requests Now

61

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wotafaq.com

wotafaq.com

564 ms

wotafaq.com

wotafaq.com

2075 ms

qa-styles.css

qa-styles.css

854 ms

slick.css

slick.css

27 ms

slick-theme.css

slick-theme.css

45 ms

myCss.css

myCss.css

43 ms

jquery.min.js

jquery.min.js

23 ms

context.js

context.js

967 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1178 ms

qa-page.js

qa-page.js

37 ms

jquery.bxslider.js

jquery.bxslider.js

42 ms

slick.min.js

slick.min.js

841 ms

thickbox.js

thickbox.js

906 ms

thickbox.css

thickbox.css

54 ms

style.css

style.css

58 ms

share.js

share.js

398 ms

jquery.bxslider.css

jquery.bxslider.css

874 ms

index1.php

index1.php

1009 ms

jquery.cookie.js

jquery.cookie.js

66 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

81 ms

lib.js

lib.js

885 ms

customized.fancybox.css

customized.fancybox.css

1679 ms

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

254 ms

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

264 ms

a2e4f467b89f415485d27967b8a95b2f.gif

a2e4f467b89f415485d27967b8a95b2f.gif

63 ms

boyw.png

boyw.png

61 ms

rss.jpg

rss.jpg

60 ms

2.png

2.png

59 ms

1.png

1.png

60 ms

d.png

d.png

797 ms

sd1.jpg

sd1.jpg

65 ms

12331.png

12331.png

64 ms

gold.png

gold.png

62 ms

search.png

search.png

824 ms

shadow.png

shadow.png

48 ms

watch.js

watch.js

3 ms

hit

hit

511 ms

feed-icon-14x14.png

feed-icon-14x14.png

34 ms

users-icon.png

users-icon.png

33 ms

upload.gif

upload.gif

162 ms

widget_community.php

widget_community.php

166 ms

bac92e5caa5f026f1449c7e0c79aa17b.jpg

bac92e5caa5f026f1449c7e0c79aa17b.jpg

79 ms

watch.js

watch.js

72 ms

ajax.php

ajax.php

389 ms

ya-share-cnt.html

ya-share-cnt.html

135 ms

ajax-loader.gif

ajax-loader.gif

11 ms

spinner-icon-14x14.gif

spinner-icon-14x14.gif

12 ms

loadingAnimation.gif

loadingAnimation.gif

24 ms

bx_loader.gif

bx_loader.gif

1812 ms

controls.png

controls.png

2447 ms

slick.woff

slick.woff

1112 ms

loader_nav21107839182_3.js

loader_nav21107839182_3.js

425 ms

fonts_cnt.c7a76efe.css

fonts_cnt.c7a76efe.css

1049 ms

lite.93f44416.css

lite.93f44416.css

759 ms

lang3_2.js

lang3_2.js

477 ms

c3d11fba.db7dbf71.js

c3d11fba.db7dbf71.js

630 ms

xdm.js

xdm.js

652 ms

base.ec2ae8ae.css

base.ec2ae8ae.css

680 ms

fql.query

fql.query

94 ms

share.php

share.php

412 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

525 ms

b-share_counter_large.png

b-share_counter_large.png

93 ms

hit

hit

143 ms

browsers.png

browsers.png

191 ms

upload.gif

upload.gif

79 ms

code.js

code.js

610 ms

counter

counter

122 ms

dyn-goal-config.js

dyn-goal-config.js

238 ms

tracker

tracker

121 ms

Accessibility Review

wotafaq.com accessibility score

79

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best Practices

wotafaq.com best practices score

58

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

SEO Factors

wotafaq.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wotafaq.com can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wotafaq.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

wotafaq.com

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