15.8 sec in total
467 ms
11.7 sec
3.7 sec
Click here to check amazing Df content for Chile. Otherwise, check out these important facts you probably never knew about df.cl
Manténgase al día con las últimas noticias en vivo en Diario Financiero. Obtenga información financiera relevante del mundo de la economía en el portal mas importante de Chile.
Visit df.clWe analyzed Df.cl page load time and found that the first response time was 467 ms and then it took 15.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
df.cl performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value77.4 s
0/100
25%
Value24.1 s
0/100
10%
Value9,770 ms
0/100
30%
Value0.277
44/100
15%
Value84.3 s
0/100
10%
467 ms
1066 ms
998 ms
649 ms
401 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 78% of them (98 requests) were addressed to the original Df.cl, 8% (10 requests) were made to Tpc.googlesyndication.com and 5% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source S1.2mdn.net.
Page size can be reduced by 798.0 kB (33%)
2.4 MB
1.6 MB
In fact, the total size of Df.cl main page is 2.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 193.2 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 43.2 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 193.2 kB or 87% of the original size.
Potential reduce by 187.1 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, Df needs image optimization as it can save up to 187.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 173.2 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 173.2 kB or 24% of the original size.
Potential reduce by 244.5 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. Df.cl needs all CSS files to be minified and compressed as it can save up to 244.5 kB or 81% of the original size.
Number of requests can be reduced by 60 (50%)
119
59
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Df. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
df.cl
467 ms
www.df.cl
1066 ms
style.css
998 ms
style_av.css
649 ms
grid.css
401 ms
enquire.js
430 ms
enquire-polyfill.js
451 ms
fullScreen-pollyfill.js
467 ms
iscroll5.js
662 ms
jquery.js
1571 ms
jqueryui.js
2009 ms
modernizr.js
765 ms
ninjaSlider.js
776 ms
requestAnimationFrame.js
791 ms
rutValidator.js
912 ms
script.js
1424 ms
selectivizr.js
921 ms
validizr.js
1076 ms
swfobject.js
1065 ms
Usuario.class.js
1128 ms
DF.class.js
1173 ms
PapelDigital.class.js
1209 ms
jquery.jqplot.min.css
1271 ms
style_inicio.css
1304 ms
jquery.jqplot.min.js
2215 ms
jqplot.highlighter.min.js
1414 ms
jqplot.cursor.min.js
1620 ms
jqplot.dateAxisRenderer.min.js
1541 ms
graphObject.class.js
1601 ms
cd.class.js
1671 ms
Utiles.class.js
1680 ms
Social.class.js
1682 ms
Search.class.js
1676 ms
publicidad.js
1781 ms
sst8_3.js
1807 ms
ima3.js
48 ms
prontusPlayer.min.js
1818 ms
controls.css
1820 ms
adsbygoogle.js
32 ms
ads.css
1806 ms
gpt.js
98 ms
analytics.js
506 ms
capital.svg
444 ms
the-note.svg
488 ms
ed.svg
442 ms
midf-logo-home.svg
469 ms
ajax-loader.gif
480 ms
logo.svg
482 ms
foto_0000000220160217085625.jpg
634 ms
pag1.jpg
634 ms
papeldigital.gif
658 ms
foto_0000000320160217112038.jpg
659 ms
foto_0000000320160217090646.jpg
650 ms
foto_0000000920160216211502.jpg
650 ms
foto_0000000620160216211527.jpg
1206 ms
foto_0000000220160216211533.jpg
1206 ms
foto_0000000420160216211536.jpg
1205 ms
foto_0000000320160217125153.jpg
1126 ms
foto_0000000320160217092535.jpg
1126 ms
foto_0000000320160217115101.jpg
1204 ms
foto_0000000320160217104827.jpg
1199 ms
foto_0000000520160216211511.jpg
1199 ms
more.svg
1331 ms
morningstar.gif
1333 ms
foto_0000000220160128002741.jpg
1333 ms
foto_0000000620160217130049.jpg
1331 ms
foto_0000000320160217075433.jpg
1541 ms
foto_0000000320160217122154.jpg
1331 ms
foto_0000000920160217094934.jpg
1541 ms
foto_0000000720160216211501.jpg
1524 ms
foto_0000000820160216211500.jpg
1624 ms
foto_0000000320160216112319.jpg
1531 ms
foto_0000000820160216211537.jpg
1531 ms
cristian_saieh.jpg
1855 ms
juan_emilio_cheyre.jpg
1671 ms
foto_0000012720160216132000.jpg
1657 ms
foto_0000010420160209152133.jpg
1669 ms
foto_0000011120160129115529.jpg
1656 ms
pubads_impl_80.js
482 ms
pt_sans-web-regular-webfont.woff
1527 ms
pt_sans-web-bold-webfont.woff
1510 ms
foto_0000006420151204134324.jpg
1384 ms
foto_0000012320151022132043.jpg
1396 ms
foto_0000013520151008162530.jpg
1396 ms
foto_0000009220150729135549.jpg
1479 ms
collect
87 ms
collect
617 ms
pt_serif-web-bold-webfont.woff
1701 ms
pt_serif-web-regular-webfont.woff
1685 ms
pt_serif-web-italic-webfont.woff
1684 ms
foto_0000011120150304123452.jpg
1541 ms
foto_0000000220160217101456.jpg
1677 ms
lock.png
1677 ms
container.html
263 ms
noise-bg.png
2054 ms
ads
881 ms
aclk
648 ms
osd.js
447 ms
runtime.js
1952 ms
4566165389889705987
436 ms
runtime.js
2039 ms
13912048428323655919
366 ms
7677910656841071611
1422 ms
728x90_01.png
2500 ms
lidar.js
186 ms
sbhK2lTE.js
1244 ms
16254927740069189047
1721 ms
1845149702147558074
2047 ms
3162691709022090548
1244 ms
6979742927939412507
1553 ms
ca-pub-6745467922636621.js
1370 ms
zrt_lookup.html
2108 ms
show_ads_impl.js
1936 ms
ninjaSlider.js
1668 ms
enquire.js
1267 ms
fullScreen-pollyfill.js
1267 ms
jqueryui.js
2284 ms
jqueryui.css
1331 ms
rutValidator.js
1265 ms
tour-handler.js
1266 ms
cTrvNaRi.html
1028 ms
ninjaSlider.js
367 ms
-Wxc5n6ag8mSVPmrosQZJ6hEHpQooK3Qr1Gxv0lUkvE.js
34 ms
enquire.js
144 ms
fullScreen-pollyfill.js
146 ms
jqueryui.js
1577 ms
df.cl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
df.cl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
df.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
Tap targets are not sized appropriately
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Df.cl can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Df.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.
df.cl
Open Graph data is detected on the main page of Df. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: