57.4 sec in total
422 ms
51.6 sec
5.4 sec
Visit ogame.us now to see the best up-to-date Ogame content and also check out these interesting facts you probably never knew about ogame.us
OGame - The legendary game in the space! Discover the universe together with thousands of players.
Visit ogame.usWe analyzed Ogame.us page load time and found that the first response time was 422 ms and then it took 57 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
ogame.us performance score
422 ms
200 ms
449 ms
2442 ms
2431 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ogame.us, 23% (14 requests) were made to Gf2.geo.gfsrv.net and 18% (11 requests) were made to Gf1.geo.gfsrv.net. The less responsive or slowest element that took the longest time to load (10.2 sec) relates to the external source Ads-delivery.gameforge.com.
Page size can be reduced by 861.5 kB (53%)
1.6 MB
779.3 kB
In fact, the total size of Ogame.us main page is 1.6 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. 55% of websites need less resources to load. CSS take 557.5 kB which makes up the majority of the site volume.
Potential reduce by 84.4 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 17.3 kB, which is 17% 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 84.4 kB or 84% of the original size.
Potential reduce by 5.5 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. Ogame images are well optimized though.
Potential reduce by 315.4 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 315.4 kB or 60% of the original size.
Potential reduce by 456.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. Ogame.us needs all CSS files to be minified and compressed as it can save up to 456.2 kB or 82% of the original size.
Number of requests can be reduced by 28 (55%)
51
23
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ogame. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ogame.us
422 ms
us.ogame.gameforge.com
200 ms
us.ogame.gameforge.com
449 ms
eb9df5eeb514647c2061eb0deb26c6.css
2442 ms
8eb0908b8ad7243d2e6c1efb829232.css
2431 ms
f0e4dd4b8bdc69b6f412414bec8b07.css
2499 ms
50f811909977c19c9e2fd72217ee4c.js
2432 ms
799ec2f0eba935380926ea7756db23.js
2498 ms
d0437255213d95b42db39070285d8c.js
3521 ms
c6df02d71647441cce06ff575d0c98.js
3423 ms
d2534224c339dcf7ef94bac20b4976.js
2472 ms
0871fe298345f9eda8231ffb3ed207.js
3520 ms
60cd95d4ce5cb91a86861f433773d1.js
3421 ms
functions.js
3752 ms
fc4e8d71eddb92bfcf0adfff458150.js
2417 ms
0a5fa2929f5326fade793585415a22.gif
3011 ms
1817433e4a8d432a8d8ed25a4d6060.png
1844 ms
c98a4685de676300b80da072ab6ad7.png
1844 ms
atrk.js
1567 ms
ab65c4951f415dff50d74738c953b5.bg
1924 ms
113abb97b5fff99cb7d4d5019f04eb.gif
1167 ms
0f334111ba97c654b6e353f7168012.sprites
1422 ms
71fe874d78b03e38e06a3b471f6224.png
1260 ms
al.php
10180 ms
atrk.gif
433 ms
1867da5b5f8769b547bb91d88bb4f8.jpg
3518 ms
c732feb94125f1122741b89857eaf6.gif
2840 ms
76cbf0115f4559fb1d6f25e9819ecb.gif
2704 ms
lg.php
0 ms
f88cc2bd8efa2b7d232e50d56a1180.png
2703 ms
69677f0e9f1a6f9da264837a284c2d.png
2703 ms
freeName.php
4180 ms
freeName.php
4693 ms
Pb6Pgoxajqg
2830 ms
9ec040e9c5cc03591fdb3f4fb9a5f8.png
2597 ms
aef3bd3bdfb1d2be6d99ff39e7a394.png
2556 ms
f1c317aff2183c9b8b905bbbca9e8a.jpg
2413 ms
2c3d8b94dc095ab950a202f7089995.jpg
2476 ms
480120d537b7f69afcfda1356dd39e.gif
2315 ms
daeabdae9844ec3d61c235e5ee1a64.gif
2412 ms
de8b29a965ae085e8f3cdfcc63fb8e.gif
1736 ms
246742ee5fa2f53100ef6a5b823249.png
1847 ms
75032c7386f3b361cfbbac3fac191b.png
1736 ms
a0451be6b0bbf01d57849f6f2d67b8.jpg
1846 ms
e33da11dfe7f3e0c511125dbdd95ee.png
1845 ms
72a97f02af4493519c741f49f7180b.jpg
1845 ms
9ee28c83e3a3554b9d195e29309ebe.png
1846 ms
E6gg7P33.js
1439 ms
ga.js
1981 ms
1411 ms
GT7h68ox.js
1232 ms
simple
0 ms
Pb6Pgoxajqg
0 ms
__utm.gif
0 ms
collect
821 ms
www-player-vflMqr8uC.css
1546 ms
www-embed-player.js
134 ms
base.js
1401 ms
ga-audiences
5897 ms
id
2043 ms
YubHWiCUdycrt9r0pwxtCFMvWBBxMHmgtw0lFaZzSbY.js
1740 ms
ad_status.js
3019 ms
ogame.us SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ogame.us 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ogame.us 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.
ogame.us
Open Graph description is not detected on the main page of Ogame. 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: