Tools & Wizards About Us

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

tourneykeeper.net

TourneyKeeper - Organize Warhammer 40K, Age of Sigmar, 9th age and more

Page Load Speed

2.9 sec in total

First Response

529 ms

Resources Loaded

2.2 sec

Page Rendered

145 ms

About Website

Visit tourneykeeper.net now to see the best up-to-date Tourney Keeper content for United States and also check out these interesting facts you probably never knew about tourneykeeper.net

TourneyKeeper is a free online tool for organizing tabletop tournaments and supports games such as Warhammer 40K, Age of Sigmar, 9th Age and Flames of War. TourneyKeeper is rock solid and free to use.

Visit tourneykeeper.net

Key Findings

We analyzed Tourneykeeper.net page load time and found that the first response time was 529 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

tourneykeeper.net performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value3,470 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

tourneykeeper.net

529 ms

all.css

77 ms

bootstrap.min.css

201 ms

mdb.min.css

414 ms

fileinput.min.css

58 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 66% of them (19 requests) were addressed to the original Tourneykeeper.net, 7% (2 requests) were made to Cdnjs.cloudflare.com and 7% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (779 ms) belongs to the original domain Tourneykeeper.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.2 kB (25%)

Content Size

739.5 kB

After Optimization

553.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tourneykeeper.net main page is 739.5 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. Javascripts take 471.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 85.2 kB

  • Original 103.2 kB
  • After minification 85.7 kB
  • After compression 18.0 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 17.5 kB, which is 17% 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 85.2 kB or 83% of the original size.

Image Optimization

-27%

Potential reduce by 4.4 kB

  • Original 15.9 kB
  • After minification 11.6 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. Obviously, Tourney Keeper needs image optimization as it can save up to 4.4 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 53.9 kB

  • Original 471.4 kB
  • After minification 471.4 kB
  • After compression 417.5 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 53.9 kB or 11% of the original size.

CSS Optimization

-29%

Potential reduce by 42.7 kB

  • Original 149.0 kB
  • After minification 148.9 kB
  • After compression 106.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. Tourneykeeper.net needs all CSS files to be minified and compressed as it can save up to 42.7 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (70%)

Requests Now

23

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

tourneykeeper.net accessibility score

77

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

tourneykeeper.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tourneykeeper.net SEO score

82

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 Tourneykeeper.net 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 Tourneykeeper.net 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 Tourney Keeper. 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: