6.1 sec in total
217 ms
5.3 sec
601 ms
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.comWe analyzed Dfdoom.com page load time and found that the first response time was 217 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
dfdoom.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value15.2 s
0/100
25%
Value8.2 s
20/100
10%
Value450 ms
63/100
30%
Value0.06
98/100
15%
Value7.2 s
51/100
10%
217 ms
383 ms
2516 ms
190 ms
278 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 64% of them (54 requests) were addressed to the original Dfdoom.com, 19% (16 requests) were made to Cdn.dfdoom.com and 11% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Dfdoom.com.
Page size can be reduced by 564.8 kB (16%)
3.6 MB
3.0 MB
In fact, the total size of Dfdoom.com main page is 3.6 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 202.3 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 202.3 kB or 84% of the original size.
Potential reduce by 349.3 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, Df Doom needs image optimization as it can save up to 349.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 11.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.0 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.
Number of requests can be reduced by 41 (73%)
56
15
The browser has sent 56 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.
dfdoom.com
217 ms
dfdoom.com
383 ms
www.dfdoom.com
2516 ms
extra.min.css
190 ms
p.css
278 ms
basicLightbox.min.css
287 ms
styles.css
283 ms
style.css
293 ms
css
30 ms
css
14 ms
style.css
206 ms
style.css
191 ms
jquery.min.js
377 ms
jquery-migrate.min.js
291 ms
p.js
292 ms
basicLightbox.min.js
293 ms
js
63 ms
mediaelementplayer-legacy.min.css
295 ms
wp-mediaelement.min.css
299 ms
index.js
390 ms
index.js
390 ms
dlm-xhr.min.js
391 ms
idle-timer.min.js
393 ms
custom.js
400 ms
scripts.min.js
581 ms
jquery.fitvids.js
492 ms
jquery.mobile.js
492 ms
easypiechart.js
498 ms
salvattore.js
495 ms
common.js
498 ms
scripts.js
596 ms
smush-lazy-load.min.js
590 ms
mediaelement-and-player.min.js
796 ms
mediaelement-migrate.min.js
595 ms
wp-mediaelement.min.js
604 ms
style.css
490 ms
adventure-ep-cover-banner.png
534 ms
progheader.jpg
560 ms
prodeus-header.png
563 ms
skulldash-1.jpg
562 ms
skulldash-2.jpg
561 ms
skulldash-4.jpg
559 ms
dragonfly-background.jpg
579 ms
latest-posts.png
102 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
26 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
33 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
38 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
44 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
46 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
47 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
46 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
42 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
45 ms
modules.woff
242 ms
et-divi-dynamic-2-late.css
107 ms
js
124 ms
analytics.js
170 ms
dfdoom-logo-edge.png
457 ms
006-home.png
265 ms
005-sketch.png
265 ms
midi-music.png
268 ms
004-open-book.png
274 ms
003-chat.png
275 ms
001-twitter.png
287 ms
002-twitch.png
359 ms
dfload.png
358 ms
adventure-ep-cover-banner.png
565 ms
collect
14 ms
skulldash-4.jpg
290 ms
progheader.jpg
375 ms
skulldash-2.jpg
375 ms
skulldash-1.jpg
378 ms
prodeus-header.png
567 ms
dragonfly-background.jpg
465 ms
006-home.png
390 ms
005-sketch.png
387 ms
midi-music.png
388 ms
004-open-book.png
480 ms
003-chat.png
479 ms
001-twitter.png
472 ms
dfload.png
401 ms
002-twitch.png
447 ms
style.min.css
109 ms
e1m1.gif
93 ms
e1m1.gif
102 ms
dfdoom.com accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dfdoom.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
dfdoom.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
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.
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: