Tools & Wizards About Us
eblocks.cl screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

eblocks.cl

e-Blocks

Page Load Speed

9.2 sec in total

First Response

1.7 sec

Resources Loaded

7.2 sec

Page Rendered

312 ms

eblocks.cl screenshot

About Website

Welcome to eblocks.cl homepage info - get ready to check E Blocks best content right away, or after learning these important things about eblocks.cl

Visit eblocks.cl

Key Findings

We analyzed Eblocks.cl page load time and found that the first response time was 1.7 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

eblocks.cl performance score

0

Network Requests Diagram

eblocks.cl

1687 ms

bootstrap.css

692 ms

default.css

291 ms

template.css

420 ms

touch.gallery.css

287 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 84% of them (54 requests) were addressed to the original Eblocks.cl, 9% (6 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Eblocks.cl.

Page Optimization Overview & Recommendations

Page size can be reduced by 751.0 kB (36%)

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 21.7 kB

  • Original 28.2 kB
  • After minification 24.4 kB
  • After compression 6.4 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 3.8 kB, which is 13% 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 21.7 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 45.9 kB

  • Original 1.2 MB
  • After minification 1.1 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. E Blocks images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 486.0 kB

  • Original 666.8 kB
  • After minification 596.6 kB
  • After compression 180.8 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 486.0 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 197.4 kB

  • Original 234.1 kB
  • After minification 187.3 kB
  • After compression 36.7 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. Eblocks.cl needs all CSS files to be minified and compressed as it can save up to 197.4 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eblocks.cl

eblocks.cl

1687 ms

bootstrap.css

bootstrap.css

692 ms

default.css

default.css

291 ms

template.css

template.css

420 ms

touch.gallery.css

touch.gallery.css

287 ms

responsive.css

responsive.css

292 ms

komento.css

komento.css

289 ms

magnific-popup.css

magnific-popup.css

429 ms

camera.css

camera.css

427 ms

superfish.css

superfish.css

436 ms

superfish-navbar.css

superfish-navbar.css

434 ms

superfish-vertical.css

superfish-vertical.css

555 ms

jquery.min.js

jquery.min.js

965 ms

jquery-noconflict.js

jquery-noconflict.js

565 ms

jquery-migrate.min.js

jquery-migrate.min.js

572 ms

caption.js

caption.js

576 ms

mootools-core.js

mootools-core.js

960 ms

core.js

core.js

711 ms

mootools-more.js

mootools-more.js

1428 ms

jquery.mobile.customized.min.js

jquery.mobile.customized.min.js

859 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

821 ms

bootstrap.js

bootstrap.js

1110 ms

jquery.isotope.min.js

jquery.isotope.min.js

997 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

1176 ms

scripts.js

scripts.js

1089 ms

camera.min.js

camera.min.js

1097 ms

jquery.mobile.customized.min.js

jquery.mobile.customized.min.js

1100 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1228 ms

superfish.js

superfish.js

1238 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

1239 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

1245 ms

supersubs.js

supersubs.js

1316 ms

sftouchscreen.js

sftouchscreen.js

1364 ms

css

css

24 ms

css

css

34 ms

css

css

44 ms

css

css

44 ms

feature-row_bg.png

feature-row_bg.png

141 ms

main_img.jpg

main_img.jpg

2760 ms

logo.png

logo.png

146 ms

search_icon.gif

search_icon.gif

143 ms

menu_border.gif

menu_border.gif

144 ms

s-BiyweUPV0v-yRb-cjciL3hpw3pgy2gAi-Ip7WPMi0.woff

s-BiyweUPV0v-yRb-cjciL3hpw3pgy2gAi-Ip7WPMi0.woff

66 ms

EFpQQyG9GqCrobXxL-KRMXbFhgvWbfSbdVg11QabG8w.woff

EFpQQyG9GqCrobXxL-KRMXbFhgvWbfSbdVg11QabG8w.woff

66 ms

thumb-1.jpg

thumb-1.jpg

410 ms

thumb-2.jpg

thumb-2.jpg

405 ms

thumb-3.jpg

thumb-3.jpg

420 ms

thumb-4.jpg

thumb-4.jpg

423 ms

cubosnios.png

cubosnios.png

1444 ms

linares-ch.JPG

linares-ch.JPG

547 ms

panama-ch.jpg

panama-ch.jpg

553 ms

shadow.png

shadow.png

494 ms

dotted_border.gif

dotted_border.gif

500 ms

footer_texture.jpg

footer_texture.jpg

633 ms

up-arrow.png

up-arrow.png

634 ms

prev.png

prev.png

634 ms

next.png

next.png

640 ms

camera-loader.gif

camera-loader.gif

775 ms

slide-1.jpg

slide-1.jpg

2377 ms

_weQNDK6Uf40CiGFKBBUjrrIa-7acMAeDBVuclsi6Gc.woff

_weQNDK6Uf40CiGFKBBUjrrIa-7acMAeDBVuclsi6Gc.woff

7 ms

hudNQFKFl98JdNnlo363fhbnBKKEOwRKgsHDreGcocg.woff

hudNQFKFl98JdNnlo363fhbnBKKEOwRKgsHDreGcocg.woff

9 ms

QGN0GG0540fyG6NL_PpOpgLUuEpTyoUstqEm5AMlJo4.woff

QGN0GG0540fyG6NL_PpOpgLUuEpTyoUstqEm5AMlJo4.woff

8 ms

nvGvEwsMAvkIa6w2U-PXffesZW2xOQ-xsNqO47m55DA.woff

nvGvEwsMAvkIa6w2U-PXffesZW2xOQ-xsNqO47m55DA.woff

7 ms

slide-2.jpg

slide-2.jpg

1617 ms

SEO Factors

eblocks.cl SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eblocks.cl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Eblocks.cl 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

eblocks.cl

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