Report Summary

  • 7

    Performance

    Renders faster than
    21% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 63% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

Page Load Speed

12 sec in total

First Response

219 ms

Resources Loaded

11.3 sec

Page Rendered

471 ms

ogame.com.es screenshot

About Website

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

OGame - ¡El juego legendario en el espacio! Descubre un universo junto con miles de jugadores.

Visit ogame.com.es

Key Findings

We analyzed Ogame.com.es page load time and found that the first response time was 219 ms and then it took 11.7 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.com.es performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value3,200 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.306

38/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

ogame.com.es

219 ms

es.ogame.gameforge.com

265 ms

es.ogame.gameforge.com

511 ms

eb9df5eeb514647c2061eb0deb26c6.css

4629 ms

2269ee6a4e63878f2f363e719f8eb1.css

4068 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ogame.com.es, 16% (6 requests) were made to Gf2.geo.gfsrv.net and 16% (6 requests) were made to Gf3.geo.gfsrv.net. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Gf2.geo.gfsrv.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 366.9 kB (75%)

Content Size

490.2 kB

After Optimization

123.3 kB

In fact, the total size of Ogame.com.es main page is 490.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. CSS take 244.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 86.6 kB

  • Original 103.9 kB
  • After minification 88.6 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 15.3 kB, which is 15% 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.6 kB or 83% of the original size.

JavaScript Optimization

-55%

Potential reduce by 78.1 kB

  • Original 141.4 kB
  • After minification 141.3 kB
  • After compression 63.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 78.1 kB or 55% of the original size.

CSS Optimization

-83%

Potential reduce by 202.2 kB

  • Original 244.8 kB
  • After minification 244.7 kB
  • After compression 42.6 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.com.es needs all CSS files to be minified and compressed as it can save up to 202.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (53%)

Requests Now

15

After Optimization

7

The browser has sent 15 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 9 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

ogame.com.es 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.com.es 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.com.es 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.com.es 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.com.es 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: