4.2 sec in total
489 ms
2.9 sec
775 ms
Click here to check amazing Fatal Game content for Russia. Otherwise, check out these important facts you probably never knew about fatalgame.com
Мир компьютерных игр - прохождение, коды к играм. С помощью FatalGame вы можете скачивать игры, читать обзоры и обсуждать новинки в кругу единомышленников
Visit fatalgame.comWe analyzed Fatalgame.com page load time and found that the first response time was 489 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fatalgame.com performance score
name
value
score
weighting
Value2.2 s
76/100
10%
Value5.8 s
15/100
25%
Value7.0 s
32/100
10%
Value820 ms
35/100
30%
Value0.001
100/100
15%
Value10.7 s
22/100
10%
489 ms
615 ms
399 ms
274 ms
415 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 48% of them (42 requests) were addressed to the original Fatalgame.com, 14% (12 requests) were made to Media.fatalgame.com and 7% (6 requests) were made to Media1.fatalgame.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Media.fatalgame.com.
Page size can be reduced by 328.4 kB (20%)
1.7 MB
1.3 MB
In fact, the total size of Fatalgame.com main page is 1.7 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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 59.0 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 59.0 kB or 79% of the original size.
Potential reduce by 92.2 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. Fatal Game images are well optimized though.
Potential reduce by 93.6 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 93.6 kB or 65% of the original size.
Potential reduce by 83.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. Fatalgame.com needs all CSS files to be minified and compressed as it can save up to 83.5 kB or 81% of the original size.
Number of requests can be reduced by 19 (23%)
83
64
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fatal Game. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
fatalgame.com
489 ms
www.fatalgame.com
615 ms
front.min.css
399 ms
adfox.asyn.code.ver3.js
274 ms
jquery.js
415 ms
swfobject.js
23 ms
hoverIntent.js
145 ms
superfish.js
284 ms
jquery_ui_effects_core-1.7.3.js
282 ms
main.js
281 ms
bbg.jpg
152 ms
analytics.js
22 ms
news_icon_preview_2688.jpg
787 ms
14234_icon.jpg
708 ms
14142_icon.jpg
686 ms
14125_icon.jpg
635 ms
13839_icon.png
636 ms
13586_icon.png
719 ms
13401_icon.png
714 ms
13213_icon.jpg
712 ms
game_icon_9018.png
824 ms
game_icon_9017.png
813 ms
priklyucheniya-treysi-na-lyzhah.jpg
641 ms
top100.cnt
293 ms
banner-88x31-rambler-brown2.gif
298 ms
news_icon_preview_2687.jpg
918 ms
news_icon_preview_2686.jpg
918 ms
game_icon_9020.png
913 ms
online_icon_258.png
926 ms
online_icon_462.png
920 ms
online_icon_58.jpg
906 ms
online_icon_461.png
1176 ms
game_icon_1400.png
1068 ms
online_icon_112.png
1195 ms
online_icon_102.gif
1400 ms
news_icon_preview_2685.jpg
1060 ms
perezapusti-solevye-bloki.jpg
635 ms
sokoban-2.jpg
443 ms
misticheskaya-ohota.jpg
442 ms
lara.jpg
843 ms
fgwot.png
315 ms
scorpion-subzero.jpg
283 ms
articles.png
195 ms
ogames.png
194 ms
comments.png
231 ms
newspaper.png
282 ms
13371_icon.jpg
707 ms
game_icon_9021.png
825 ms
game_icon_11.png
832 ms
game_icon_31.png
836 ms
game_icon_51.png
832 ms
game_icon_8.png
803 ms
14132_icon.jpg
808 ms
13302_icon.jpg
655 ms
game_icon_52.png
801 ms
game_icon_9019.png
772 ms
watch.js
2 ms
collect
29 ms
collect
168 ms
transparent.png
232 ms
date_bg_mainpage.jpg
300 ms
bg-l-n.jpg
365 ms
bg-m-n.jpg
365 ms
bg-r-n.jpg
365 ms
rect-top.png
386 ms
rect-bottom.png
451 ms
rect-head.png
509 ms
rect-head-long.png
510 ms
costplay-banner-text.png
640 ms
costplay-banner-btn.png
564 ms
costplay-banner-bg.jpg
1118 ms
ssbg.jpg
881 ms
sstl.png
1033 ms
sidebar-joniffer.png
921 ms
sidebar-text.png
734 ms
sidebar-btn.png
865 ms
sidebar-btn_hov.png
874 ms
sidebar-triss.jpg
972 ms
foo_arraows.png
992 ms
icons_foo_game.png
1037 ms
logoic.png
1072 ms
hit
258 ms
arrows-ffffff.png
1025 ms
witcher.gif
1157 ms
witcher.png
1300 ms
hit
149 ms
counter2
154 ms
fatalgame.com accessibility score
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
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fatalgame.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Page has valid source maps
fatalgame.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fatalgame.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 Fatalgame.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.
fatalgame.com
Open Graph description is not detected on the main page of Fatal Game. 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: