Tools & Wizards About Us
oldages.de screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    84% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 90% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    92% of websites

oldages.de

Das historische Browsergame Old Ages - Schreibe die Geschichte neu und erlebe sagenhafte Kämpfe

Page Load Speed

3.5 sec in total

First Response

501 ms

Resources Loaded

2.8 sec

Page Rendered

238 ms

oldages.de screenshot

About Website

Click here to check amazing Old Ages content. Otherwise, check out these important facts you probably never knew about oldages.de

Browserspiel der Antike: Helden, Schätze & Mythen! Historische Abenteuer im Web-Browser? Erlebe Geschichte bei Old Ages!

Visit oldages.de

Key Findings

We analyzed Oldages.de page load time and found that the first response time was 501 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

oldages.de performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

oldages.de

501 ms

newsblock.js

105 ms

my_input.js

201 ms

wod_layout.js

203 ms

wod_standard.js

202 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 62% of them (26 requests) were addressed to the original Oldages.de, 29% (12 requests) were made to Fonts.wod-game.de and 10% (4 requests) were made to Vote.neise-games.de. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Vote.neise-games.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.3 kB (7%)

Content Size

439.2 kB

After Optimization

406.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oldages.de main page is 439.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. 25% of websites need less resources to load. Images take 351.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 15.2 kB

  • Original 19.3 kB
  • After minification 16.9 kB
  • After compression 4.2 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 2.5 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 15.2 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 9.2 kB

  • Original 351.5 kB
  • After minification 342.4 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. Old Ages images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 5.9 kB

  • Original 59.2 kB
  • After minification 59.2 kB
  • After compression 53.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-22%

Potential reduce by 2.0 kB

  • Original 9.1 kB
  • After minification 9.1 kB
  • After compression 7.1 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. Oldages.de needs all CSS files to be minified and compressed as it can save up to 2.0 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (52%)

Requests Now

29

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Old Ages. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

oldages.de

oldages.de

501 ms

newsblock.js

newsblock.js

105 ms

my_input.js

my_input.js

201 ms

wod_layout.js

wod_layout.js

203 ms

wod_standard.js

wod_standard.js

202 ms

wodtooltip.js

wodtooltip.js

203 ms

ajax_private.js

ajax_private.js

205 ms

ajax.js

ajax.js

205 ms

ajax.js

ajax.js

299 ms

ajax_controls.js

ajax_controls.js

301 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

507 ms

startpage.css

startpage.css

301 ms

layout.css

layout.css

311 ms

common.css

common.css

103 ms

ajax.css

ajax.css

101 ms

news.css

news.css

99 ms

news.css

news.css

111 ms

render

render

462 ms

lg.php

lg.php

421 ms

render

render

461 ms

render

render

461 ms

render

render

461 ms

render

render

460 ms

render

render

463 ms

render

render

463 ms

render

render

463 ms

render

render

463 ms

render

render

463 ms

render

render

462 ms

render

render

462 ms

background.jpg

background.jpg

144 ms

frontpage_1a.jpg

frontpage_1a.jpg

686 ms

lg.php

lg.php

1514 ms

lg.php

lg.php

417 ms

frontpage_3.jpg

frontpage_3.jpg

260 ms

block_olive_110.jpg

block_olive_110.jpg

259 ms

textbox.gif

textbox.gif

99 ms

button.gif

button.gif

101 ms

medium_green_button.png

medium_green_button.png

258 ms

frontpage_5.jpg

frontpage_5.jpg

300 ms

bottom.jpg

bottom.jpg

458 ms

ajs.php

ajs.php

350 ms

Accessibility Review

oldages.de accessibility score

96

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

oldages.de best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

oldages.de SEO score

97

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oldages.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Oldages.de 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

oldages.de

Open Graph description is not detected on the main page of Old Ages. 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: