Tools & Wizards About Us
d20criticalhit.com screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

d20criticalhit.com

A Critical Hit and Fumble Generator for Pathfinder and d20/3.0/3.5

Page Load Speed

2.3 sec in total

First Response

182 ms

Resources Loaded

1.9 sec

Page Rendered

162 ms

d20criticalhit.com screenshot

About Website

Click here to check amazing D20 Critical Hit content. Otherwise, check out these important facts you probably never knew about d20criticalhit.com

A Critical Hit and Fumble Generator for Pathfinder and d20/3.0/3.5

Visit d20criticalhit.com

Key Findings

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

Performance Metrics

d20criticalhit.com performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

d20criticalhit.com

182 ms

d20criticalhit.com

293 ms

critTool3.css

72 ms

imageData.js

143 ms

critTool3.js

213 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that all of those requests were addressed to D20criticalhit.com and no external sources were called. The less responsive or slowest element that took the longest time to load (919 ms) belongs to the original domain D20criticalhit.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.0 MB (86%)

Content Size

8.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 68.9 kB

  • Original 78.1 kB
  • After minification 66.0 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 12.1 kB, which is 15% 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 68.9 kB or 88% of the original size.

Image Optimization

-86%

Potential reduce by 6.9 MB

  • Original 8.0 MB
  • After minification 1.1 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. Obviously, D20 Critical Hit needs image optimization as it can save up to 6.9 MB or 86% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 2.7 kB

  • Original 6.4 kB
  • After minification 6.4 kB
  • After compression 3.8 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 2.7 kB or 42% of the original size.

CSS Optimization

-30%

Potential reduce by 734 B

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 1.7 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. D20criticalhit.com needs all CSS files to be minified and compressed as it can save up to 734 B or 30% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

65

After Optimization

65

  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of D20 Critical Hit. According to our analytics all requests are already optimized.

Network Requests Diagram

d20criticalhit.com

d20criticalhit.com

182 ms

d20criticalhit.com

d20criticalhit.com

293 ms

critTool3.css

critTool3.css

72 ms

imageData.js

imageData.js

143 ms

critTool3.js

critTool3.js

213 ms

BackgroundFlashColorReduced.jpg

BackgroundFlashColorReduced.jpg

279 ms

TopBar_Reduced.png

TopBar_Reduced.png

351 ms

HelpButton.png

HelpButton.png

280 ms

criticalSmashButton_Reduced.png

criticalSmashButton_Reduced.png

352 ms

smashButton_Reduced.png

smashButton_Reduced.png

353 ms

criticalHitButton_Reduced.png

criticalHitButton_Reduced.png

354 ms

stumbleButton_Reduced.png

stumbleButton_Reduced.png

349 ms

fumbleButton_Reduced.png

fumbleButton_Reduced.png

417 ms

catastropheButton_Reduced.png

catastropheButton_Reduced.png

421 ms

GoodLuck_CleanReduced.jpg

GoodLuck_CleanReduced.jpg

493 ms

BadLuck_CleanReduced.jpg

BadLuck_CleanReduced.jpg

629 ms

HelpScroll.png

HelpScroll.png

775 ms

Dagger.png

Dagger.png

495 ms

ShortSword.png

ShortSword.png

487 ms

BigSword.png

BigSword.png

490 ms

ConanSword.png

ConanSword.png

557 ms

Hatchet.png

Hatchet.png

561 ms

PickAxe.png

PickAxe.png

562 ms

BiBladeAxe.png

BiBladeAxe.png

636 ms

BattleAxe.png

BattleAxe.png

628 ms

Scythe.png

Scythe.png

634 ms

WoodenShield.png

WoodenShield.png

635 ms

SnakeShield.png

SnakeShield.png

700 ms

DragonShield.png

DragonShield.png

768 ms

HeaterShield.png

HeaterShield.png

707 ms

GoodLuckClover.png

GoodLuckClover.png

706 ms

Bananapeel.png

Bananapeel.png

778 ms

BlackCat.png

BlackCat.png

771 ms

StormCloud.png

StormCloud.png

779 ms

DiceView1.png

DiceView1.png

779 ms

DiceView2.png

DiceView2.png

840 ms

DiceView3.png

DiceView3.png

841 ms

DiceView4.png

DiceView4.png

845 ms

DiceView5.png

DiceView5.png

919 ms

DiceView6.png

DiceView6.png

849 ms

DiceView7.png

DiceView7.png

852 ms

DiceView8.png

DiceView8.png

639 ms

DiceView9.png

DiceView9.png

637 ms

DiceView10.png

DiceView10.png

577 ms

DiceView11.png

DiceView11.png

575 ms

DiceView12.png

DiceView12.png

579 ms

DiceView13.png

DiceView13.png

638 ms

DiceView14.png

DiceView14.png

636 ms

DiceView15.png

DiceView15.png

583 ms

DiceView16.png

DiceView16.png

575 ms

DiceView17.png

DiceView17.png

510 ms

DiceView18.png

DiceView18.png

511 ms

DiceView19.png

DiceView19.png

569 ms

DiceView20.png

DiceView20.png

566 ms

dieRollAnimation1.gif

dieRollAnimation1.gif

648 ms

NumberPlus.png

NumberPlus.png

505 ms

NumberMinus.png

NumberMinus.png

508 ms

Number0.png

Number0.png

443 ms

Number1.png

Number1.png

503 ms

Number2.png

Number2.png

495 ms

Number3.png

Number3.png

502 ms

Number4.png

Number4.png

505 ms

Number5.png

Number5.png

440 ms

Number6.png

Number6.png

494 ms

Number7.png

Number7.png

492 ms

Number8.png

Number8.png

440 ms

Number9.png

Number9.png

439 ms

Accessibility Review

d20criticalhit.com accessibility score

57

Accessibility Issues

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

Image elements do not have [alt] attributes

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.

Best Practices

d20criticalhit.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

SEO Factors

d20criticalhit.com SEO score

62

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 D20criticalhit.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 D20criticalhit.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

d20criticalhit.com

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