10 sec in total
323 ms
9.3 sec
390 ms
Welcome to intelog.org homepage info - get ready to check Intelog best content right away, or after learning these important things about intelog.org
Portal de clipping sobre logística
Visit intelog.orgWe analyzed Intelog.org page load time and found that the first response time was 323 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
intelog.org performance score
323 ms
6775 ms
602 ms
243 ms
392 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 68% of them (108 requests) were addressed to the original Intelog.org, 11% (17 requests) were made to Google-analytics.com and 4% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Intelog.org.
Page size can be reduced by 736.5 kB (61%)
1.2 MB
478.6 kB
In fact, the total size of Intelog.org main page is 1.2 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. 75% 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. Javascripts take 466.5 kB which makes up the majority of the site volume.
Potential reduce by 76.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 12.1 kB, which is 14% 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 76.2 kB or 86% of the original size.
Potential reduce by 156.6 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, Intelog needs image optimization as it can save up to 156.6 kB or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 286.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 286.8 kB or 61% of the original size.
Potential reduce by 216.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. Intelog.org needs all CSS files to be minified and compressed as it can save up to 216.8 kB or 83% of the original size.
Number of requests can be reduced by 74 (49%)
150
76
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intelog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
intelog.org
323 ms
default.asp
6775 ms
prototype.js
602 ms
scriptaculous.js
243 ms
effects.js
392 ms
util.js
263 ms
ajax.js
264 ms
slider.js
364 ms
flash.js
393 ms
swfobject2.js
379 ms
padrao.css
393 ms
show_ads.js
6 ms
webticker_lib.js
132 ms
builder.js
135 ms
dragdrop.js
138 ms
controls.js
139 ms
slider.js
123 ms
sound.js
123 ms
ga.js
4 ms
__utm.gif
32 ms
fundo_corpo.gif
257 ms
fundo_menusup.gif
257 ms
pixel.gif
190 ms
logotipo2.gif
174 ms
icone_logisticaonline.gif
174 ms
banner-logintegrada64.gif
397 ms
fundo_menusup_troncos.gif
279 ms
botao_go.gif
280 ms
icone_rss2.gif
342 ms
botao_email.gif
342 ms
pixel
342 ms
icone_tronco.gif
414 ms
icone_secao.gif
414 ms
fundo_menulat_bottom.gif
460 ms
box_bottom.gif
463 ms
links_rotas.gif
462 ms
links_showmystreet.gif
519 ms
links_flightradar.gif
651 ms
links_ibge.gif
651 ms
links_hora.gif
669 ms
links_jornais.gif
668 ms
icone_agencianoticiasintelog.png
875 ms
icon_facebook.jpg
669 ms
icon_twitter.jpg
669 ms
icone_trans.gif
669 ms
banner-ccr-425.jpg
869 ms
Sincodiv_450X65.jpg
929 ms
TruckPAD450x65_fev16.gif
1048 ms
pixelcolor1.gif
869 ms
bullet1.gif
867 ms
fundo_menulat.gif
906 ms
MostraSelo120.php
129 ms
41 ms
cabecalho_noticia.gif
889 ms
ca-pub-7019648290595415.js
108 ms
zrt_lookup.html
188 ms
show_ads_impl.js
116 ms
urchin.js
67 ms
BIe-dw1kfw8
257 ms
bullet2.gif
832 ms
ANPTrilhos_logo450x65.jpg
894 ms
gif_uprj_450x65.gif
922 ms
poweredby_FFFFFF.gif
175 ms
__utm.gif
101 ms
icone_loading.gif
867 ms
beacon.js
112 ms
__utm.gif
91 ms
rss_top2.jpg
853 ms
FeedsAjax3.asp
895 ms
ads
272 ms
rss_top3.jpg
873 ms
bannerfederasul450x65px.jpg
890 ms
publicidadetop.gif
887 ms
osd.js
35 ms
Pool-CHEP-140px-X-150px-2015-1.gif
987 ms
TruckPAD140x50px.jpg
909 ms
ads
194 ms
ads
346 ms
dinamico1change.asp
1020 ms
rodocredbanner-140x50.gif
917 ms
www-embed-player-vflfNyN_r.css
85 ms
www-embed-player.js
109 ms
base.js
168 ms
Pool-CHEP-140px-X-50px-2015.gif
908 ms
ads
262 ms
dinamico2change.asp
1033 ms
Antf-140.gif
906 ms
complemento.asp
1076 ms
ANPTrilhos_logo140x50.jpg
979 ms
sindiv_140x50px.gif
978 ms
gif_uprj_140x50.gif
1007 ms
abg.js
180 ms
m_js_controller.js
184 ms
googlelogo_color_112x36dp.png
207 ms
6113245558735998059
218 ms
logoconstrutiva.jpg
979 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
117 ms
ad_status.js
133 ms
publicidadebottom.gif
856 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
101 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
101 ms
rss_back.jpg
855 ms
css
167 ms
rss_top.jpg
841 ms
rss_back2.jpg
897 ms
rss_bottom.jpg
911 ms
rss_bottom2.jpg
950 ms
fundo_rodape_barra
955 ms
s
48 ms
x_button_blue2.png
41 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
8 ms
favicon
36 ms
nessie_icon_tiamat_white.png
31 ms
fundo_rodape.gif
757 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
35 ms
FeedsAjax3.asp
571 ms
rss_avancar.jpg
623 ms
rss_bot1.jpg
639 ms
rss_zerohora.gif
680 ms
rss_45graus.gif
675 ms
rss_atarde.gif
676 ms
rss_afp.gif
691 ms
rss_anba.gif
756 ms
rss_ana.gif
771 ms
rss_anp.gif
796 ms
rss_agenciafinanceira.gif
796 ms
rss_apn.gif
812 ms
rss_senado.gif
811 ms
__utm.gif
71 ms
__utm.gif
65 ms
__utm.gif
63 ms
__utm.gif
66 ms
__utm.gif
64 ms
__utm.gif
64 ms
__utm.gif
64 ms
banner-gabardo-140x50.gif
534 ms
banners%20para%20site%20intelog_140x50px.gif
547 ms
anptrilhos_logo140x50.jpg
562 ms
banner_140x50px.jpg
562 ms
banner-140x50.gif
589 ms
pool-chep-140px-x-50px-2015(1).gif
578 ms
logo%20abralog%20-%20140px%20x%2050px.jpg
664 ms
__utm.gif
17 ms
__utm.gif
16 ms
__utm.gif
15 ms
__utm.gif
15 ms
__utm.gif
14 ms
fecomerciop3.gif
626 ms
banner_150x50(1).gif
631 ms
fundo_corpo2.gif
627 ms
LogoABRALOG.jpg
647 ms
enquetes_top.gif
663 ms
enquetes_icon.gif
738 ms
icone_loading2.gif
746 ms
enquetes_bottom.gif
739 ms
Camaralog-banner120x640-4.gif
850 ms
rss_businessweek.gif
611 ms
rss_clarin.gif
639 ms
intelog.org SEO score
PT
PT
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intelog.org can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Intelog.org main page’s claimed encoding is iso-8859-1. 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.
intelog.org
Open Graph description is not detected on the main page of Intelog. 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: