Tools & Wizards About Us
mp3leak.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mp3leak.com

Page Load Speed

3 sec in total

First Response

235 ms

Resources Loaded

2.4 sec

Page Rendered

321 ms

mp3leak.com screenshot

About Website

Visit mp3leak.com now to see the best up-to-date Mp 3 Leak content and also check out these interesting facts you probably never knew about mp3leak.com

We specialize in Professional Web Design, Myspace Profile Design, Online VIRAL Marketing, Flash Multimedia, Email Marketing, Newsletter Campaigns, SMS Text Blasts, Corporate Identity, and Print Graphi...

Visit mp3leak.com

Key Findings

We analyzed Mp3leak.com page load time and found that the first response time was 235 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

mp3leak.com performance score

0

Network Requests Diagram

mp3leak.com

235 ms

styles.css

264 ms

theme.css

206 ms

jquery-1.4.1.min.js

845 ms

jquery.flow.1.2.min.js

232 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 96% of them (67 requests) were addressed to the original Mp3leak.com, 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (845 ms) belongs to the original domain Mp3leak.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.4 kB (21%)

Content Size

989.8 kB

After Optimization

778.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mp3leak.com main page is 989.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 742.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 12.3 kB

  • Original 16.0 kB
  • After minification 14.0 kB
  • After compression 3.7 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 2.0 kB, which is 12% 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 12.3 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 48.5 kB

  • Original 742.8 kB
  • After minification 694.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. Mp 3 Leak images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 133.6 kB

  • Original 209.8 kB
  • After minification 195.0 kB
  • After compression 76.2 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 133.6 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 17.1 kB

  • Original 21.2 kB
  • After minification 15.6 kB
  • After compression 4.1 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. Mp3leak.com needs all CSS files to be minified and compressed as it can save up to 17.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (46%)

Requests Now

68

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mp3leak.com

mp3leak.com

235 ms

styles.css

styles.css

264 ms

theme.css

theme.css

206 ms

jquery-1.4.1.min.js

jquery-1.4.1.min.js

845 ms

jquery.flow.1.2.min.js

jquery.flow.1.2.min.js

232 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

291 ms

DD_belatedPNG.js

DD_belatedPNG.js

300 ms

clearbox.js

clearbox.js

269 ms

custom.js

custom.js

304 ms

cufon-yui.js

cufon-yui.js

385 ms

bebas_400.font.js

bebas_400.font.js

559 ms

cb_style.css

cb_style.css

62 ms

cb_config.js

cb_config.js

88 ms

cb_language.js

cb_language.js

131 ms

cb_core.js

cb_core.js

327 ms

Background.jpg

Background.jpg

229 ms

rainbow.png

rainbow.png

122 ms

head_bg.png

head_bg.png

191 ms

logo.png

logo.png

207 ms

teaser_bg.png

teaser_bg.png

692 ms

frameOver.png

frameOver.png

266 ms

home_fade_1.jpg

home_fade_1.jpg

482 ms

home_fade_2.jpg

home_fade_2.jpg

321 ms

home_fade_3.jpg

home_fade_3.jpg

423 ms

home_fade_4.jpg

home_fade_4.jpg

463 ms

block_head.png

block_head.png

345 ms

block_bg.png

block_bg.png

393 ms

underline_dotted.png

underline_dotted.png

420 ms

readmore_1.png

readmore_1.png

470 ms

block_bottom.png

block_bottom.png

503 ms

slider_squarePic_Bg.png

slider_squarePic_Bg.png

502 ms

footer_bg.png

footer_bg.png

591 ms

copyright.png

copyright.png

557 ms

ga.js

ga.js

4 ms

__utm.gif

__utm.gif

11 ms

close.png

close.png

82 ms

blank.gif

blank.gif

72 ms

prev.png

prev.png

91 ms

next.png

next.png

132 ms

pause.png

pause.png

139 ms

start.png

start.png

161 ms

s_topleft.png

s_topleft.png

176 ms

s_top.png

s_top.png

161 ms

s_topright.png

s_topright.png

210 ms

s_left.png

s_left.png

215 ms

s_right.png

s_right.png

227 ms

s_btmleft.png

s_btmleft.png

220 ms

s_btm.png

s_btm.png

249 ms

s_btmright.png

s_btmright.png

284 ms

btm_dl.gif

btm_dl.gif

287 ms

btm_max.gif

btm_max.gif

288 ms

btm_next.gif

btm_next.gif

290 ms

btm_prev.gif

btm_prev.gif

295 ms

btm_rot_l.gif

btm_rot_l.gif

329 ms

btm_rot_r.gif

btm_rot_r.gif

368 ms

no_flash.gif

no_flash.gif

358 ms

no_html.gif

no_html.gif

364 ms

no_iframe.gif

no_iframe.gif

350 ms

no_image.gif

no_image.gif

357 ms

no_inner.gif

no_inner.gif

405 ms

no_quicktime.gif

no_quicktime.gif

417 ms

no_winmedia.gif

no_winmedia.gif

425 ms

no_winmediaavi.gif

no_winmediaavi.gif

424 ms

no_winmediamp3.gif

no_winmediamp3.gif

432 ms

no_winmediampg.gif

no_winmediampg.gif

455 ms

no_winmediawav.gif

no_winmediawav.gif

480 ms

no_winmediawma.gif

no_winmediawma.gif

471 ms

no_winmediawmv.gif

no_winmediawmv.gif

494 ms

no_youtube.gif

no_youtube.gif

435 ms

__utm.gif

__utm.gif

9 ms

SEO Factors

mp3leak.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mp3leak.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Mp3leak.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

mp3leak.com

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