6 sec in total
2 sec
3.8 sec
202 ms
Visit ina.pt now to see the best up-to-date INA content for Portugal and also check out these interesting facts you probably never knew about ina.pt
O INA desenvolve relações de cooperação com outras entidades que atuam no domínio da Administração Pública, numa perspetiva de complementaridade de vocação e experiências, aperfeiçoando e dinamizando ...
Visit ina.ptWe analyzed Ina.pt page load time and found that the first response time was 2 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ina.pt performance score
1981 ms
213 ms
221 ms
222 ms
66 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 88% of them (71 requests) were addressed to the original Ina.pt, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ina.pt.
Page size can be reduced by 1.1 MB (55%)
2.0 MB
926.9 kB
In fact, the total size of Ina.pt main page is 2.0 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. 50% of websites need less resources to load. Images take 718.5 kB which makes up the majority of the site volume.
Potential reduce by 52.0 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 52.0 kB or 81% of the original size.
Potential reduce by 116.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. Obviously, INA needs image optimization as it can save up to 116.5 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 449.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 449.8 kB or 68% of the original size.
Potential reduce by 504.3 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. Ina.pt needs all CSS files to be minified and compressed as it can save up to 504.3 kB or 84% of the original size.
Number of requests can be reduced by 38 (49%)
78
40
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
ina.pt
1981 ms
css_556fc.css
213 ms
template.css.php
221 ms
css_e037d.css
222 ms
jquery.min.js
66 ms
jquerynoconflict.js
214 ms
js_eb0d9.js
610 ms
js_bc4c3.js
896 ms
js_385d6.js
462 ms
js_5b53f.js
325 ms
videobox.css
332 ms
EUCookieDirective.js
226 ms
font-awesome.css
352 ms
colorbox1.min.css
229 ms
bootstrap.min.css
514 ms
bootstrap-responsive.min.css
361 ms
style.min.css
387 ms
system.css
463 ms
general.css
472 ms
style.css
498 ms
addons.css
502 ms
template.css
582 ms
layout.css
572 ms
usertools.css
597 ms
css3.css
617 ms
mega.css
615 ms
k2.css
810 ms
typo.css
708 ms
template.css
737 ms
layout-mobile.css
727 ms
layout-mobile-port.css
727 ms
layout-tablet.css
779 ms
layout.css
813 ms
mega.css
840 ms
mod_jasidenews.css
835 ms
system.css
395 ms
continue_button.png
135 ms
social_icon_fb.png
135 ms
social_icon_yt.png
136 ms
social_icon_instg.jpg
133 ms
social_icon_rss.png
134 ms
45_37a06e4a72d6cb27621f1ed829bbee81_s.jpg
366 ms
70_3749aaa8ee129d7e919bddcc7e09cd36_s.jpg
436 ms
61_00d9b1e39f02d57be65ad2a9a6eaa3b8_s.jpg
453 ms
63_9415f9bcd76598f9c08127db1641b596_s.jpg
461 ms
56_d3b3799d6611d677944f5f86a500beb3_s.jpg
366 ms
45_37a06e4a72d6cb27621f1ed829bbee81_t.jpg
235 ms
70_3749aaa8ee129d7e919bddcc7e09cd36_t.jpg
365 ms
61_00d9b1e39f02d57be65ad2a9a6eaa3b8_t.jpg
452 ms
63_9415f9bcd76598f9c08127db1641b596_t.jpg
462 ms
56_d3b3799d6611d677944f5f86a500beb3_t.jpg
467 ms
RAF2016_140_110.jpg
544 ms
imagem_noticias_cadapi2016_140_110.jpg
564 ms
cartaz_exp_sp21_2016_140_110.jpg
561 ms
Govint_140_110.jpg
572 ms
imagem_BB_noticia_2016_140_110.jpg
624 ms
B_balcaounico.jpg
576 ms
receber_news.JPG
652 ms
B_pf.jpg
671 ms
ina_2015_link_rapido.jpg
668 ms
B_bep.jpg
678 ms
B_pepac.jpg
689 ms
ROADSHOW_valorizacao.jpg
733 ms
BB2016.jpg
762 ms
repapp_roxo.jpg
783 ms
B_elearning.jpg
783 ms
aenor2016.PNG
897 ms
icon-search.png
783 ms
logo.png
823 ms
loading.gif
794 ms
arrow.png
811 ms
ga.js
26 ms
er_DV4Rb-9Y
93 ms
overlay.png
764 ms
__utm.gif
15 ms
www-embed-player-vflfNyN_r.css
21 ms
www-embed-player.js
43 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
40 ms
ad_status.js
39 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
40 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
41 ms
ina.pt SEO score
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ina.pt 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 Ina.pt 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.
ina.pt
Open Graph data is detected on the main page of INA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: