Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

57.4 sec in total

First Response

422 ms

Resources Loaded

51.6 sec

Page Rendered

5.4 sec

ogame.us screenshot

About Website

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.us

Key Findings

We 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.

Performance Metrics

ogame.us performance score

0

Network Requests Diagram

ogame.us

422 ms

us.ogame.gameforge.com

200 ms

us.ogame.gameforge.com

449 ms

eb9df5eeb514647c2061eb0deb26c6.css

2442 ms

8eb0908b8ad7243d2e6c1efb829232.css

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 Optimization Overview & Recommendations

Page size can be reduced by 861.5 kB (53%)

Content Size

1.6 MB

After Optimization

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.

HTML Optimization

-84%

Potential reduce by 84.4 kB

  • Original 100.8 kB
  • After minification 83.5 kB
  • After compression 16.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. 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.

Image Optimization

-1%

Potential reduce by 5.5 kB

  • Original 460.2 kB
  • After minification 454.8 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.

JavaScript Optimization

-60%

Potential reduce by 315.4 kB

  • Original 522.3 kB
  • After minification 522.2 kB
  • After compression 206.9 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.

CSS Optimization

-82%

Potential reduce by 456.2 kB

  • Original 557.5 kB
  • After minification 557.1 kB
  • After compression 101.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.

Requests Breakdown

Number of requests can be reduced by 28 (55%)

Requests Now

51

After Optimization

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.

SEO Factors

ogame.us SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: