Report Summary

  • 7

    Performance

    Renders faster than
    30% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 83

    SEO

    Google-friendlier than
    54% of websites

Page Load Speed

48.2 sec in total

First Response

602 ms

Resources Loaded

41.4 sec

Page Rendered

6.2 sec

ogame.org screenshot

About Website

Visit ogame.org now to see the best up-to-date Ogame content for United States and also check out these interesting facts you probably never knew about ogame.org

OGame - The legendary game in the space! Discover the universe together with thousands of players.

Visit ogame.org

Key Findings

We analyzed Ogame.org page load time and found that the first response time was 602 ms and then it took 47.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ogame.org performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value5,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.28

43/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

ogame.org

602 ms

en.ogame.gameforge.com

335 ms

en.ogame.gameforge.com

895 ms

eb9df5eeb514647c2061eb0deb26c6.css

2844 ms

8eb0908b8ad7243d2e6c1efb829232.css

2843 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ogame.org, 22% (14 requests) were made to Gf2.geo.gfsrv.net and 19% (12 requests) were made to Gf3.geo.gfsrv.net. The less responsive or slowest element that took the longest time to load (20.6 sec) relates to the external source S143-en.ogame.gameforge.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (46%)

Content Size

2.3 MB

After Optimization

1.3 MB

In fact, the total size of Ogame.org main page is 2.3 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. 60% of websites need less resources to load. Images take 912.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 99.2 kB

  • Original 116.6 kB
  • After minification 91.9 kB
  • After compression 17.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 24.6 kB, which is 21% 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 99.2 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 45.8 kB

  • Original 912.4 kB
  • After minification 866.6 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

-63%

Potential reduce by 458.2 kB

  • Original 728.7 kB
  • After minification 728.5 kB
  • After compression 270.5 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 458.2 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 476.4 kB

  • Original 580.9 kB
  • After minification 575.5 kB
  • After compression 104.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. Ogame.org needs all CSS files to be minified and compressed as it can save up to 476.4 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

52

After Optimization

24

The browser has sent 52 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.

Accessibility Review

ogame.org accessibility score

86

Accessibility Issues

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

ogame.org 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

High

Missing source maps for large first-party JavaScript

SEO Factors

ogame.org SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    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.org 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.org 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: