Tools & Wizards About Us
leacore.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

leacore.com

Page Load Speed

1.8 sec in total

First Response

218 ms

Resources Loaded

1.2 sec

Page Rendered

418 ms

leacore.com screenshot

About Website

Click here to check amazing Leacore content. Otherwise, check out these important facts you probably never knew about leacore.com

www.leacore.com

Visit leacore.com

Key Findings

We analyzed Leacore.com page load time and found that the first response time was 218 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

leacore.com performance score

0

Network Requests Diagram

www.leacore.com

218 ms

a89e9e1e52f784d42f2ffc9f00594b59.css

38 ms

8fcb24b8283d4f00ad7b6982eed802e8.css

147 ms

prototype.js

130 ms

ccard.js

97 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 96% of them (75 requests) were addressed to the original Leacore.com, 3% (2 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (318 ms) belongs to the original domain Leacore.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (46%)

Content Size

3.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Leacore.com main page is 3.1 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 133.3 kB

  • Original 144.3 kB
  • After minification 102.9 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 41.4 kB, which is 29% 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 133.3 kB or 92% of the original size.

Image Optimization

-8%

Potential reduce by 119.9 kB

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

JavaScript Optimization

-75%

Potential reduce by 683.5 kB

  • Original 917.1 kB
  • After minification 778.9 kB
  • After compression 233.6 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 683.5 kB or 75% of the original size.

CSS Optimization

-87%

Potential reduce by 480.4 kB

  • Original 551.8 kB
  • After minification 482.9 kB
  • After compression 71.3 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. Leacore.com needs all CSS files to be minified and compressed as it can save up to 480.4 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

74

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.leacore.com

www.leacore.com

218 ms

a89e9e1e52f784d42f2ffc9f00594b59.css

a89e9e1e52f784d42f2ffc9f00594b59.css

38 ms

8fcb24b8283d4f00ad7b6982eed802e8.css

8fcb24b8283d4f00ad7b6982eed802e8.css

147 ms

prototype.js

prototype.js

130 ms

ccard.js

ccard.js

97 ms

validation.js

validation.js

97 ms

builder.js

builder.js

86 ms

effects.js

effects.js

99 ms

dragdrop.js

dragdrop.js

121 ms

controls.js

controls.js

133 ms

slider.js

slider.js

132 ms

js.js

js.js

135 ms

form.js

form.js

198 ms

menu.js

menu.js

198 ms

translate.js

translate.js

199 ms

cookies.js

cookies.js

198 ms

jquery.js

jquery.js

209 ms

jquery-noconflict.js

jquery-noconflict.js

200 ms

jquery.cookie.min.js

jquery.cookie.min.js

199 ms

jquery.easing.js

jquery.easing.js

200 ms

bootstrap.min.js

bootstrap.min.js

200 ms

owl.carousel.min.js

owl.carousel.min.js

201 ms

toolbar.js

toolbar.js

227 ms

lightbox.js

lightbox.js

228 ms

easylightbox.js

easylightbox.js

229 ms

jquery.jqtransform.js

jquery.jqtransform.js

232 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

236 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

242 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

247 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

252 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

301 ms

pslogin.js

pslogin.js

268 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

318 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

282 ms

twitterfetcher-min.js

twitterfetcher-min.js

280 ms

jquery.sticky-kit.min.js

jquery.sticky-kit.min.js

284 ms

css

css

22 ms

sns-extend.js

sns-extend.js

313 ms

sns-script.js

sns-script.js

300 ms

close.png

close.png

45 ms

loading.gif

loading.gif

48 ms

prev.png

prev.png

46 ms

next.png

next.png

47 ms

separator-h.gif

separator-h.gif

47 ms

arrow-down.gif

arrow-down.gif

46 ms

logo.png

logo.png

150 ms

mainproduct1.jpg

mainproduct1.jpg

268 ms

learnmore.jpg

learnmore.jpg

150 ms

mainproduct2.jpg

mainproduct2.jpg

152 ms

mainproduct3.jpg

mainproduct3.jpg

188 ms

sl4-bg.jpg

sl4-bg.jpg

151 ms

file_11.png

file_11.png

168 ms

file_9_2.png

file_9_2.png

152 ms

file_1_2.png

file_1_2.png

188 ms

file_7.png

file_7.png

213 ms

logo_4.png

logo_4.png

184 ms

1.jpg

1.jpg

205 ms

file_2.png

file_2.png

261 ms

we357a7pxaa_pa-l_1.jpg

we357a7pxaa_pa-l_1.jpg

218 ms

file_3.png

file_3.png

260 ms

wmn3000_1_5.jpg

wmn3000_1_5.jpg

241 ms

untitled-1_5.jpg

untitled-1_5.jpg

249 ms

level-u_002_dynamic_white_400_1.jpg

level-u_002_dynamic_white_400_1.jpg

254 ms

file_1.png

file_1.png

312 ms

ODelI1aHBYDBqgeIAH2zlEY6Fu39Tt9XkmtSosaMoEA.ttf

ODelI1aHBYDBqgeIAH2zlEY6Fu39Tt9XkmtSosaMoEA.ttf

12 ms

toadOcfmlt9b38dHJxOBGBRq_IsDXucKYMk4-diqPEc.ttf

toadOcfmlt9b38dHJxOBGBRq_IsDXucKYMk4-diqPEc.ttf

12 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

307 ms

timer.png

timer.png

269 ms

phone_1.png

phone_1.png

257 ms

phonefilm_1.png

phonefilm_1.png

256 ms

dataline_1.png

dataline_1.png

260 ms

other_2.png

other_2.png

290 ms

dot-1.png

dot-1.png

302 ms

pay-me.png

pay-me.png

284 ms

loader.gif

loader.gif

199 ms

arrow-sliseshow.png

arrow-sliseshow.png

227 ms

arrow-sliseshow-inner.png

arrow-sliseshow-inner.png

228 ms

9358d6050bbbc17e4aa4e2e97566d141.css

9358d6050bbbc17e4aa4e2e97566d141.css

35 ms

SEO Factors

leacore.com 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 Leacore.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 Leacore.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.

Social Sharing Optimization

leacore.com

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