5.5 sec in total
564 ms
4.6 sec
384 ms
Visit centi.pt now to see the best up-to-date CeNTI content for Portugal and also check out these interesting facts you probably never knew about centi.pt
O CeNTI é um instituto de I&DT que se dedica ao estudo e desenvolvimento de produtos nas áreas de nanotecnologia e materiais inteligentes.
Visit centi.ptWe analyzed Centi.pt page load time and found that the first response time was 564 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
centi.pt performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value10.1 s
0/100
25%
Value6.2 s
43/100
10%
Value350 ms
73/100
30%
Value0.004
100/100
15%
Value7.9 s
44/100
10%
564 ms
545 ms
153 ms
329 ms
341 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 71% of them (62 requests) were addressed to the original Centi.pt, 6% (5 requests) were made to Ssl.google-analytics.com and 6% (5 requests) were made to I.vimeocdn.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Centi.pt.
Page size can be reduced by 828.9 kB (13%)
6.5 MB
5.7 MB
In fact, the total size of Centi.pt main page is 6.5 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. 55% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.
Potential reduce by 18.4 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 18.4 kB or 74% of the original size.
Potential reduce by 57.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. CeNTI images are well optimized though.
Potential reduce by 552.3 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 552.3 kB or 67% of the original size.
Potential reduce by 200.7 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. Centi.pt needs all CSS files to be minified and compressed as it can save up to 200.7 kB or 86% of the original size.
Number of requests can be reduced by 58 (71%)
82
24
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CeNTI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
centi.pt
564 ms
www.centi.pt
545 ms
jcemediabox.css
153 ms
style.css
329 ms
widgetkit-05d9046e.css
341 ms
base.css
325 ms
layout.css
426 ms
menus.css
425 ms
modules.css
422 ms
tools.css
458 ms
system.css
458 ms
extensions.css
465 ms
custom.css
597 ms
colorbox.css
591 ms
blue.css
640 ms
droidsans.css
631 ms
yanonekaffeesatz.css
693 ms
yanonekaffeesatz.css
667 ms
style.css
710 ms
print.css
719 ms
droidsans.css
759 ms
css
23 ms
jcemediabox.js
796 ms
mediaobject.js
785 ms
default.js
831 ms
mootools.js
986 ms
caption.js
855 ms
jquery.js
1034 ms
widgetkit-827fd9cd.js
898 ms
warp.js
933 ms
accordionmenu.js
959 ms
dropdownmenu.js
992 ms
template.js
1027 ms
jquery.colorbox-min.js
1067 ms
jquery.cookie.js
1108 ms
search.js
1124 ms
base.css
815 ms
modules.css
745 ms
menus.css
747 ms
layout.css
776 ms
tools.css
796 ms
system.css
800 ms
print.css
553 ms
menus.css
130 ms
tools.css
123 ms
system.css
126 ms
system.css
135 ms
system-all.css
117 ms
lightbox.js
151 ms
mediaelement-and-player.js
155 ms
spotlight.js
132 ms
analytics.js
24 ms
menu_dropdown_level3.png
139 ms
searchbox_magnifier.png
138 ms
ispo_banner_site.jpg
2019 ms
img_2440.jpg
497 ms
peep.png
750 ms
compete_qren_ue.jpg
279 ms
nav.png
342 ms
DroidSans-webfont.woff
340 ms
YDAoLskQQ5MOAgvHUQCcLbvy90DtE_Pg_qiF9bHvTzw.ttf
48 ms
We_iSDqttE3etzfdfhuPRX4NhRhUVU1NOvrEWRXSCoI.ttf
49 ms
ga.js
42 ms
slideshow.js
385 ms
popup.html
416 ms
tooltip.html
416 ms
collect
37 ms
overlay.png
469 ms
60216375
86 ms
60214633
105 ms
60215048
107 ms
60215057
110 ms
__utm.gif
20 ms
player.js
132 ms
player.css
108 ms
ga.js
49 ms
vuid.min.js
119 ms
__utm.gif
34 ms
__utm.gif
7 ms
__utm.gif
11 ms
__utm.gif
13 ms
proxy.html
97 ms
419042617.jpg
200 ms
4994286_60x60.jpg
160 ms
421101409.jpg
112 ms
421088442.jpg
151 ms
419050664.jpg
69 ms
centi.pt accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
centi.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
General
Impact
Issue
Detected JavaScript libraries
centi.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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Centi.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Centi.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.
centi.pt
Open Graph description is not detected on the main page of CeNTI. 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: