Tools & Wizards About Us
legendkeeper.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

legendkeeper.com

LegendKeeper - Worldbuilding app with maps, wiki, and whiteboards

Page Load Speed

2 sec in total

First Response

100 ms

Resources Loaded

1.1 sec

Page Rendered

788 ms

legendkeeper.com screenshot

About Website

Click here to check amazing Legend Keeper content for United States. Otherwise, check out these important facts you probably never knew about legendkeeper.com

Build better worlds faster for RPG campaigns and stories. Free-form wiki, integrated maps, collaborative whiteboards, and our thriving community make it easy.

Visit legendkeeper.com

Key Findings

We analyzed Legendkeeper.com page load time and found that the first response time was 100 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

legendkeeper.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value1,540 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

legendkeeper.com

100 ms

legendkeeper.com

86 ms

www.legendkeeper.com

166 ms

7ba9f0a9c9d37d29.css

93 ms

4f9b0bbb3e8fa4ea.css

60 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 98% of them (48 requests) were addressed to the original Legendkeeper.com, 2% (1 request) were made to Rsms.me. The less responsive or slowest element that took the longest time to load (630 ms) belongs to the original domain Legendkeeper.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.4 kB (3%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images

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

HTML Optimization

-80%

Potential reduce by 38.2 kB

  • Original 48.0 kB
  • After minification 47.7 kB
  • After compression 9.8 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 38.2 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 12.2 kB

  • Original 1.6 MB
  • After minification 1.6 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. Legend Keeper images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 20 (43%)

Requests Now

46

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

legendkeeper.com

legendkeeper.com

100 ms

legendkeeper.com

legendkeeper.com

86 ms

www.legendkeeper.com

www.legendkeeper.com

166 ms

7ba9f0a9c9d37d29.css

7ba9f0a9c9d37d29.css

93 ms

4f9b0bbb3e8fa4ea.css

4f9b0bbb3e8fa4ea.css

60 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

104 ms

8000.53efcea50689e12e.js

8000.53efcea50689e12e.js

99 ms

webpack-470cf14393175998.js

webpack-470cf14393175998.js

83 ms

framework-17f4e32718570ada.js

framework-17f4e32718570ada.js

159 ms

main-8df4b4668cd772f1.js

main-8df4b4668cd772f1.js

200 ms

_app-1eb92271eb93b3fe.js

_app-1eb92271eb93b3fe.js

158 ms

79598cfd-0fe44c90814f3ad1.js

79598cfd-0fe44c90814f3ad1.js

172 ms

68234bd8-df353ba1327ae129.js

68234bd8-df353ba1327ae129.js

229 ms

a6380923-6944e5973cd9bbb5.js

a6380923-6944e5973cd9bbb5.js

200 ms

5801d45a-1da92782ba8c2d9e.js

5801d45a-1da92782ba8c2d9e.js

245 ms

8248-0f0585f7bee8c648.js

8248-0f0585f7bee8c648.js

306 ms

1515-385ed17de6913f1d.js

1515-385ed17de6913f1d.js

307 ms

9385-3efa5dd96ee8a452.js

9385-3efa5dd96ee8a452.js

306 ms

8391-2be0acddd2d7360f.js

8391-2be0acddd2d7360f.js

305 ms

7148-1c43fc510440fa5e.js

7148-1c43fc510440fa5e.js

357 ms

1996-f108bcc030775005.js

1996-f108bcc030775005.js

328 ms

4922-fb3afb6a8ded4d1a.js

4922-fb3afb6a8ded4d1a.js

357 ms

8580-c9f97590b6a7bacc.js

8580-c9f97590b6a7bacc.js

360 ms

index-34e16a6b862fb5cd.js

index-34e16a6b862fb5cd.js

402 ms

_buildManifest.js

_buildManifest.js

379 ms

_ssgManifest.js

_ssgManifest.js

374 ms

422 ms

427 ms

405 ms

462 ms

444 ms

479 ms

545 ms

511 ms

537 ms

492 ms

571 ms

630 ms

604 ms

525 ms

551 ms

inter.css

inter.css

41 ms

572 ms

571 ms

543 ms

562 ms

bg-map-dark.webp

bg-map-dark.webp

573 ms

bg02.webp

bg02.webp

560 ms

bg03.webp

bg03.webp

562 ms

Accessibility Review

legendkeeper.com accessibility score

90

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.

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

ARIA IDs 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

Best Practices

legendkeeper.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

legendkeeper.com SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Legendkeeper.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Legendkeeper.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

legendkeeper.com

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