8.5 sec in total
2.5 sec
5.6 sec
424 ms
Visit epi.cl now to see the best up-to-date Epi content for Chile and also check out these interesting facts you probably never knew about epi.cl
Visit epi.clWe analyzed Epi.cl page load time and found that the first response time was 2.5 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
epi.cl performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value10.9 s
0/100
25%
Value12.4 s
3/100
10%
Value780 ms
38/100
30%
Value1.102
2/100
15%
Value11.0 s
21/100
10%
2490 ms
790 ms
793 ms
950 ms
649 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 78% of them (75 requests) were addressed to the original Epi.cl, 8% (8 requests) were made to Farm2.staticflickr.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Epi.cl.
Page size can be reduced by 1.5 MB (55%)
2.8 MB
1.2 MB
In fact, the total size of Epi.cl main page is 2.8 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. 65% of websites need less resources to load. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 65.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 65.7 kB or 84% of the original size.
Potential reduce by 17.5 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. Epi images are well optimized though.
Potential reduce by 374.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 374.3 kB or 68% of the original size.
Potential reduce by 1.0 MB
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. Epi.cl needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 88% of the original size.
Number of requests can be reduced by 56 (62%)
91
35
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
epi.cl
2490 ms
wp-emoji-release.min.js
790 ms
flick.css
793 ms
950 ms
layerslider.css
649 ms
css
24 ms
style.css
489 ms
dashicons.min.css
1141 ms
desktop_style.css
810 ms
styles.css
900 ms
comments.css
946 ms
css
35 ms
css
45 ms
bootstrap.css
1416 ms
skin.css
970 ms
quick_newsletter.css
1062 ms
font-awesome.min.css
1573 ms
colorbox.css
1104 ms
flexslider.css
1130 ms
contact.css
1226 ms
style.css
1743 ms
responsive.css
1292 ms
layerslider.css
1298 ms
color.php
2493 ms
wpgform.css
1455 ms
form-basic.min.css
1331 ms
js_composer.min.css
2090 ms
jquery.js
1810 ms
jquery-migrate.min.js
1494 ms
scrollTo.js
1594 ms
jquery.form.min.js
1659 ms
mailchimp.js
1752 ms
core.min.js
1768 ms
datepicker.js
1987 ms
mailchimp-widget-min.js
1910 ms
layerslider.kreaturamedia.jquery.js
1940 ms
greensock.js
1975 ms
layerslider.transitions.js
2069 ms
front_end_script.js
2140 ms
js
42 ms
modernizr.js
1798 ms
jquery-easing-1.3.js
1652 ms
badge_code_v2.gne
91 ms
twitterFetcher_v10_min.js
1637 ms
swfobject.js
1602 ms
scripts.js
1620 ms
social.js
1638 ms
comment-reply.min.js
1562 ms
jquery-transit-modified.js
1719 ms
jquery.colorbox-min.js
1718 ms
jquery.jcarousel.min.js
1696 ms
jquery.flexslider.js
1604 ms
jquery.fitvids.js
1562 ms
custom.js
1563 ms
wp-embed.min.js
1561 ms
js_composer_front.min.js
1490 ms
nuevo_logo.png
800 ms
blank.gif
529 ms
map_1.jpg
531 ms
portal_acceso-30b1shkjc7ekco2in8tts0.jpg
537 ms
DSC0777-2zupo6d6k0ywvzos0jz0g0.jpg
532 ms
15853190196_836eed8129_z-2yfzz1chele5ten6p4uuww.jpg
587 ms
crucero-2yid2r0v5izy8xhm5szdog.jpg
533 ms
IMG_0483-30ryhjp2qeqvotnt4wy8lc.jpg
534 ms
IMG_3586-copia-30r17tw33fir1dlczpepz4.jpg
535 ms
Captura-de-pantalla-2015-12-29-a-las-9.36.25-a.m.-30kqu7zgysbvbdpvm8d2ww.png
536 ms
IMG_3713-30jeja4gjr281akerqz9c0.jpg
537 ms
descripcion_mapa.jpg
941 ms
660x100.jpg
1109 ms
sellos.png
967 ms
denuncialey.jpg
803 ms
proveedores.jpg
805 ms
tarjetas_3.png
946 ms
2Q-AW1e_taO6pHwMXcXW5w.ttf
29 ms
_aijTyevf54tkVDLy-dlnKCWcynf_cDxXwCLxiixG1c.ttf
29 ms
0ihfXUL2emPh0ROJezvraKCWcynf_cDxXwCLxiixG1c.ttf
29 ms
fontawesome-webfont.woff
503 ms
421303796367499264
473 ms
25559170112_50a2f54e74_s.jpg
443 ms
p
446 ms
25651717776_9f9503fd4d_s.jpg
435 ms
25651720026_533a0ab201_s.jpg
436 ms
25651722236_448bb7777c_s.jpg
433 ms
25559179602_8d97562c53_s.jpg
437 ms
25051173863_8464e75804_s.jpg
436 ms
25211812060_d3dcfaea76_s.jpg
439 ms
25374335615_b2efed327b_s.jpg
439 ms
analytics.js
425 ms
skin.css
166 ms
overlay.png
174 ms
collect
23 ms
proxy.jpg
31 ms
blank.gif
165 ms
skin.png
166 ms
shadow.png
161 ms
2000x550px-SLIDEWEB-01.jpg
326 ms
epi.cl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
epi.cl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
epi.cl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epi.cl can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Epi.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.
epi.cl
Open Graph description is not detected on the main page of Epi. 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: