4.4 sec in total
365 ms
3.9 sec
130 ms
Visit ine.pt now to see the best up-to-date Ine content for Portugal and also check out these interesting facts you probably never knew about ine.pt
Visit ine.ptWe analyzed Ine.pt page load time and found that the first response time was 365 ms 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.
ine.pt performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value14.3 s
0/100
25%
Value13.1 s
2/100
10%
Value480 ms
60/100
30%
Value0.419
23/100
15%
Value13.2 s
12/100
10%
365 ms
619 ms
286 ms
122 ms
364 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 96% of them (86 requests) were addressed to the original Ine.pt, 2% (2 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (796 ms) belongs to the original domain Ine.pt.
Page size can be reduced by 342.3 kB (51%)
669.4 kB
327.1 kB
In fact, the total size of Ine.pt main page is 669.4 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. 35% of websites need less resources to load. Javascripts take 350.1 kB which makes up the majority of the site volume.
Potential reduce by 33.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. This page needs HTML code to be minified as it can gain 8.3 kB, which is 20% 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 33.5 kB or 81% of the original size.
Potential reduce by 34.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. Obviously, Ine needs image optimization as it can save up to 34.8 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 224.1 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 224.1 kB or 64% of the original size.
Potential reduce by 50.0 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. Ine.pt needs all CSS files to be minified and compressed as it can save up to 50.0 kB or 81% of the original size.
Number of requests can be reduced by 43 (52%)
83
40
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ine. 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 14 to 1 for CSS and as a result speed up the page load time.
ine.pt
365 ms
www.ine.pt
619 ms
xmain
286 ms
c_config.js
122 ms
c_smartmenus.js
364 ms
css_html13550535_any.css
339 ms
css_html13681556_any.css
348 ms
css_html13870455_any.css
361 ms
css_html13550651_any.css
373 ms
css_html13865052_any.css
374 ms
css_html13851648_any.css
449 ms
css_html13668508_any.css
577 ms
swfobject.js
481 ms
stats.js
481 ms
h_arrow_white.gif
122 ms
v_arrow_black.gif
121 ms
v_arrow_white.gif
191 ms
n_logotipo.gif
240 ms
n_bt_pesquisa.gif
124 ms
n_btutilizador.gif
118 ms
xst_loadimg.jsp
125 ms
xst_loadimg.jsp
128 ms
xst_loadimg.jsp
121 ms
ytb_slider.png
131 ms
rss_slider.png
232 ms
pinterest.png
232 ms
n_sep_seta.gif
241 ms
n_icon_RSS.gif
243 ms
xst_loadimg.jsp
371 ms
xst_loadimg.jsp
374 ms
logo_ine_mobile.png
342 ms
stat_data_hand.png
346 ms
avail.png
360 ms
av_soon.png
361 ms
google_play.png
455 ms
app_store.png
462 ms
amazon_app.png
480 ms
windows_mobile.png
482 ms
qdv2_en.png
489 ms
revstat_grid_2.gif
493 ms
access.gif
567 ms
wcag1AA.png
576 ms
xst_loadimg.jsp
604 ms
xst_loadimg.jsp
605 ms
xst_loadimg.jsp
611 ms
xst_loadimg.jsp
616 ms
xst_loadimg.jsp
682 ms
index_en.html
689 ms
index.html
714 ms
n_seta_menu.gif
715 ms
n_join_inicial.gif
720 ms
n_join.gif
726 ms
n_join_final.gif
789 ms
n_setinha_azul.gif
788 ms
data.jsp
737 ms
linha_sup.gif
728 ms
linha_inf.gif
735 ms
linha_esq.gif
738 ms
linha_dir.gif
782 ms
canto_inf_esq.gif
796 ms
canto_inf_dir.gif
736 ms
canto_sup_esq.gif
740 ms
canto_sup_dir.gif
736 ms
styles.css
288 ms
iview.css
326 ms
style.css
347 ms
jquery-1.7.1.min.js
750 ms
raphael-min.js
769 ms
jquery.easing.js
401 ms
iview.js
528 ms
jquery.fullscreen.js
436 ms
jquery.min.js
56 ms
slick.min.js
547 ms
style.css
492 ms
slick.css
520 ms
slick-theme.css
613 ms
css
63 ms
reset.css
409 ms
Portal012.png
124 ms
Portal001.png
118 ms
Portal002.png
123 ms
Portal003.png
116 ms
Portal004.png
178 ms
Portal005.png
181 ms
ajax-loader.gif
228 ms
slick.woff
232 ms
btn_transp.png
156 ms
topo_n.png
491 ms
mZSs29ggGoaqrCNB3kDfZQ.woff
91 ms
trnbTfqisuuhRVI3i45C5w.woff
113 ms
ine.pt accessibility score
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
Buttons do not have an accessible 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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
ine.pt 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ine.pt SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ine.pt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ine.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.
ine.pt
Open Graph description is not detected on the main page of Ine. 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: