FCT.PT Fundação para a Ciência e a Tecnologia - FCT

fct.pt Website Information

Daily Unique Visits: 22,344

Daily Page Views: 134,064

Income Per Day: $268

Estimated Value: $192,960

This website is located in Portugal and is using following IP address 193.137.236.180. See the complete list of popular websites hosted in Portugal.

fct.pt is registered under .PT top-level domain. Please check other sites in .PT zone.

Website fct.pt is using the following name servers:

  • ns03.fccn.pt
  • ns.fct.pt
  • ns02.fccn.pt

and is probably hosted by Fundacao para a Ciencia e a Tecnologia, I.P.. See the full list of other websites hosted by Fundacao para a Ciencia e a Tecnologia, I.P..

The highest website fct.pt position in Alexa rank database was 11056 and the lowest rank position was 946394. Current position of fct.pt in Alexa rank database is 64188.

Desktop speed score of fct.pt (70/100) is better than the results of 50.91% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of fct.pt (63/100) is better than the results of 9.16% of other sites and means that the page is not mobile-friendly.

Mobile speed score of fct.pt (62/100) is better than the results of 59.44% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

fct.pt Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


fct.pt whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


fct.pt server information

Servers Location

fct.pt desktop page speed rank

Last tested: 2016-12-15


Desktop Speed Medium
70/100

fct.pt Desktop Speed Test Quick Summary


priority - 33Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 323.1KiB (73% reduction).

Compressing http://www.fct.pt/images/banners/F0174PT_estagiostecnologicos_PT.jpg could save 99.4KiB (78% reduction).
Compressing http://www.fct.pt/images/banners/F0165PT_PremioFernandoGil2017_pt.jpg could save 92.3KiB (71% reduction).
Compressing http://www.fct.pt/images/banners/F0176PT_bolsas_fullbright_PT.jpg could save 70.4KiB (74% reduction).
Compressing http://www.fct.pt/images/banners/F0172PT_Debate_PT.jpg could save 57.2KiB (74% reduction).
Compressing http://www.fct.pt/images/logos_promo.png could save 1.1KiB (18% reduction).
Compressing http://www.fct.pt/images/bg_top_right2.gif could save 1KiB (86% reduction).
Compressing http://www.fct.pt/images/FCT_logo_2014.png could save 996B (20% reduction).
Compressing http://www.fct.pt/images/orbit/bullets_alt.png could save 872B (82% reduction).

priority - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.fct.pt/javascript/jquery/jquery.min.js
http://www.fct.pt/scripts/jquery.orbit.min.js
http://www.fct.pt/scripts/clear.js
http://www.fct.pt/scripts/ga.js

Optimize CSS Delivery of the following:

http://www.fct.pt/css/screen.css
http://www.fct.pt/css/orbit.css

priority - 3Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.google-analytics.com/analytics.js (2 hours)
http://www.fct.pt/css/orbit.css (24 hours)
http://www.fct.pt/css/print.css (24 hours)
http://www.fct.pt/css/screen.css (24 hours)
http://www.fct.pt/javascript/jquery/jquery.min.js (24 hours)
http://www.fct.pt/scripts/clear.js (24 hours)
http://www.fct.pt/scripts/ga.js (24 hours)
http://www.fct.pt/scripts/jquery.orbit.min.js (24 hours)

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.4KiB (19% reduction).

Minifying http://www.fct.pt/css/screen.css could save 1.4KiB (19% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 642B (12% reduction).

Minifying http://www.fct.pt/ could save 642B (12% reduction) after compression.

fct.pt Desktop Resource Breakdown

Total Resources25
Number of Hosts3
Static Resources22
JavaScript Resources5
CSS Resources3

fct.pt mobile page speed rank

Last tested: 2016-12-15


Mobile Speed Bad
62/100

fct.pt Mobile Speed Test Quick Summary


priority - 33Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 323.1KiB (73% reduction).

Compressing http://www.fct.pt/images/banners/F0174PT_estagiostecnologicos_PT.jpg could save 99.4KiB (78% reduction).
Compressing http://www.fct.pt/images/banners/F0165PT_PremioFernandoGil2017_pt.jpg could save 92.3KiB (71% reduction).
Compressing http://www.fct.pt/images/banners/F0176PT_bolsas_fullbright_PT.jpg could save 70.4KiB (74% reduction).
Compressing http://www.fct.pt/images/banners/F0172PT_Debate_PT.jpg could save 57.2KiB (74% reduction).
Compressing http://www.fct.pt/images/logos_promo.png could save 1.1KiB (18% reduction).
Compressing http://www.fct.pt/images/bg_top_right2.gif could save 1KiB (86% reduction).
Compressing http://www.fct.pt/images/FCT_logo_2014.png could save 996B (20% reduction).
Compressing http://www.fct.pt/images/orbit/bullets_alt.png could save 872B (82% reduction).

priority - 24Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.fct.pt/javascript/jquery/jquery.min.js
http://www.fct.pt/scripts/jquery.orbit.min.js
http://www.fct.pt/scripts/clear.js
http://www.fct.pt/scripts/ga.js

Optimize CSS Delivery of the following:

http://www.fct.pt/css/screen.css
http://www.fct.pt/css/orbit.css

priority - 5Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.google-analytics.com/analytics.js (2 hours)
http://www.fct.pt/css/orbit.css (24 hours)
http://www.fct.pt/css/print.css (24 hours)
http://www.fct.pt/css/screen.css (24 hours)
http://www.fct.pt/javascript/jquery/jquery.min.js (24 hours)
http://www.fct.pt/scripts/clear.js (24 hours)
http://www.fct.pt/scripts/ga.js (24 hours)
http://www.fct.pt/scripts/jquery.orbit.min.js (24 hours)

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 1.4KiB (19% reduction).

Minifying http://www.fct.pt/css/screen.css could save 1.4KiB (19% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 642B (12% reduction).

Minifying http://www.fct.pt/ could save 642B (12% reduction) after compression.

fct.pt Mobile Resource Breakdown

Total Resources25
Number of Hosts3
Static Resources22
JavaScript Resources5
CSS Resources3

fct.pt mobile page usability

Last tested: 2016-12-15


Mobile Usability Bad
63/100

fct.pt Mobile Usability Test Quick Summary


priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Estatísticas and 4 others render only 4 pixels tall (11 CSS pixels).

EM DESTAQUE and 2 others render only 5 pixels tall (12 CSS pixels).

12-12-2016 and 2 others render only 4 pixels tall (11 CSS pixels).

FCT divulga do…ego Científico and 2 others render only 6 pixels tall (16 CSS pixels).

A FCT e a Comi…1 de dezembro. and 1 others render only 5 pixels tall (12 CSS pixels).

Documento Orie…anciamento FCT renders only 5 pixels tall (13 CSS pixels).

Mais calendário › and 2 others render only 4 pixels tall (11 CSS pixels).

Bolsas de Dout…Língua Falada) and 9 others render only 5 pixels tall (12 CSS pixels).

Termina em 15-12-2016 and 4 others render only 4 pixels tall (10 CSS pixels).

15 and 4 others render only 5 pixels tall (13 CSS pixels).

dez and 4 others render only 4 pixels tall (11 CSS pixels).

Concursos FCT and 4 others render only 4 pixels tall (11 CSS pixels).

PT | EN renders only 3 pixels tall (9 CSS pixels).

mapa do site and 2 others render only 4 pixels tall (10 CSS pixels).

Registo and 1 others render only 4 pixels tall (10 CSS pixels).

A FCT é a agên…ia e inovação. renders only 7 pixels tall (18 CSS pixels).

ÁREAS DE AÇÃO and 1 others render only 5 pixels tall (12 CSS pixels).

Infraestrutura…e Investigação and 20 others render only 5 pixels tall (12 CSS pixels).

©2016 · Fundaç…e a Tecnologia renders only 4 pixels tall (10 CSS pixels).

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 8Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/apoios/">Apoios</a> and 4 others are close to other tap targets.

The tap target <li class="">0</li> and 2 others are close to other tap targets.

The tap target <li class="active">1</li> is close to 4 other tap targets.

The tap target <a href="/noticias">Em destaque</a> and 1 others are close to other tap targets.

The tap target <a href="noticias/index.phtml.pt">Mais notícias ›</a> and 1 others are close to other tap targets.

The tap target <a href="index.phtml.en">PT | EN</a> is close to 2 other tap targets.

The tap target <input id="search" type="text" name="search" class="textinput clearme"> is close to 1 other tap targets.

The tap target <input id="submit" type="image" name="submit" class="submit"> is close to 2 other tap targets.

The tap target <a href="/contactos.phtml">contactos</a> and 2 others are close to other tap targets.

The tap target <a href="https://sig.fct.pt/fctsig/">Login</a> and 1 others are close to other tap targets.

The tap target <a href="rss/feed_PT.php"></a> and 1 others are close to other tap targets.

The tap target <a href="/apoios/bolsas/">Bolsas e Formação Avançada</a> and 20 others are close to other tap targets.

priority - 3Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 992 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="index.phtml.en">PT | EN</a> falls outside the viewport.
The element <input id="submit" type="image" name="submit" class="submit"> falls outside the viewport.
The element <div id="minimenu">contactos   FA…mapa do site</div> falls outside the viewport.
The element <a href="/registo">Registo</a> falls outside the viewport.
The element <div class="hero">A FCT é a agên…ia e inovação.</div> falls outside the viewport.
The element <ul>Bolsas e Forma…I&amp;I 2014-2020</ul> falls outside the viewport.
The element <ul>Consulta a Pro…s e Estratégia</ul> falls outside the viewport.
The element <p>©2016 · Fundaç…e a Tecnologia</p> falls outside the viewport.

fct.pt HTML validation

Errors

End tag “div” seen, but there were open elements.

Line: 196 Column: 21 - 26
"... </div> ..."

Unclosed element “ul”.

Line: 186 Column: 25 - 28
"... <ul> ..."

fct.pt similar domains

Similar domains:
www.fct.com
www.fct.net
www.fct.org
www.fct.info
www.fct.biz
www.fct.us
www.fct.mobi
www.ct.pt
www.fct.pt
www.cct.pt
www.fcct.pt
www.cfct.pt
www.dct.pt
www.fdct.pt
www.dfct.pt
www.rct.pt
www.frct.pt
www.rfct.pt
www.tct.pt
www.ftct.pt
www.tfct.pt
www.gct.pt
www.fgct.pt
www.gfct.pt
www.vct.pt
www.fvct.pt
www.vfct.pt
www.ft.pt
www.fxt.pt
www.fcxt.pt
www.fxct.pt
www.fdt.pt
www.fcdt.pt
www.fft.pt
www.fcft.pt
www.ffct.pt
www.fvt.pt
www.fcvt.pt
www.fc.pt
www.fcr.pt
www.fctr.pt
www.fcrt.pt
www.fcf.pt
www.fctf.pt
www.fcg.pt
www.fctg.pt
www.fcgt.pt
www.fcy.pt
www.fcty.pt
www.fcyt.pt

fct.pt Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


fct.pt TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.