Tools & Wizards About Us
onleech.me screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

onleech.me

OnLeech

Page Load Speed

5.2 sec in total

First Response

534 ms

Resources Loaded

2.4 sec

Page Rendered

2.3 sec

onleech.me screenshot

About Website

Welcome to onleech.me homepage info - get ready to check On Leech best content for Iran right away, or after learning these important things about onleech.me

Free premium link generator service for uploaded, rapidgator, turbobit, keep2share, fboom, wushare, nitroflare, file.al, 1fichier, yunfile, filefactory, uptobox, katfile, datafile, mega, easybytez and...

Visit onleech.me

Key Findings

We analyzed Onleech.me page load time and found that the first response time was 534 ms and then it took 4.7 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

onleech.me performance score

0

Network Requests Diagram

onleech.me

534 ms

css

25 ms

ui.totop.css

87 ms

jquery-1.12.4.min.js

104 ms

jquery.dropotron.min.js

175 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 65% of them (47 requests) were addressed to the original Onleech.me, 13% (9 requests) were made to Smilies.onleech.me and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (950 ms) relates to the external source Smilies.onleech.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 295.6 kB (71%)

Content Size

419.2 kB

After Optimization

123.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Onleech.me main page is 419.2 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. 45% of websites need less resources to load. Javascripts take 318.3 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 7.4 kB

  • Original 10.4 kB
  • After minification 8.4 kB
  • After compression 2.9 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 19% 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 7.4 kB or 72% of the original size.

JavaScript Optimization

-67%

Potential reduce by 212.1 kB

  • Original 318.3 kB
  • After minification 305.5 kB
  • After compression 106.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 212.1 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 76.1 kB

  • Original 90.5 kB
  • After minification 61.4 kB
  • After compression 14.4 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. Onleech.me needs all CSS files to be minified and compressed as it can save up to 76.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (61%)

Requests Now

61

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onleech.me

onleech.me

534 ms

css

css

25 ms

ui.totop.css

ui.totop.css

87 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

104 ms

jquery.dropotron.min.js

jquery.dropotron.min.js

175 ms

config.js

config.js

175 ms

skel.min.js

skel.min.js

260 ms

skel-panels.min.js

skel-panels.min.js

267 ms

styles.css

styles.css

176 ms

font-awesome.css

font-awesome.css

268 ms

css

css

35 ms

easing.js

easing.js

264 ms

jquery.ui.totop.js

jquery.ui.totop.js

265 ms

style.css

style.css

174 ms

style-desktop.css

style-desktop.css

88 ms

style-1000px.css

style-1000px.css

90 ms

70 ms

70 ms

bg02.png

bg02.png

174 ms

bg01.png

bg01.png

257 ms

logo.png

logo.png

94 ms

ui.totop.png

ui.totop.png

260 ms

128 ms

133 ms

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

29 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

38 ms

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

54 ms

toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf

toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf

56 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

176 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

257 ms

gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf

gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf

54 ms

gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf

gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf

54 ms

65 ms

jsc_compact_6961.js

jsc_compact_6961.js

19 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

260 ms

buttons.css

buttons.css

93 ms

ticker-style.css

ticker-style.css

144 ms

jquery.ticker.js

jquery.ticker.js

152 ms

jquery.cookie.js

jquery.cookie.js

185 ms

mod.js

mod.js

217 ms

shake.css

shake.css

170 ms

colour.css

colour.css

170 ms

chk_good.png

chk_good.png

750 ms

yoyo200.gif

yoyo200.gif

742 ms

yociexp102.gif

yociexp102.gif

743 ms

sung.gif

sung.gif

746 ms

156.gif

156.gif

742 ms

Orion_51.gif

Orion_51.gif

743 ms

bom.gif

bom.gif

950 ms

f2.gif

f2.gif

744 ms

148.gif

148.gif

745 ms

button_bg.png

button_bg.png

90 ms

effect2.gif

effect2.gif

18 ms

group.php

group.php

95 ms

color.js

color.js

96 ms

filter.js

filter.js

95 ms

jquery.colourPicker.js

jquery.colourPicker.js

93 ms

cmod.js

cmod.js

89 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

504 ms

post.js

post.js

499 ms

267 ms

jquery.colourPicker.png

jquery.colourPicker.png

92 ms

b.png

b.png

89 ms

i.png

i.png

103 ms

u.png

u.png

101 ms

s.png

s.png

91 ms

sup.png

sup.png

101 ms

sub.png

sub.png

185 ms

center.png

center.png

178 ms

media.png

media.png

177 ms

img.png

img.png

183 ms

robot.png

robot.png

180 ms

SEO Factors

onleech.me SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onleech.me can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Onleech.me 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

onleech.me

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