Tools & Wizards About Us
exe2.net screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

exe2.net

exe2.net - Esports Blog

Page Load Speed

8.4 sec in total

First Response

2.5 sec

Resources Loaded

5 sec

Page Rendered

929 ms

exe2.net screenshot

About Website

Click here to check amazing Exe 2 content for Russia. Otherwise, check out these important facts you probably never knew about exe2.net

Esports Blog

Visit exe2.net

Key Findings

We analyzed Exe2.net page load time and found that the first response time was 2.5 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

exe2.net performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

exe2.net

2482 ms

style.css

129 ms

engine.css

255 ms

openapi.js

389 ms

menu.js

286 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 39% of them (14 requests) were addressed to the original Exe2.net, 11% (4 requests) were made to S018.radikal.ru and 11% (4 requests) were made to Acint.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source I73.fastpic.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.2 kB (41%)

Content Size

352.5 kB

After Optimization

208.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Exe2.net main page is 352.5 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. 30% of websites need less resources to load. Images take 184.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 46.3 kB

  • Original 56.5 kB
  • After minification 54.3 kB
  • After compression 10.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 46.3 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 14.8 kB

  • Original 184.5 kB
  • After minification 169.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. Exe 2 images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 72.5 kB

  • Original 98.8 kB
  • After minification 78.9 kB
  • After compression 26.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 72.5 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 10.6 kB

  • Original 12.7 kB
  • After minification 8.5 kB
  • After compression 2.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. Exe2.net needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (39%)

Requests Now

33

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

exe2.net

exe2.net

2482 ms

style.css

style.css

129 ms

engine.css

engine.css

255 ms

openapi.js

openapi.js

389 ms

menu.js

menu.js

286 ms

dle_ajax.js

dle_ajax.js

259 ms

js_edit.js

js_edit.js

260 ms

8716043537af.jpg

8716043537af.jpg

938 ms

1c13c12b6f99.jpg

1c13c12b6f99.jpg

1006 ms

124d4209ad86.jpg

124d4209ad86.jpg

1074 ms

195c8c3b3d7b5bcb7947282ec624d663.jpeg

195c8c3b3d7b5bcb7947282ec624d663.jpeg

2518 ms

cacdab988504.jpg

cacdab988504.jpg

1099 ms

7de7ab856190.jpg

7de7ab856190.jpg

1079 ms

b51fe1fec102.jpg

b51fe1fec102.jpg

1104 ms

loading.gif

loading.gif

230 ms

lupa.gif

lupa.gif

250 ms

send.png

send.png

348 ms

blue_rus.gif

blue_rus.gif

356 ms

ce1cad14b008.jpg

ce1cad14b008.jpg

1147 ms

66598ddb3aeb.jpg

66598ddb3aeb.jpg

1046 ms

966f5d8c42b4.jpg

966f5d8c42b4.jpg

1053 ms

all.js

all.js

15 ms

bg_1.jpg

bg_1.jpg

182 ms

logo.jpg

logo.jpg

568 ms

titlebas1.png

titlebas1.png

216 ms

aci.js

aci.js

216 ms

149 ms

title_top.png

title_top.png

180 ms

hit

hit

310 ms

xd_arbiter.php

xd_arbiter.php

71 ms

xd_arbiter.php

xd_arbiter.php

87 ms

94 ms

185 ms

hit

hit

135 ms

275 ms

match

match

193 ms

Accessibility Review

exe2.net accessibility score

100

Accessibility Issues

Best Practices

exe2.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

exe2.net SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exe2.net can be misinterpreted by Google and other search engines. Our service has detected that English 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 Exe2.net 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

exe2.net

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