Tools & Wizards About Us
grandages.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

grandages.com

Grand Ages: Medieval | Kalypso US

Page Load Speed

3.9 sec in total

First Response

652 ms

Resources Loaded

2.9 sec

Page Rendered

342 ms

grandages.com screenshot

About Website

Click here to check amazing Grand Ages content for United States. Otherwise, check out these important facts you probably never knew about grandages.com

Lead your empire towards flourishing prosperity and expand your power through clever trade, diplomacy and conquest in Grand Ages: Medieval!

Visit grandages.com

Key Findings

We analyzed Grandages.com page load time and found that the first response time was 652 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

grandages.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value20.8 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.548

13/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

652 ms

analytics.js

18 ms

fbevents.js

138 ms

wp-emoji-release.min.js

145 ms

nivo-lightbox.css

202 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 73% of them (49 requests) were addressed to the original Grandages.com, 9% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (830 ms) belongs to the original domain Grandages.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 673.3 kB (31%)

Content Size

2.1 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Grandages.com main page is 2.1 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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 12.6 kB

  • Original 17.7 kB
  • After minification 16.4 kB
  • After compression 5.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 12.6 kB or 71% of the original size.

Image Optimization

-2%

Potential reduce by 23.7 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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. Grand Ages images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 299.3 kB

  • Original 477.1 kB
  • After minification 470.7 kB
  • After compression 177.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 299.3 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 337.7 kB

  • Original 411.0 kB
  • After minification 375.5 kB
  • After compression 73.3 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. Grandages.com needs all CSS files to be minified and compressed as it can save up to 337.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (40%)

Requests Now

60

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grand 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 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

652 ms

analytics.js

analytics.js

18 ms

fbevents.js

fbevents.js

138 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

145 ms

nivo-lightbox.css

nivo-lightbox.css

202 ms

default.css

default.css

203 ms

css

css

23 ms

genericons.css

genericons.css

305 ms

style.css

style.css

507 ms

jquery.js

jquery.js

521 ms

jquery-migrate.min.js

jquery-migrate.min.js

247 ms

nivo-lightbox.min.js

nivo-lightbox.min.js

303 ms

front.js

front.js

306 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

555 ms

modernizr.custom.js

modernizr.custom.js

405 ms

default.css

default.css

406 ms

component.css

component.css

408 ms

classie.js

classie.js

504 ms

modalEffects.js

modalEffects.js

515 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

516 ms

functions.js

functions.js

614 ms

collect

collect

15 ms

24 ms

css

css

15 ms

bg-tile1.jpg

bg-tile1.jpg

296 ms

gam_gamenavi.jpg

gam_gamenavi.jpg

111 ms

ddb.jpg

ddb.jpg

296 ms

fag_button.png

fag_button.png

119 ms

footer_logos.png

footer_logos.png

119 ms

de.png

de.png

126 ms

uk.png

uk.png

289 ms

us_mo.png

us_mo.png

289 ms

facebook.png

facebook.png

290 ms

twitter.png

twitter.png

290 ms

youtube.png

youtube.png

320 ms

gam_header.jpg

gam_header.jpg

616 ms

gam_subnavi.jpg

gam_subnavi.jpg

427 ms

newsletter.png

newsletter.png

327 ms

news.png

news.png

327 ms

trenn.png

trenn.png

328 ms

info.png

info.png

414 ms

media.png

media.png

432 ms

forum.png

forum.png

429 ms

buynow.png

buynow.png

430 ms

6PKvCY6Lirs

6PKvCY6Lirs

100 ms

gam_leadpost.jpg

gam_leadpost.jpg

617 ms

title_underline.png

title_underline.png

518 ms

gam.png

gam.png

519 ms

preorder_us.jpg

preorder_us.jpg

660 ms

gam_repeat.jpg

gam_repeat.jpg

633 ms

trailerrahmen.jpg

trailerrahmen.jpg

620 ms

gam_footer.jpg

gam_footer.jpg

830 ms

trenner.png

trenner.png

707 ms

support.png

support.png

717 ms

imprint.png

imprint.png

721 ms

ppolicy.png

ppolicy.png

737 ms

fVu1p3782bqS2z-CaJvp9i3USBnSvpkopQaUR-2r7iU.ttf

fVu1p3782bqS2z-CaJvp9i3USBnSvpkopQaUR-2r7iU.ttf

49 ms

lJAvZoKA5NttpPc9yc6lPbOLyRJkM5aLlPlkJMOAyH0.ttf

lJAvZoKA5NttpPc9yc6lPbOLyRJkM5aLlPlkJMOAyH0.ttf

55 ms

PIbvSEyHEdL91QLOQRnZ19qQynqKV_9Plp7mupa0S4g.ttf

PIbvSEyHEdL91QLOQRnZ19qQynqKV_9Plp7mupa0S4g.ttf

63 ms

erE3KsIWUumgD1j_Ca-V-6CWcynf_cDxXwCLxiixG1c.ttf

erE3KsIWUumgD1j_Ca-V-6CWcynf_cDxXwCLxiixG1c.ttf

61 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

25 ms

www-embed-player.js

www-embed-player.js

46 ms

base.js

base.js

74 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

51 ms

ad_status.js

ad_status.js

51 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

60 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

60 ms

Accessibility Review

grandages.com accessibility score

74

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

grandages.com 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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

grandages.com 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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

grandages.com

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