3.5 sec in total
475 ms
2.9 sec
115 ms
Click here to check amazing Eyesthehorrorgame content for Russia. Otherwise, check out these important facts you probably never knew about eyesthehorrorgame.com
Visit eyesthehorrorgame.comWe analyzed Eyesthehorrorgame.com page load time and found that the first response time was 475 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
eyesthehorrorgame.com performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value2.1 s
95/100
25%
Value1.1 s
100/100
10%
Value10 ms
100/100
30%
Value0.274
44/100
15%
Value1.1 s
100/100
10%
475 ms
19 ms
25 ms
30 ms
150 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Eyesthehorrorgame.com, 13% (14 requests) were made to Apis.google.com and 9% (10 requests) were made to Static.tumblr.com. The less responsive or slowest element that took the longest time to load (751 ms) relates to the external source Btn.createsend1.com.
Page size can be reduced by 1.3 MB (60%)
2.2 MB
865.7 kB
In fact, the total size of Eyesthehorrorgame.com main page is 2.2 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. 75% 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. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 119.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 119.3 kB or 80% of the original size.
Potential reduce by 93.0 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. Obviously, Eyesthehorrorgame needs image optimization as it can save up to 93.0 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 809.1 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 809.1 kB or 65% of the original size.
Potential reduce by 263.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. Eyesthehorrorgame.com needs all CSS files to be minified and compressed as it can save up to 263.3 kB or 82% of the original size.
Number of requests can be reduced by 54 (54%)
100
46
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyesthehorrorgame. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
eyesthehorrorgame.com
475 ms
pre_tumblelog.js
19 ms
theme.css
25 ms
main.js
30 ms
shCore.css
150 ms
shThemeEclipse.css
147 ms
shCore.js
146 ms
shBrushBash.js
149 ms
shBrushPlain.js
150 ms
shBrushPython.js
150 ms
tumblelog_post_message_queue.js
20 ms
stylesheet.css
19 ms
index.js
53 ms
shThemeEclipse.css
703 ms
shCore.js
549 ms
shBrushBash.js
560 ms
shCore.css
699 ms
shBrushPython.js
738 ms
shBrushPlain.js
545 ms
tumblr-actions-1.png
28 ms
badge_appstore-lrg.png
155 ms
en_generic_rgb_wo_60.png
320 ms
anonymous_avatar_16.gif
50 ms
avatar_37bf0c0b9932_16.png
52 ms
horizontal-arrows-1.png
51 ms
tumblr_static_icon512.png
50 ms
social-networks-1.png
151 ms
post-types-1.png
149 ms
sb.min.js
164 ms
4Qy_HtfWiPE
214 ms
false
159 ms
tumblr-meta-1.png
127 ms
tumblr-actions-2.png
128 ms
horizontal-arrows-2.png
130 ms
aZan2a8RQj4jDQpWzlQuAQ.js
439 ms
impixu
376 ms
count.js
87 ms
all.js
48 ms
pinit.js
48 ms
plusone.js
85 ms
widgets.js
288 ms
impixu
284 ms
analytics.html
185 ms
login_check.html
17 ms
ga.js
60 ms
tumblr_mkzzsxwW7x1s6slkfo1_500.png
169 ms
tumblr_mkzzsxwW7x1s6slkfo4_250.png
151 ms
tumblr_mkzzsxwW7x1s6slkfo7_250.png
249 ms
tumblr_mkzzsxwW7x1s6slkfo8_250.png
295 ms
tumblr_mkzzsxwW7x1s6slkfo3_250.png
305 ms
tumblr_mkzzsxwW7x1s6slkfo2_250.png
295 ms
tumblr_mkzzsxwW7x1s6slkfo9_250.png
296 ms
tumblr_mkzzsxwW7x1s6slkfo5_250.png
159 ms
subscribe
47 ms
webfont.js
134 ms
363 ms
subscribe-button.min.css
90 ms
subscribe-button-modal.min.css
91 ms
subscribebutton.noncc.min.js
138 ms
xd_arbiter.php
95 ms
xd_arbiter.php
206 ms
www-embed-player-vflfNyN_r.css
274 ms
www-embed-player.js
458 ms
base.js
627 ms
pinit_main.js
110 ms
count-data.js
92 ms
cb=gapi.loaded_0
257 ms
cb=gapi.loaded_1
350 ms
fastbutton
475 ms
fastbutton
465 ms
fastbutton
476 ms
fastbutton
473 ms
fastbutton
465 ms
fastbutton
471 ms
__utm.gif
53 ms
rapid-3.36.js
245 ms
rapidworker-1.2.js
249 ms
17C5A78721A98688.json
751 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
507 ms
feedback-tab.png
99 ms
ga.js
262 ms
analytics.js
180 ms
cs.js
256 ms
yql
541 ms
tab-right-dark-da2413549ce324fc421ae86a0e5881ee.png
112 ms
postmessageRelay
329 ms
rs=AGLTcCNFg9Lxr6A_1qJE1FafaQPPaU_lFQ
55 ms
cb=gapi.loaded_0
192 ms
cb=gapi.loaded_1
193 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
230 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
107 ms
ad_status.js
98 ms
3193398744-postmessagerelay.js
82 ms
rpc:shindig_random.js
62 ms
__utm.gif
43 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
34 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
34 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
66 ms
cb=gapi.loaded_0
9 ms
cedexis.radar.js
63 ms
track.js
169 ms
button.png
13 ms
like.php
75 ms
like.php
91 ms
qeKvIRsJabD.js
44 ms
LVx-xkvaJ0b.png
41 ms
like.php
135 ms
like.php
152 ms
like.php
157 ms
like.php
142 ms
jot.html
37 ms
eyesthehorrorgame.com accessibility score
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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
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
<html> element does not have a [lang] attribute
eyesthehorrorgame.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
eyesthehorrorgame.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyesthehorrorgame.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Eyesthehorrorgame.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.
eyesthehorrorgame.com
Open Graph description is not detected on the main page of Eyesthehorrorgame. 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: