Report Summary

  • 14

    Performance

    Renders faster than
    33% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 64% 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

5.3 sec in total

First Response

255 ms

Resources Loaded

4.1 sec

Page Rendered

975 ms

gladiatus.cz screenshot

About Website

Click here to check amazing Gladiatus content. Otherwise, check out these important facts you probably never knew about gladiatus.cz

Visit gladiatus.cz

Key Findings

We analyzed Gladiatus.cz page load time and found that the first response time was 255 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

gladiatus.cz performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.257

48/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

gladiatus.cz

255 ms

296 ms

layout.css

189 ms

start.css

193 ms

game.css

291 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gladiatus.cz, 66% (44 requests) were made to Cz.gladiatus.gameforge.com and 7% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Gf3.geo.gfsrv.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 861.9 kB (45%)

Content Size

1.9 MB

After Optimization

1.1 MB

In fact, the total size of Gladiatus.cz main page is 1.9 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. 45% of websites need less resources to load. Images take 850.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 83.1 kB

  • Original 97.9 kB
  • After minification 79.6 kB
  • After compression 14.9 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 18.3 kB, which is 19% 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 83.1 kB or 85% of the original size.

Image Optimization

-9%

Potential reduce by 72.3 kB

  • Original 850.5 kB
  • After minification 778.2 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. Gladiatus images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 562.0 kB

  • Original 794.4 kB
  • After minification 760.1 kB
  • After compression 232.3 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 562.0 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 144.5 kB

  • Original 171.3 kB
  • After minification 136.3 kB
  • After compression 26.8 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. Gladiatus.cz needs all CSS files to be minified and compressed as it can save up to 144.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (56%)

Requests Now

63

After Optimization

28

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

Accessibility Review

gladiatus.cz accessibility score

83

Accessibility Issues

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.

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

gladiatus.cz 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

gladiatus.cz 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 Gladiatus.cz 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 Gladiatus.cz 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 Gladiatus. 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: