CFF.CH Tout pour votre mobilité | CFF


cff.ch website information.

cff.ch domain name is registered by .CH top-level domain registry. See the other sites registred in .CH domain zone.

Following name servers are specified for cff.ch domain:

  • ns1.ip-plus.net
  • ns2.ip-plus.net

and probably website cff.ch is hosted by CNNIC-ALIBABA-CN-NET-AP Alibaba (China) Technology Co., Ltd., CN web hosting company. Check the complete list of other most popular websites hosted by CNNIC-ALIBABA-CN-NET-AP Alibaba (China) Technology Co., Ltd., CN hosting company.

According to Alexa traffic rank the highest website cff.ch position was 48838 (in the world). The lowest Alexa rank position was 996592. Now website cff.ch ranked in Alexa database as number 128033 (in the world).

Website cff.ch Desktop speed measurement score (80/100) is better than the results of 69.89% of other sites and shows that the page is performing great on desktop computers.

cff.ch 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 cff.ch (50/100) is better than the results of 33.92% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-08-2024 128,033117
Nov-07-2024 128,1501,747
Nov-06-2024 129,897-2,483
Nov-05-2024 127,4142,173
Nov-04-2024 129,587-3,026
Nov-03-2024 126,5612,791
Nov-02-2024 129,3521,707

Advertisement

cff.ch 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.



cff.ch 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.


Requests of this client are not permitted. Please use https://www.nic.ch/whois/ for queries.

cff.ch server information

Servers Location

IP Address
194.150.245.142
Region
Bern
City
Bern

cff.ch desktop page speed rank

Last tested: 2019-12-14


Desktop Speed Medium
80/100

cff.ch Desktop Speed Test Quick Summary


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

Your page has 5 blocking script resources and 4 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:

https://cdn.app.sbb.ch/base/10.2.6/js/head.min.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…3dc13f8c4e6d58d62cd.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…6ac64746d2cd0005e42.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…85d64746d47ca01dda4.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…81b64746d47ca01dd97.js

Optimize CSS Delivery of the following:

https://cdn.app.sbb.ch/base/10.2.6/css/base.min.css
https://cdn.app.sbb.ch/base/10.2.6/css/header.min.css
https://cdn.app.sbb.ch/base/10.2.6/css/main_homepage.min.css
https://cdn.app.sbb.ch/base/10.2.6/css/footer.min.css

priority - 5 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:

https://sbb-ssl.wemfbox.ch/2004/01/survey.js (expiration not specified)
https://sbb-ssl.wemfbox.ch/blank.gif (expiration not specified)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…3dc13f8c4e6d58d62cd.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…81b64746d47ca01dd97.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…85d64746d47ca01dda4.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…8ce64746d619900d4b6.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…6ac64746d2cd0005e42.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…d7a64746d33eb008dbc.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…0fc64746d1662004e7c.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…2b864746d5828000ea7.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…8db64746d3b150018ee.js (60 minutes)

priority - 2 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 43% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

priority - 2 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 18.2KiB (73% reduction).

Compressing https://www.swisspass.ch/oevlogin/login could save 17.8KiB (73% reduction).
Compressing https://sbb-ssl.wemfbox.ch/2004/01/survey.js could save 339B (48% reduction).

priority - 1 Minify 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 13.2KiB (22% reduction).

Minifying https://www.swisspass.ch/oevlogin/login could save 8.8KiB (37% reduction).
Minifying https://www.sbb.ch/fr/ could save 4.4KiB (12% reduction) after compression.

priority - 1 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 9.7KiB (46% reduction).

Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…2b864746d5828000ea7.js could save 9.2KiB (47% reduction) after compression.
Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…81b64746d47ca01dd97.js could save 268B (34% reduction) after compression.
Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…85d64746d47ca01dda4.js could save 266B (37% reduction) after compression.

cff.ch Desktop Resources

Total Resources70
Number of Hosts13
Static Resources48
JavaScript Resources26
CSS Resources4

cff.ch Desktop Resource Breakdown

cff.ch mobile page speed rank

Last tested: 2018-07-02


Mobile Speed Bad
50/100

cff.ch Mobile Speed Test Quick Summary


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

Your page has 8 blocking script resources and 4 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:

https://cdn.app.sbb.ch/base/7.2.3/js/head.min.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…3dc13f8c4e6d58d62cd.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…12164746d5527004b4d.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…42d64746d75620005d1.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…7eb64746d19e70003ab.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…6ac64746d2cd0005e42.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…85d64746d47ca01dda4.js
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…81b64746d47ca01dd97.js

Optimize CSS Delivery of the following:

https://cdn.app.sbb.ch/base/7.2.3/css/base.min.css
https://cdn.app.sbb.ch/base/7.2.3/css/header.min.css
https://cdn.app.sbb.ch/base/7.2.3/css/main_homepage.min.css
https://cdn.app.sbb.ch/base/7.2.3/css/footer.min.css

priority - 25 Optimize images

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

Optimize the following images to reduce their size by 245.9KiB (20% reduction).

Compressing https://www.sbb.ch/content/dam/internet/sharedimag…1MB.1530254195902.jpeg could save 105.3KiB (22% reduction).
Compressing https://www.sbb.ch/content/dam/internet/sharedimag…ein.1523622589200.jpeg could save 49.1KiB (19% reduction).
Compressing https://www.sbb.ch/content/dam/internet/sharedimag…_V2.1529386904901.jpeg could save 41.2KiB (17% reduction).
Compressing https://www.sbb.ch/content/dam/internet/sharedimag…eis.1519023833731.jpeg could save 28.4KiB (19% reduction).
Compressing https://www.sbb.ch/content/dam/internet/sharedimag…ich.1522246513198.jpeg could save 21.8KiB (16% reduction).

priority - 12 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:

https://sbb-ssl.wemfbox.ch/2004/01/survey.js (expiration not specified)
https://sbb-ssl.wemfbox.ch/blank.gif (expiration not specified)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/175596…3323?v=2.8.18&r=stable (20 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…3dc13f8c4e6d58d62cd.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…7eb64746d19e70003ab.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…81b64746d47ca01dd97.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…85d64746d47ca01dda4.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…8ce64746d619900d4b6.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…6ac64746d2cd0005e42.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…e3d64746d463a0041c3.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…16e64746d6c8e00434c.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…78e64746d72190025b2.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…92564746d2d78000a66.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…96464746d19050008dc.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…12164746d5527004b4d.js (60 minutes)
https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…42d64746d75620005d1.js (60 minutes)

priority - 8 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 46% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

priority - 0 Minify 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 3.8KiB (11% reduction).

Minifying https://www.sbb.ch/fr/ could save 3.8KiB (11% reduction) after compression.

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.9KiB (27% reduction).

Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…92564746d2d78000a66.js could save 384B (24% reduction) after compression.
Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…96464746d19050008dc.js could save 384B (24% reduction) after compression.
Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…81b64746d47ca01dd97.js could save 264B (35% reduction) after compression.
Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…78e64746d72190025b2.js could save 240B (27% reduction) after compression.
Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…42d64746d75620005d1.js could save 227B (33% reduction) after compression.
Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…12164746d5527004b4d.js could save 204B (30% reduction) after compression.
Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…85d64746d47ca01dda4.js could save 165B (36% reduction) after compression.
Minifying https://assets.adobedtm.com/ab1bdbe8e40fa1ba96e607…6ac64746d2cd0005e42.js could save 115B (21% reduction) after compression.

priority - 0 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 336B (48% reduction).

Compressing https://sbb-ssl.wemfbox.ch/2004/01/survey.js could save 336B (48% reduction).

cff.ch Mobile Resources

Total Resources64
Number of Hosts10
Static Resources40
JavaScript Resources31
CSS Resources4

cff.ch Mobile Resource Breakdown

cff.ch mobile page usability

Last tested: 2018-07-02


Mobile Usability Good
99/100

cff.ch 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.

The tap target <div class="mod_timetable_…_form var_home">Horaire et ach…herche élargie</div> is close to 1 other tap targets.

The tap target <form id="checkoutForm">Vérifier les s…herche élargie</form> is close to 2 other tap targets.

The tap target <button type="submit" class="text__primarybutton button">Rechercher</button> is close to 1 other tap targets.

The tap target <div class="mod_homepage_main_teaser">Campagnes et o…–50%</div> is close to 3 other tap targets.
The tap target <a href="/it/home.html" class="mod_langnav_item">it…a in Italiano.</a> and 1 others are close to other tap targets.

cff.ch similar domains

Similar domains:
www.cff.com
www.cff.net
www.cff.org
www.cff.info
www.cff.biz
www.cff.us
www.cff.mobi
www.ff.ch
www.cff.ch
www.xff.ch
www.cxff.ch
www.xcff.ch
www.dff.ch
www.cdff.ch
www.dcff.ch
www.fff.ch
www.cfff.ch
www.fcff.ch
www.vff.ch
www.cvff.ch
www.vcff.ch
www.cf.ch
www.ccf.ch
www.cfcf.ch
www.ccff.ch
www.cdf.ch
www.cfdf.ch
www.crf.ch
www.cfrf.ch
www.crff.ch
www.ctf.ch
www.cftf.ch
www.ctff.ch
www.cgf.ch
www.cfgf.ch
www.cgff.ch
www.cvf.ch
www.cfvf.ch
www.cfc.ch
www.cffc.ch
www.cfd.ch
www.cffd.ch
www.cfr.ch
www.cffr.ch
www.cft.ch
www.cfft.ch
www.cfg.ch
www.cffg.ch
www.cfv.ch
www.cffv.ch

cff.ch 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.


cff.ch 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.