fcc.es website information.
fcc.es domain name is registered by .ES top-level domain registry. See the other sites registred in .ES domain zone.
Following name servers are specified for fcc.es domain:
- nsjc8hos01.telefonica-data.com
- nsalchos01.telefonica-data.com
and probably website fcc.es is hosted by GOOGLE - Google LLC, US web hosting company. Check the complete list of other most popular websites hosted by GOOGLE - Google LLC, US hosting company.
According to Alexa traffic rank the highest website fcc.es position was 21694 (in the world). The lowest Alexa rank position was 992299. Now website fcc.es ranked in Alexa database as number 134516 (in the world).
Website fcc.es Desktop speed measurement score (55/100) is better than the results of 29.37% of other sites shows that the page desktop performance can be improved.
fcc.es Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of fcc.es (45/100) is better than the results of 25.64% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Nov-16-2024 | 134,516 | 3,753 |
| Nov-15-2024 | 138,269 | -611 |
| Nov-14-2024 | 137,658 | -1,248 |
| Nov-13-2024 | 136,410 | 0 |
| Nov-12-2024 | 136,410 | 0 |
| Nov-11-2024 | 136,410 | 0 |
| Nov-10-2024 | 136,410 | -26 |
Advertisement
fcc.es Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
fcc.es whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
fcc.es server information
fcc.es desktop page speed rank
Last tested: 2017-05-20
fcc.es Desktop Speed Test Quick Summary
priority - 61 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 595.9KiB (62% reduction).
Compressing http://www.fcc.es/documents/21301/732744/Red+de+Co…e904ce?t=1491924030332 could save 69.6KiB (84% reduction).
Compressing http://www.fcc.es/documents/21301/29508/Semanadela…ce344e?t=1495197090124 could save 53.2KiB (50% reduction).
Compressing http://www.fcc.es/documents/21301/1415614/Edificio…0f108e?t=1486368003398 could save 48.1KiB (50% reduction).
Compressing http://www.fcc.es/documents/20195/732071/AC_2016_p…24d779?t=1484130156582 could save 47.9KiB (49% reduction).
Compressing http://www.fcc.es/documents/21301/732744/Videos/be…4ac075?t=1484047421689 could save 24.9KiB (44% reduction).
Compressing http://www.fcc.es/documents/20195/732071/AC_2016_p…c326b0?t=1484130157483 could save 24.5KiB (50% reduction).
Compressing http://www.fcc.es/documents/20195/732071/AC_2016_p…5d53a7?t=1484130155121 could save 18.6KiB (50% reduction).
Compressing http://www.fcc.es/documents/21301/732744/Grid_GOBI…f30a1e?t=1483013498556 could save 13KiB (50% reduction).
priority - 15 Reduce server response time
In our test, your server responded in 1.7 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 10 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 6 blocking script resources and 12 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
http://www.fcc.es/html/portlet/journal/js/main.js?…b=6210&t=1494328456000
http://www.fcc.es/html/portlet/journal/js/navigati…b=6210&t=1494328456000
http://www.fcc.es/html/portlet/dynamic_data_lists/…b=6210&t=1494328456000
http://www.fcc.es/html/portlet/dynamic_data_mappin…b=6210&t=1494328456000
http://www.fcc.es/FCC-theme/js/top.js
Optimize CSS Delivery of the following:
http://www.fcc.es/html/css/main.css?browserId=othe…b=6210&t=1383307538000
http://www.fcc.es/html/portlet/asset_publisher/css…b=6210&t=1494328456000
http://www.fcc.es/html/portlet/journal_content/css…b=6210&t=1494328456000
http://www.fcc.es/notifications-portlet/notificati…b=6210&t=1494318463000
http://www.fcc.es/html/portlet/search/css/main.css…b=6210&t=1494328456000
http://www.fcc.es/FCC_InformacionBursatil-portlet/…b=6210&t=1494318463000
http://www.fcc.es/html/portlet/journal/css/main.cs…b=6210&t=1494328456000
http://www.fcc.es/html/portlet/staging_bar/css/mai…b=6210&t=1494328456000
http://www.fcc.es/html/portlet/document_library/cs…b=6210&t=1494328456000
http://www.fcc.es/html/portlet/dynamic_data_mappin…b=6210&t=1494328456000
http://www.fcc.es/FCC-theme/css/main.css?browserId…b=6210&t=1494324144000
priority - 3 Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://www.fcc.es/
http://www.fcc.es/es/
priority - 0 Leverage 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:
fcc.es Desktop Resources
| Total Resources | 77 |
| Number of Hosts | 3 |
| Static Resources | 32 |
| JavaScript Resources | 22 |
| CSS Resources | 14 |
fcc.es Desktop Resource Breakdown
fcc.es mobile page speed rank
Last tested: 2017-05-20
fcc.es Mobile Speed Test Quick Summary
priority - 61 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 595.9KiB (62% reduction).
Compressing http://www.fcc.es/documents/21301/732744/Red+de+Co…e904ce?t=1491924030332 could save 69.6KiB (84% reduction).
Compressing http://www.fcc.es/documents/21301/29508/Semanadela…ce344e?t=1495197090124 could save 53.2KiB (50% reduction).
Compressing http://www.fcc.es/documents/21301/1415614/Edificio…0f108e?t=1486368003398 could save 48.1KiB (50% reduction).
Compressing http://www.fcc.es/documents/20195/732071/AC_2016_p…24d779?t=1484130156582 could save 47.9KiB (49% reduction).
Compressing http://www.fcc.es/documents/21301/732744/Videos/be…4ac075?t=1484047421689 could save 24.9KiB (44% reduction).
Compressing http://www.fcc.es/documents/20195/732071/AC_2016_p…c326b0?t=1484130157483 could save 24.5KiB (50% reduction).
Compressing http://www.fcc.es/documents/20195/732071/AC_2016_p…5d53a7?t=1484130155121 could save 18.6KiB (50% reduction).
Compressing http://www.fcc.es/documents/21301/732744/Grid_GOBI…f30a1e?t=1483013498556 could save 13KiB (50% reduction).
priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 6 blocking script resources and 12 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
http://www.fcc.es/html/portlet/journal/js/main.js?…b=6210&t=1494328710000
http://www.fcc.es/html/portlet/journal/js/navigati…b=6210&t=1494328710000
http://www.fcc.es/html/portlet/dynamic_data_lists/…b=6210&t=1494328710000
http://www.fcc.es/html/portlet/dynamic_data_mappin…b=6210&t=1494328710000
http://www.fcc.es/FCC-theme/js/top.js
Optimize CSS Delivery of the following:
http://www.fcc.es/html/css/main.css?browserId=othe…b=6210&t=1383307538000
http://www.fcc.es/html/portlet/asset_publisher/css…b=6210&t=1494328710000
http://www.fcc.es/html/portlet/journal_content/css…b=6210&t=1494328710000
http://www.fcc.es/notifications-portlet/notificati…b=6210&t=1494319631000
http://www.fcc.es/html/portlet/search/css/main.css…b=6210&t=1494328710000
http://www.fcc.es/FCC_InformacionBursatil-portlet/…b=6210&t=1494319631000
http://www.fcc.es/html/portlet/journal/css/main.cs…b=6210&t=1494328710000
http://www.fcc.es/html/portlet/staging_bar/css/mai…b=6210&t=1494328710000
http://www.fcc.es/html/portlet/document_library/cs…b=6210&t=1494328710000
http://www.fcc.es/html/portlet/dynamic_data_mappin…b=6210&t=1494328710000
http://www.fcc.es/FCC-theme/css/main.css?browserId…b=6210&t=1494321700000
priority - 24 Reduce server response time
In our test, your server responded in 1.8 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 10 Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://www.fcc.es/
http://www.fcc.es/es/
priority - 1 Leverage 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:
fcc.es Mobile Resources
| Total Resources | 78 |
| Number of Hosts | 3 |
| Static Resources | 33 |
| JavaScript Resources | 23 |
| CSS Resources | 14 |
fcc.es Mobile Resource Breakdown
fcc.es mobile page usability
Last tested: 2017-05-20
fcc.es Mobile Usability Test Quick Summary
priority - 0 Size 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.
<a href="http://www.som…-N1/index.html"></a> is close to 1 other tap targets.fcc.es similar domains
www.fcc.net
www.fcc.org
www.fcc.info
www.fcc.biz
www.fcc.us
www.fcc.mobi
www.cc.es
www.fcc.es
www.ccc.es
www.fccc.es
www.cfcc.es
www.dcc.es
www.fdcc.es
www.dfcc.es
www.rcc.es
www.frcc.es
www.rfcc.es
www.tcc.es
www.ftcc.es
www.tfcc.es
www.gcc.es
www.fgcc.es
www.gfcc.es
www.vcc.es
www.fvcc.es
www.vfcc.es
www.fc.es
www.fxc.es
www.fcxc.es
www.fxcc.es
www.fdc.es
www.fcdc.es
www.ffc.es
www.fcfc.es
www.ffcc.es
www.fvc.es
www.fcvc.es
www.fcx.es
www.fccx.es
www.fcd.es
www.fccd.es
www.fcf.es
www.fccf.es
www.fcv.es
www.fccv.es
fcc.es Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
fcc.es TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.