Tools & Wizards About Us
dfdoom.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

dfdoom.com

Dragonfly's Doomworks - The Home of Creative Custom Doom Content

Page Load Speed

5.1 sec in total

First Response

299 ms

Resources Loaded

4.3 sec

Page Rendered

477 ms

dfdoom.com screenshot

About Website

Welcome to dfdoom.com homepage info - get ready to check Df Doom best content right away, or after learning these important things about dfdoom.com

Welcome to Dragonfly's Doomworks! I’ve been avidly making custom Doom content since 2005, from maps and mods to tutorials and music!

Visit dfdoom.com

Key Findings

We analyzed Dfdoom.com page load time and found that the first response time was 299 ms and then it took 4.8 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

dfdoom.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

dfdoom.com

299 ms

dfdoom.com

384 ms

www.dfdoom.com

1892 ms

extra.min.css

188 ms

styles.css

281 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 68% of them (52 requests) were addressed to the original Dfdoom.com, 17% (13 requests) were made to Cdn.dfdoom.com and 12% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Dfdoom.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 209.8 kB (14%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dfdoom.com main page is 1.5 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. 55% of websites need less resources to load. Images take 984.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 197.5 kB

  • Original 234.0 kB
  • After minification 230.8 kB
  • After compression 36.4 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 197.5 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 2.7 kB

  • Original 984.7 kB
  • After minification 982.0 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. Df Doom images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 7.7 kB

  • Original 205.8 kB
  • After minification 205.8 kB
  • After compression 198.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 1.9 kB

  • Original 47.5 kB
  • After minification 47.4 kB
  • After compression 45.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. Dfdoom.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (80%)

Requests Now

51

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dfdoom.com

dfdoom.com

299 ms

dfdoom.com

dfdoom.com

384 ms

www.dfdoom.com

www.dfdoom.com

1892 ms

extra.min.css

extra.min.css

188 ms

styles.css

styles.css

281 ms

p.css

p.css

283 ms

basicLightbox.min.css

basicLightbox.min.css

282 ms

style.css

style.css

292 ms

css

css

34 ms

css

css

19 ms

style.css

style.css

195 ms

style.css

style.css

202 ms

jquery.min.js

jquery.min.js

375 ms

jquery-migrate.min.js

jquery-migrate.min.js

288 ms

p.js

p.js

293 ms

basicLightbox.min.js

basicLightbox.min.js

294 ms

js

js

62 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

298 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

299 ms

hooks.min.js

hooks.min.js

381 ms

i18n.min.js

i18n.min.js

391 ms

index.js

index.js

390 ms

index.js

index.js

401 ms

dlm-xhr.min.js

dlm-xhr.min.js

401 ms

idle-timer.min.js

idle-timer.min.js

469 ms

custom.js

custom.js

477 ms

scripts.min.js

scripts.min.js

684 ms

jquery.fitvids.js

jquery.fitvids.js

495 ms

jquery.mobile.js

jquery.mobile.js

498 ms

easypiechart.js

easypiechart.js

504 ms

salvattore.js

salvattore.js

566 ms

common.js

common.js

572 ms

scripts.js

scripts.js

593 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

597 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

769 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

668 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

670 ms

style.css

style.css

495 ms

e1m1.gif

e1m1.gif

409 ms

dragonfly-background.jpg

dragonfly-background.jpg

404 ms

dfdoom-logo-edge.png

dfdoom-logo-edge.png

285 ms

et-divi-dynamic-2-late.css

et-divi-dynamic-2-late.css

105 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

17 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

21 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

27 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

33 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

33 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

35 ms

modules.woff

modules.woff

200 ms

006-home.png

006-home.png

242 ms

005-sketch.png

005-sketch.png

246 ms

midi-music.png

midi-music.png

275 ms

004-open-book.png

004-open-book.png

275 ms

003-chat.png

003-chat.png

283 ms

001-twitter.png

001-twitter.png

283 ms

002-twitch.png

002-twitch.png

334 ms

dfload.png

dfload.png

340 ms

skulldash-1.jpg

skulldash-1.jpg

327 ms

skulldash-2.jpg

skulldash-2.jpg

327 ms

style.min.css

style.min.css

101 ms

skulldash-4.jpg

skulldash-4.jpg

312 ms

e1m1.gif

e1m1.gif

103 ms

dragonfly-background.jpg

dragonfly-background.jpg

463 ms

006-home.png

006-home.png

97 ms

005-sketch.png

005-sketch.png

100 ms

midi-music.png

midi-music.png

98 ms

004-open-book.png

004-open-book.png

97 ms

003-chat.png

003-chat.png

99 ms

001-twitter.png

001-twitter.png

155 ms

002-twitch.png

002-twitch.png

119 ms

dfload.png

dfload.png

136 ms

skulldash-1.jpg

skulldash-1.jpg

110 ms

skulldash-2.jpg

skulldash-2.jpg

396 ms

skulldash-4.jpg

skulldash-4.jpg

346 ms

Accessibility Review

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

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

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Page has valid source maps

SEO Factors

dfdoom.com SEO score

93

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dfdoom.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 Dfdoom.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

dfdoom.com

Open Graph data is detected on the main page of Df Doom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: