Report Summary

  • 4

    Performance

    Renders faster than
    29% 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

17 sec in total

First Response

433 ms

Resources Loaded

16.2 sec

Page Rendered

325 ms

ogame.ru screenshot

About Website

Click here to check amazing Ogame content. Otherwise, check out these important facts you probably never knew about ogame.ru

ОГейм - легендарная космическая стратегия! Откройте вселенную вместе с тысячами игроков!

Visit ogame.ru

Key Findings

We analyzed Ogame.ru page load time and found that the first response time was 433 ms and then it took 16.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

ogame.ru performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value5,080 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.504

16/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

ogame.ru

433 ms

ru.ogame.gameforge.com

220 ms

ru.ogame.gameforge.com

539 ms

eb9df5eeb514647c2061eb0deb26c6.css

2458 ms

2269ee6a4e63878f2f363e719f8eb1.css

2433 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ogame.ru, 22% (14 requests) were made to Gf2.geo.gfsrv.net and 21% (13 requests) were made to Gf1.geo.gfsrv.net. The less responsive or slowest element that took the longest time to load (9.4 sec) relates to the external source Ads-delivery.gameforge.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 562.4 kB (46%)

Content Size

1.2 MB

After Optimization

656.3 kB

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

HTML Optimization

-84%

Potential reduce by 86.3 kB

  • Original 103.1 kB
  • After minification 90.2 kB
  • After compression 16.8 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 12.9 kB, which is 13% 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 86.3 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 5.5 kB

  • Original 450.3 kB
  • After minification 444.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

-63%

Potential reduce by 248.3 kB

  • Original 394.0 kB
  • After minification 393.9 kB
  • After compression 145.7 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 248.3 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 222.4 kB

  • Original 271.4 kB
  • After minification 271.2 kB
  • After compression 48.9 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.ru needs all CSS files to be minified and compressed as it can save up to 222.4 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

26

The browser has sent 57 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.ru 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.ru 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.ru 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.ru 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.ru 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: