Tools & Wizards About Us
leafre.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

leafre.net

leafre.net

Page Load Speed

8 sec in total

First Response

1.2 sec

Resources Loaded

6.3 sec

Page Rendered

479 ms

leafre.net screenshot

About Website

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

This domain may be for sale!

Visit leafre.net

Key Findings

We analyzed Leafre.net page load time and found that the first response time was 1.2 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

leafre.net performance score

0

Network Requests Diagram

leafre.net

1245 ms

combo

63 ms

vbulletin-core.js

19 ms

main-rollup.css

29 ms

e360_markup.css

18 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 70% of them (92 requests) were addressed to the original Leafre.net, 5% (6 requests) were made to C.betrad.com and 4% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Leafre.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 431.2 kB (50%)

Content Size

856.2 kB

After Optimization

425.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 102.9 kB

  • Original 121.6 kB
  • After minification 109.5 kB
  • After compression 18.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. 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 102.9 kB or 85% of the original size.

Image Optimization

-33%

Potential reduce by 119.8 kB

  • Original 368.0 kB
  • After minification 248.2 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, Leafre needs image optimization as it can save up to 119.8 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-40%

Potential reduce by 86.9 kB

  • Original 215.3 kB
  • After minification 213.1 kB
  • After compression 128.4 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 86.9 kB or 40% of the original size.

CSS Optimization

-80%

Potential reduce by 121.5 kB

  • Original 151.4 kB
  • After minification 140.9 kB
  • After compression 29.8 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. Leafre.net needs all CSS files to be minified and compressed as it can save up to 121.5 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

123

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

leafre.net

leafre.net

1245 ms

combo

combo

63 ms

vbulletin-core.js

vbulletin-core.js

19 ms

main-rollup.css

main-rollup.css

29 ms

e360_markup.css

e360_markup.css

18 ms

css

css

37 ms

dbtech_vbshout.css

dbtech_vbshout.css

20 ms

dbtech_vbshout_colours.css

dbtech_vbshout_colours.css

21 ms

dbtech_vbshout_editor.css

dbtech_vbshout_editor.css

13 ms

jquery.min.js

jquery.min.js

51 ms

jquery.tmpl.min.js

jquery.tmpl.min.js

39 ms

vbshout.js

vbshout.js

34 ms

dbtech_posttemplates.css

dbtech_posttemplates.css

37 ms

vbulletin_read_marker.js

vbulletin_read_marker.js

45 ms

forumhome-rollup.css

forumhome-rollup.css

1967 ms

sidebar.css

sidebar.css

958 ms

widgets.css

widgets.css

1993 ms

tagcloud.css

tagcloud.css

1969 ms

vbulletin-sidebar.js

vbulletin-sidebar.js

2019 ms

additional.css

additional.css

2020 ms

jquery.min.js

jquery.min.js

94 ms

tabview.css

tabview.css

2042 ms

skin-tfh.css

skin-tfh.css

2034 ms

utilities.js

utilities.js

94 ms

tabview-min.js

tabview-min.js

94 ms

dispatcher-min.js

dispatcher-min.js

490 ms

css.php

css.php

2055 ms

vbulletin_md5.js

vbulletin_md5.js

2050 ms

adsbygoogle.js

adsbygoogle.js

32 ms

animation-min.js

animation-min.js

11 ms

V2ncQgy.png

V2ncQgy.png

39 ms

regSplit.gif

regSplit.gif

894 ms

loginBoxInput.gif

loginBoxInput.gif

911 ms

loginButton.gif

loginButton.gif

25 ms

search.png

search.png

891 ms

navbit-home.png

navbit-home.png

27 ms

Leafre.net.png

Leafre.net.png

25 ms

collapse_tcat.png

collapse_tcat.png

912 ms

forum_old-48.png

forum_old-48.png

908 ms

lastpost-right.png

lastpost-right.png

1897 ms

nxforum_old-48.png

nxforum_old-48.png

1939 ms

Patch.png

Patch.png

1902 ms

Event.png

Event.png

1903 ms

Info.png

Info.png

1904 ms

News.png

News.png

1905 ms

Offline.png

Offline.png

1907 ms

Developer.png

Developer.png

1917 ms

ms2forum_old-48.png

ms2forum_old-48.png

1910 ms

subforum_old-48.png

subforum_old-48.png

1912 ms

MapleStory%202.png

MapleStory%202.png

1947 ms

icon9.png

icon9.png

1950 ms

icon10.png

icon10.png

1919 ms

Korean%20Maplestory.png

Korean%20Maplestory.png

1945 ms

icon11.png

icon11.png

1925 ms

icon14.png

icon14.png

1944 ms

poll_posticon.gif

poll_posticon.gif

1956 ms

Support.png

Support.png

1978 ms

Social%20Corner.png

Social%20Corner.png

2012 ms

users_online.png

users_online.png

2008 ms

forum_stats.png

forum_stats.png

1981 ms

tab-collapsed.png

tab-collapsed.png

1967 ms

collapse_40b.png

collapse_40b.png

2022 ms

widget-forum.png

widget-forum.png

2890 ms

cash.gif

cash.gif

2893 ms

block_verified.png

block_verified.png

2907 ms

Paypal.png

Paypal.png

2893 ms

6fRNNCO.png

6fRNNCO.png

82 ms

ta1

ta1

122 ms

visa.png

visa.png

2888 ms

MasterCard.png

MasterCard.png

2888 ms

amex.png

amex.png

2891 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

63 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

64 ms

Discover.png

Discover.png

2892 ms

ca-pub-1959029395340554.js

ca-pub-1959029395340554.js

101 ms

zrt_lookup.html

zrt_lookup.html

110 ms

show_ads_impl.js

show_ads_impl.js

147 ms

1pO9eUAp8pSF8VnRTP3xnvesZW2xOQ-xsNqO47m55DA.woff

1pO9eUAp8pSF8VnRTP3xnvesZW2xOQ-xsNqO47m55DA.woff

24 ms

7m8l7TlFO-S3VkhHuR0at4bN6UDyHWBl620a-IRfuBk.woff

7m8l7TlFO-S3VkhHuR0at4bN6UDyHWBl620a-IRfuBk.woff

112 ms

t6Nd4cfPRhZP44Q5QAjcC4bN6UDyHWBl620a-IRfuBk.woff

t6Nd4cfPRhZP44Q5QAjcC4bN6UDyHWBl620a-IRfuBk.woff

111 ms

ts.php

ts.php

105 ms

ads

ads

210 ms

osd.js

osd.js

19 ms

ads

ads

234 ms

ads

ads

274 ms

0_3AxRJtmH.jpg

0_3AxRJtmH.jpg

217 ms

a.gif

a.gif

71 ms

bcs0

bcs0

81 ms

creative_add_on.js

creative_add_on.js

157 ms

surly.js

surly.js

188 ms

a.gif

a.gif

5 ms

bcs0

bcs0

6 ms

0_3AxRJtmH.jpg

0_3AxRJtmH.jpg

122 ms

ba.html

ba.html

34 ms

4.gif

4.gif

53 ms

2532.js

2532.js

49 ms

avatar18278_3.gif

avatar18278_3.gif

2026 ms

avatar20216_5.gif

avatar20216_5.gif

2028 ms

box_19_top-right.png

box_19_top-right.png

28 ms

ci.png

ci.png

92 ms

avatar20342_1.gif

avatar20342_1.gif

2042 ms

unknown.gif

unknown.gif

2016 ms

cron.php

cron.php

2006 ms

social_twitter.png

social_twitter.png

1023 ms

social_fb.png

social_fb.png

1025 ms

youtube.png

youtube.png

1026 ms

nature.png

nature.png

1047 ms

logo_blue.png

logo_blue.png

1031 ms

navBG.gif

navBG.gif

1030 ms

activeview

activeview

14 ms

navSplit.gif

navSplit.gif

1023 ms

navBG_blue.gif

navBG_blue.gif

1029 ms

arrow.png

arrow.png

1031 ms

contentBG.gif

contentBG.gif

1019 ms

bcBG.gif

bcBG.gif

1021 ms

vbsocialreg.jpg

vbsocialreg.jpg

1016 ms

tcatBG.gif

tcatBG.gif

1008 ms

tcatLeft.gif

tcatLeft.gif

1017 ms

tcatRight.gif

tcatRight.gif

1011 ms

rss_40b.png

rss_40b.png

1010 ms

bottomBarBG.gif

bottomBarBG.gif

997 ms

bottomBarLeft.gif

bottomBarLeft.gif

1000 ms

bottomBarRight.gif

bottomBarRight.gif

983 ms

gradient-greytowhite.png

gradient-greytowhite.png

978 ms

background6.gif

background6.gif

958 ms

top-highlight.png

top-highlight.png

951 ms

gradient-black-down.png

gradient-black-down.png

946 ms

generic_button.png

generic_button.png

84 ms

bottom-shadow.png

bottom-shadow.png

78 ms

footerNav.gif

footerNav.gif

77 ms

footerBG.gif

footerBG.gif

71 ms

SEO Factors

leafre.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

leafre.net

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