Tools & Wizards About Us
legacy.duke4.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

legacy.duke4.net

Duke Nukem 3D, Duke Nukem Forever • Duke4.net: News

Page Load Speed

3.3 sec in total

First Response

227 ms

Resources Loaded

2.2 sec

Page Rendered

952 ms

legacy.duke4.net screenshot

About Website

Welcome to legacy.duke4.net homepage info - get ready to check Legacy Duke4 best content for United States right away, or after learning these important things about legacy.duke4.net

The largest Duke Nukem community! Features forums, latest news, media, and downloads.

Visit legacy.duke4.net

Key Findings

We analyzed Legacy.duke4.net page load time and found that the first response time was 227 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

legacy.duke4.net performance score

0

Network Requests Diagram

news.php

227 ms

sdmenu.js

75 ms

e107.js

112 ms

style.css

191 ms

jquery.min.js

27 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 84% of them (63 requests) were addressed to the original Legacy.duke4.net, 4% (3 requests) were made to S7.addthis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (879 ms) belongs to the original domain Legacy.duke4.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 731.0 kB (29%)

Content Size

2.5 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Legacy.duke4.net main page is 2.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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 327.1 kB

  • Original 455.1 kB
  • After minification 450.9 kB
  • After compression 128.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. 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 327.1 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 16.6 kB

  • Original 1.5 MB
  • After minification 1.4 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. Legacy Duke4 images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 362.4 kB

  • Original 559.9 kB
  • After minification 532.8 kB
  • After compression 197.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 362.4 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 24.9 kB

  • Original 29.8 kB
  • After minification 23.7 kB
  • After compression 4.9 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. Legacy.duke4.net needs all CSS files to be minified and compressed as it can save up to 24.9 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

news.php

news.php

227 ms

sdmenu.js

sdmenu.js

75 ms

e107.js

e107.js

112 ms

style.css

style.css

191 ms

jquery.min.js

jquery.min.js

27 ms

hidecontent.css

hidecontent.css

130 ms

lightbox.css

lightbox.css

147 ms

prototype.js

prototype.js

222 ms

scriptaculous.js

scriptaculous.js

147 ms

lightbox.js

lightbox.js

164 ms

default.css

default.css

201 ms

lightbox.css

lightbox.css

218 ms

addthis_widget.js

addthis_widget.js

13 ms

urchin.js

urchin.js

15 ms

counter_xhtml.js

counter_xhtml.js

10 ms

quant.js

quant.js

12 ms

effects.js

effects.js

84 ms

window.js

window.js

227 ms

pixel.gif

pixel.gif

189 ms

lg-bookmark-en.gif

lg-bookmark-en.gif

42 ms

flagbg.jpg

flagbg.jpg

176 ms

wrap1.gif

wrap1.gif

174 ms

wrap3.jpg

wrap3.jpg

174 ms

header2.jpg

header2.jpg

200 ms

nav12.jpg

nav12.jpg

176 ms

bottom.gif

bottom.gif

174 ms

expanded.gif

expanded.gif

246 ms

gog_new.jpg

gog_new.jpg

221 ms

title.gif

title.gif

245 ms

title_affils.gif

title_affils.gif

245 ms

eduke32.png

eduke32.png

219 ms

rtcm_button.png

rtcm_button.png

292 ms

mead_button.png

mead_button.png

292 ms

nav22.jpg

nav22.jpg

361 ms

main.gif

main.gif

332 ms

donate.gif

donate.gif

329 ms

france.gif

france.gif

328 ms

germany.gif

germany.gif

332 ms

italy.gif

italy.gif

360 ms

spain.gif

spain.gif

384 ms

portugal.gif

portugal.gif

383 ms

japan.png

japan.png

384 ms

russia.png

russia.png

359 ms

netherlands.gif

netherlands.gif

423 ms

china.png

china.png

421 ms

arabia.png

arabia.png

422 ms

korea.png

korea.png

537 ms

united-kingdom.gif

united-kingdom.gif

538 ms

button.png

button.png

537 ms

users_16.png

users_16.png

541 ms

3drealms.jpg

3drealms.jpg

540 ms

dukegen.jpg

dukegen.jpg

542 ms

wink.gif

wink.gif

544 ms

duke3d.jpg

duke3d.jpg

543 ms

tubgirls.jpg

tubgirls.jpg

658 ms

3drofficehistory_2.png

3drofficehistory_2.png

879 ms

3drofficehistory.png

3drofficehistory.png

872 ms

console.jpg

console.jpg

385 ms

dnf.jpg

dnf.jpg

428 ms

gearbox.jpg

gearbox.jpg

427 ms

site.jpg

site.jpg

425 ms

newsfooter.gif

newsfooter.gif

417 ms

newsd1.jpg

newsd1.jpg

447 ms

newsd2.jpg

newsd2.jpg

425 ms

rarrow.png

rarrow.png

446 ms

close-quote.gif

close-quote.gif

493 ms

open-quote.gif

open-quote.gif

473 ms

footer.png

footer.png

314 ms

__utm.gif

__utm.gif

104 ms

t.php

t.php

104 ms

pixel;r=180987585;a=p-6fOVuaZTMXSrk;fpan=1;fpa=P0-1636298529-1458435011796;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458435011795;tzo=-180;ref=;url=http%3A%2F%2Flegacy.duke4.net%2Fnews.php;ogl=

pixel;r=180987585;a=p-6fOVuaZTMXSrk;fpan=1;fpa=P0-1636298529-1458435011796;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458435011795;tzo=-180;ref=;url=http%3A%2F%2Flegacy.duke4.net%2Fnews.php;ogl=

93 ms

300lo.json

300lo.json

78 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

32 ms

loading.gif

loading.gif

76 ms

close.gif

close.gif

66 ms

SEO Factors

legacy.duke4.net SEO score

0

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 Legacy.duke4.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 Legacy.duke4.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

legacy.duke4.net

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