5.2 sec in total
406 ms
4 sec
791 ms
Visit echo.or.id now to see the best up-to-date ECHO content for India and also check out these interesting facts you probably never knew about echo.or.id
Visit echo.or.idWe analyzed Echo.or.id page load time and found that the first response time was 406 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
echo.or.id performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
406 ms
506 ms
70 ms
171 ms
231 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Echo.or.id, 22% (16 requests) were made to Apis.google.com and 14% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Ajax.googleapis.com.
Page size can be reduced by 193.8 kB (45%)
429.0 kB
235.2 kB
In fact, the total size of Echo.or.id main page is 429.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. 70% of websites need less resources to load. Images take 207.8 kB which makes up the majority of the site volume.
Potential reduce by 70.9 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 70.9 kB or 80% of the original size.
Potential reduce by 53.9 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, ECHO needs image optimization as it can save up to 53.9 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 6.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 6.2 kB or 13% of the original size.
Potential reduce by 62.8 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. Echo.or.id needs all CSS files to be minified and compressed as it can save up to 62.8 kB or 74% of the original size.
Number of requests can be reduced by 46 (67%)
69
23
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECHO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
echo.or.id
406 ms
wiz.echo.or.id
506 ms
webfont.js
70 ms
3375562265-css_bundle_v2.css
171 ms
authorization.css
231 ms
plusone.js
421 ms
widget.js
156 ms
widgets.js
97 ms
3731899860-widgets.js
187 ms
css
92 ms
icon18_wrench_allbkg.png
101 ms
icon18_edit_allbkg.gif
100 ms
gplus-16.png
109 ms
BSqn7FernLolrt-MFco9Wi3USBnSvpkopQaUR-2r7iU.ttf
85 ms
cb=gapi.loaded_0
302 ms
cb=gapi.loaded_1
298 ms
google_top_exp.js
139 ms
tabs_gradient_light.png
269 ms
share_buttons_20_3.png
129 ms
blank.html
14 ms
friendconnect.js
214 ms
navbar.g
108 ms
icons_peach.png
461 ms
platform:gapi.iframes.style.common.js
327 ms
arrows-light.png
507 ms
ifr
731 ms
cb=gapi.loaded_2
294 ms
fastbutton
271 ms
fastbutton
535 ms
fastbutton
306 ms
load
702 ms
load
531 ms
load
1029 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
242 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
260 ms
cb=gapi.loaded_0
361 ms
cb=gapi.loaded_1
192 ms
fastbutton
334 ms
rs=AGLTcCPRaE3q7fgQA6RhQjCv5lLDbIzLKg
112 ms
postmessageRelay
265 ms
cb=gapi.loaded_0
392 ms
cb=gapi.loaded_1
247 ms
syndication
467 ms
410981478973964288
509 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
427 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
127 ms
ifr
256 ms
3193398744-postmessagerelay.js
214 ms
rpc:shindig_random.js
282 ms
info.json
329 ms
postmessageRelay
157 ms
google.blog.js
220 ms
gadgets-ltr.css
160 ms
cb=gapi.loaded_0
42 ms
proxy.jpg
418 ms
proxy.jpg
643 ms
trash.gif
320 ms
plus.gif
532 ms
smallEnvelope.jpg
531 ms
fc-edit.png
574 ms
do-not-enter.gif
573 ms
unblock.gif
561 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
81 ms
mod_gadget_common__en_US.js
575 ms
mod_gadget_members__en_US.js
561 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
295 ms
pg4wTFhb_normal.png
567 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
525 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
423 ms
echo_normal.jpg
428 ms
e2fddd5c95502430d93d32b47171355e_normal.jpeg
483 ms
B6t36hoCQAAenfp.png
485 ms
proxy.jpg
37 ms
proxy.jpg
28 ms
echo.or.id accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
echo.or.id best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
echo.or.id SEO score
ID
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Echo.or.id can be misinterpreted by Google and other search engines. Our service has detected that 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 Echo.or.id 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.
echo.or.id
Open Graph description is not detected on the main page of ECHO. 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: