Tools & Wizards About Us
jorgeaedo.cl screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

jorgeaedo.cl

JORGE AEDO, LOCUTOR radio, documentales, videos. Locuciones y voz en off

Page Load Speed

3.4 sec in total

First Response

407 ms

Resources Loaded

2.8 sec

Page Rendered

187 ms

jorgeaedo.cl screenshot

About Website

Click here to check amazing JORGE AEDO content. Otherwise, check out these important facts you probably never knew about jorgeaedo.cl

Locucion profesional, Locutor en Chile. Servicio de locuciones y voces en off. Locutores de radio, locutores documentales y locuciones para videos en Chile

Visit jorgeaedo.cl

Key Findings

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

Performance Metrics

jorgeaedo.cl performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.511

15/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

jorgeaedo.cl

407 ms

jorgeaedo.cl

626 ms

jquery-1.7.2.min.js

267 ms

iview.css

359 ms

style.css

359 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 28% of them (19 requests) were addressed to the original Jorgeaedo.cl, 21% (14 requests) were made to Server6.hostradios.com and 12% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 48.1 kB (5%)

Content Size

966.0 kB

After Optimization

917.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jorgeaedo.cl main page is 966.0 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 515.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 37.7 kB

  • Original 50.2 kB
  • After minification 50.2 kB
  • After compression 12.5 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 37.7 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 4.5 kB

  • Original 515.3 kB
  • After minification 510.8 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. JORGE AEDO images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.9 kB

  • Original 393.3 kB
  • After minification 393.3 kB
  • After compression 388.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. This website has mostly compressed JavaScripts.

CSS Optimization

-14%

Potential reduce by 994 B

  • Original 7.2 kB
  • After minification 7.2 kB
  • After compression 6.2 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. Jorgeaedo.cl needs all CSS files to be minified and compressed as it can save up to 994 B or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (57%)

Requests Now

54

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jorgeaedo.cl

jorgeaedo.cl

407 ms

jorgeaedo.cl

jorgeaedo.cl

626 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

267 ms

iview.css

iview.css

359 ms

style.css

style.css

359 ms

raphael-min.js

raphael-min.js

490 ms

jquery.easing.js

jquery.easing.js

387 ms

iview.min.js

iview.min.js

390 ms

flowplayer.js

flowplayer.js

398 ms

estilo_responsive.min.css

estilo_responsive.min.css

478 ms

plusone.js

plusone.js

20 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

bg2.jpg

bg2.jpg

141 ms

logo.png

logo.png

140 ms

numero1.jpg

numero1.jpg

147 ms

holdservice.jpg

holdservice.jpg

140 ms

analytics.js

analytics.js

124 ms

522 ms

embed

embed

328 ms

bg.jpg

bg.jpg

159 ms

webfont.js

webfont.js

44 ms

sdk.js

sdk.js

67 ms

sns.ttf

sns.ttf

162 ms

widgets.js

widgets.js

68 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

46 ms

fastbutton

fastbutton

45 ms

slide02.jpg

slide02.jpg

490 ms

slide03.jpg

slide03.jpg

374 ms

slide01.jpg

slide01.jpg

652 ms

collect

collect

28 ms

css

css

47 ms

js

js

106 ms

postmessageRelay

postmessageRelay

93 ms

sdk.js

sdk.js

43 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

69 ms

va9E4kDNxMZdWfMOD5Vvl4jOazX3dA.ttf

va9E4kDNxMZdWfMOD5Vvl4jOazX3dA.ttf

57 ms

va9B4kDNxMZdWfMOD5VnZKveRhf_Xl7Glw.ttf

va9B4kDNxMZdWfMOD5VnZKveRhf_Xl7Glw.ttf

125 ms

va9B4kDNxMZdWfMOD5VnPKreRhf_Xl7Glw.ttf

va9B4kDNxMZdWfMOD5VnPKreRhf_Xl7Glw.ttf

167 ms

va9B4kDNxMZdWfMOD5VnLK3eRhf_Xl7Glw.ttf

va9B4kDNxMZdWfMOD5VnLK3eRhf_Xl7Glw.ttf

132 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwRmPnws9IqGuw.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4lM3OwRmPnws9IqGuw.ttf

176 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwRmPnws9IqGuw.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4mE3OwRmPnws9IqGuw.ttf

198 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwRmPnws9IqGuw.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4g03OwRmPnws9IqGuw.ttf

176 ms

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwRmPnws9IqGuw.ttf

4UaZrEtFpBI4f1ZSIK9d4LjJ4rQwOwRmPnws9IqGuw.ttf

172 ms

developers.google.com

developers.google.com

1050 ms

settings

settings

164 ms

1380534674-postmessagerelay.js

1380534674-postmessagerelay.js

92 ms

rpc:shindig_random.js

rpc:shindig_random.js

13 ms

js

js

97 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

search.js

search.js

4 ms

geometry.js

geometry.js

8 ms

main.js

main.js

20 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

4 ms

embeds

embeds

32 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.es.html

tweet_button.2f70fb173b9000da126c79afe2098f02.es.html

11 ms

jquery.min.js

jquery.min.js

161 ms

widgets.css

widgets.css

236 ms

flatie.jplayer.skin.css

flatie.jplayer.skin.css

237 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

316 ms

flatie.jplayer.skin.js

flatie.jplayer.skin.js

238 ms

jquery.marquee.min.js

jquery.marquee.min.js

239 ms

animate.css

animate.css

240 ms

art2.gif

art2.gif

393 ms

now5.png

now5.png

314 ms

preload.gif

preload.gif

159 ms

nowplay.php

nowplay.php

266 ms

art.php

art.php

411 ms

player-font.ttf

player-font.ttf

79 ms

Accessibility Review

jorgeaedo.cl accessibility score

72

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jorgeaedo.cl best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

jorgeaedo.cl SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jorgeaedo.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 Jorgeaedo.cl main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

jorgeaedo.cl

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