palliative.ch Website Information
Daily Unique Visits: 864
Daily Page Views: 1,728
Income Per Day: $5
Estimated Value: $1,200
palliative.ch is registered under .CH top-level domain. Please check other sites in .CH zone.
No name server records were found.
and is probably hosted by NovaTrend Services GmbH. See the full list of other websites hosted by NovaTrend Services GmbH.
The highest website palliative.ch position in Alexa rank database was 21658 and the lowest rank position was 996210. Current position of palliative.ch in Alexa rank database is 829864.
Desktop speed score of palliative.ch (84/100) is better than the results of 78.07% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of palliative.ch (64/100) is better than the results of 11.2% of other sites and means that the page is not mobile-friendly.
Mobile speed score of palliative.ch (75/100) is better than the results of 84.42% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
palliative.ch 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.
palliative.ch 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.
palliative.ch server information
Servers Location
palliative.ch desktop page speed rank
Last tested: 2019-04-06
palliative.ch Desktop Speed Test Quick Summary
priority - 8Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 81.2KiB (37% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…ruehling/spring_02.jpg could save 18.7KiB (48% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…ruehling/spring_01.jpg could save 12.5KiB (49% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…ruehling/spring_03.jpg could save 11.4KiB (52% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/palliativkarte_small.png could save 9.2KiB (15% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…ome/SQPC_news_home.jpg could save 3.2KiB (21% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…Home/betroffene_01.jpg could save 2.8KiB (22% reduction).
Compressing https://www.palliative.ch/fileadmin/_processed_/3/…400x400_b8f1642eb9.png could save 182B (18% reduction).
Compressing https://www.palliative.ch/fileadmin/template/pix/palliative/arrow_right.png could save 150B (24% reduction).
priority - 3Avoid 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.
https://www.palliative.ch/
https://www.palliative.ch/de/palliative-ch/
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:
https://www.palliative.ch/fileadmin/template/palliative/brainjarmenu.js (24 hours)
https://www.palliative.ch/fileadmin/templates/main/css/main.css?1537534692 (24 hours)
https://www.palliative.ch/fileadmin/templates/main…de-home.css?1537534692 (24 hours)
https://www.palliative.ch/fileadmin/templates/main…upgrade.css?1537534692 (24 hours)
https://www.palliative.ch/fileadmin/templates/main…omslider.js?1537534692 (24 hours)
https://www.palliative.ch/typo3temp/assets/css/eabd1418f5.css?1548173716 (24 hours)
priority - 2Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
priority - 0Reduce server response time
In our test, your server responded in 0.23 seconds.
priority - 0Minify 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.7KiB (48% reduction).
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 385B (21% reduction).
Minifying https://www.palliative.ch/fileadmin/templates/main…upgrade.css?1537534692 could save 122B (29% reduction) after compression.
Minifying https://www.palliative.ch/fileadmin/templates/main…de-home.css?1537534692 could save 101B (22% reduction) after compression.
palliative.ch Desktop Resource Breakdown
Total Resources | 30 |
Number of Hosts | 6 |
Static Resources | 26 |
JavaScript Resources | 5 |
CSS Resources | 5 |
palliative.ch mobile page speed rank
Last tested: 2019-04-06
palliative.ch Mobile Speed Test Quick Summary
priority - 10Avoid 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.
https://www.palliative.ch/
https://www.palliative.ch/de/palliative-ch/
priority - 8Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 81.2KiB (37% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…ruehling/spring_02.jpg could save 18.7KiB (48% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…ruehling/spring_01.jpg could save 12.5KiB (49% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…ruehling/spring_03.jpg could save 11.4KiB (52% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/palliativkarte_small.png could save 9.2KiB (15% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…ome/SQPC_news_home.jpg could save 3.2KiB (21% reduction).
Compressing https://www.palliative.ch/fileadmin/user_upload/pa…Home/betroffene_01.jpg could save 2.8KiB (22% reduction).
Compressing https://www.palliative.ch/fileadmin/_processed_/3/…400x400_b8f1642eb9.png could save 182B (18% reduction).
Compressing https://www.palliative.ch/fileadmin/template/pix/palliative/arrow_right.png could save 150B (24% reduction).
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
priority - 4Leverage 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://www.palliative.ch/fileadmin/template/palliative/brainjarmenu.js (24 hours)
https://www.palliative.ch/fileadmin/templates/main/css/main.css?1537534692 (24 hours)
https://www.palliative.ch/fileadmin/templates/main…de-home.css?1537534692 (24 hours)
https://www.palliative.ch/fileadmin/templates/main…upgrade.css?1537534692 (24 hours)
https://www.palliative.ch/fileadmin/templates/main…omslider.js?1537534692 (24 hours)
https://www.palliative.ch/typo3temp/assets/css/eabd1418f5.css?1548173716 (24 hours)
priority - 1Reduce server response time
In our test, your server responded in 0.26 seconds.
priority - 0Minify 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.7KiB (48% reduction).
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 385B (21% reduction).
Minifying https://www.palliative.ch/fileadmin/templates/main…upgrade.css?1537534692 could save 122B (29% reduction) after compression.
Minifying https://www.palliative.ch/fileadmin/templates/main…de-home.css?1537534692 could save 101B (22% reduction) after compression.
palliative.ch Mobile Resource Breakdown
Total Resources | 30 |
Number of Hosts | 6 |
Static Resources | 26 |
JavaScript Resources | 5 |
CSS Resources | 5 |
palliative.ch mobile page usability
Last tested: 2019-04-06
palliative.ch Mobile Usability Test Quick Summary
priority - 36Use 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.
Sprachen:
and 5 others render only 5 pixels tall (12 CSS pixels).PUBLIKUM
and 1 others render only 5 pixels tall (12 CSS pixels).Inserieren
and 3 others render only 5 pixels tall (12 CSS pixels).PALLIATIVE CARE
and 3 others render only 7 pixels tall (19 CSS pixels).palliativkarte.ch
and 1 others render only 7 pixels tall (17 CSS pixels).neues Angebot…palliative ch
renders only 5 pixels tall (13 CSS pixels).WO UND WIE FIN…LLIATIVE CARE?
and 1 others render only 7 pixels tall (17 CSS pixels).Holen Sie sich…Ihren Kanton.
and 2 others render only 5 pixels tall (12 CSS pixels).Kanton wählen...
renders only 5 pixels tall (12 CSS pixels).FOLGEN SIE UNS AUF FACEBOOK
and 3 others render only 7 pixels tall (17 CSS pixels).JOB BÖRSE
renders only 7 pixels tall (17 CSS pixels).QUALITÉPALLIATIVE
renders only 7 pixels tall (17 CSS pixels).Der Hauptzweck…lliative Care.
renders only 5 pixels tall (12 CSS pixels).Sponsored by
renders only 5 pixels tall (12 CSS pixels).Ihr Partner für Pflegebetten
and 2 others render only 5 pixels tall (12 CSS pixels).palliativkarte.ch
and 3 others render only 7 pixels tall (17 CSS pixels).zu Palliative…wandten Themen
and 1 others render only 5 pixels tall (14 CSS pixels).15.03.2019
and 4 others render only 5 pixels tall (14 CSS pixels).Geschäftsberic…30. Juni 2018
and 4 others render only 7 pixels tall (17 CSS pixels).Mehr News
renders only 5 pixels tall (14 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 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 1,050 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<path id="Blue_1_">
falls outside the viewport.The element
<path id="f">
falls outside the viewport.The element
<a href="/fr/palliative-ch/">FR</a>
falls outside the viewport.The element
<a href="/it/palliative-ch/">IT</a>
falls outside the viewport.The element
<a href="/en/available-languages/" class="linkclass">EN</a>
falls outside the viewport.The element
<input type="text" name="tx_indexedsearch[sword]" class="searchbox-sword">
falls outside the viewport.The element
<input type="image" name="search" class="searchbox-button">
falls outside the viewport.The element
<a href="/de/ueber-uns/kontakt/" class="linkclass">Kontakt</a>
falls outside the viewport.The element
<a href="/de/fachbereic…serat-website/" class="linkclass">Inserieren</a>
falls outside the viewport.The element
<a href="/de/fachbereich/jobs/angebote/" class="linkclass">Jobs</a>
falls outside the viewport.The element
<a href="/de/ueber-uns/spenden/" class="linkclass">Spenden</a>
falls outside the viewport.The element
<div></div>
falls outside the viewport.The element
<div class="menuBar">Palliative Car…boteFachportal</div>
falls outside the viewport.The element
<span class="title_smaller">WO UND WIE FIN…LLIATIVE CARE?</span>
falls outside the viewport.The element
<span class="copytextSmaller">Holen Sie sich…Ihren Kanton.</span>
falls outside the viewport.The element
<div class="dropdownBar">Kanton wählen...</div>
falls outside the viewport.The element
<a href="/de/ueber-uns/…tglied-werden/">FÖRDERMITGLIED WERDEN</a>
falls outside the viewport.The element
<p class="title_smaller">PATIENTEN- VERFÜGUNG</p>
falls outside the viewport.The element
<img src="/fileadmin/_pr…b8f1642eb9.png" class="image-embed-item">
falls outside the viewport.The element
<p class="title_smaller">Folgen Sie uns auf Facebook</p>
falls outside the viewport.The element
<div id="greyBox_192">
falls outside the viewport.The element
<p class="title_smaller_white">JOB BÖRSE</p>
falls outside the viewport.The element
<h2 class="">qualitépalliative</h2>
falls outside the viewport.The element
<p>Der Hauptzweck…lliative Care.</p>
falls outside the viewport.The element
<p>»mehr »Zertifi…Institutionen</p>
falls outside the viewport.The element
<p>Sponsored by</p>
falls outside the viewport.The element
<p class="copytextSmaller">Ihre Privat-SPITEX</p>
falls outside the viewport.The element
<img src="/fileadmin/tem…img/hbd-de.png" class="hbd">
falls outside the viewport.The element
<p class="copytextSmaller">Ihr Partner für Pflegebetten</p>
falls outside the viewport.The element
<p class="copytextSmaller">Ihre Weiterbildung</p>
falls outside the viewport.The element
<img src="/fileadmin/tem…ffuss_Bern.svg">
falls outside the viewport.priority - 4Size 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="https://www.fa…/palliativech/" class="logolink fb-link"></a>
is close to 3 other tap targets.<a href="/fr/palliative-ch/">FR</a>
and 3 others are close to other tap targets.The tap target
<input type="image" name="search" class="searchbox-button">
is close to 5 other tap targets.The tap target
<a href="/de/ueber-uns/kontakt/" class="linkclass">Kontakt</a>
and 3 others are close to other tap targets.<a href="#" class="menuButton">Palliative Care</a>
and 3 others are close to other tap targets.<a href="http://www.qua…palliative.ch/">»mehr</a>
and 1 others are close to other tap targets.palliative.ch HTML validation
Errors
Bad value “de_CH” for attribute “lang” on element “html”: The language subtag “de_ch” is not a valid language subtag.
"...TYPE html> <html lang=de_CH> <head..."
A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.
"...PO3 CMS"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta..."
Element “title” not allowed as child of element “head” in this context. (Suppressing further errors from this subtree.)
"... </script><title>pallia..."
End tag “li” implied, but there were open elements.
"...xt-klein"><li><..."
Unclosed element “a”.
"...></li><li><a href="/de/ueber-uns/spenden/" target="_self" class="txt-klein"><li><..."
Start tag “a” seen but an element of the same type was already open.
"...lein"><li><a href="https://www.facebook.com/palliativech/" class="txt-klein">Facebo..."
No “a” element in scope but a “a” end tag seen.
"...lein"><li><a href="https://www.facebook.com/palliativech/" class="txt-klein">Facebo..."
Stray end tag “a”.
"...k</a></li></a></li> ..."
No “li” element in scope but a “li” end tag seen.
"...></li></a></li> ..."
Duplicate ID “orangeFont”.
"...hen: <span id="orangeFont">DE</sp..." Line: 100 Column: 70 - 91
"...hen: <span id="orangeFont">DE</sp..." Line: 102 Column: 63 - 84
"...ich: <span id="orangeFont">PUBLIK..."
Bad value “49px” for attribute “height” on element “img”: Expected a digit but saw “p” instead.
"... href="/"><img src="https://www.palliative.ch/fileadmin/template/pix/logo_de.svg" alt="palliative ch" height="49px" width="198px" /></a></..." Line: 115 Column: 34 - 155
"... href="/"><img src="https://www.palliative.ch/fileadmin/template/pix/logo_de.svg" alt="palliative ch" height="49px" width="198px" /></a> ..."
Bad value “198px” for attribute “width” on element “img”: Expected a digit but saw “p” instead.
"... href="/"><img src="https://www.palliative.ch/fileadmin/template/pix/logo_de.svg" alt="palliative ch" height="49px" width="198px" /></a></..." Line: 115 Column: 34 - 155
"... href="/"><img src="https://www.palliative.ch/fileadmin/template/pix/logo_de.svg" alt="palliative ch" height="49px" width="198px" /></a> ..."
Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)
"...ativech/"> <?xml version="1..."
Duplicate ID “floatRight”.
"...</div> <div class="copytextSmaller" id="floatRight"> ..." Line: 102 Column: 4 - 48
"...v> --> <div class="copytextSmaller" id="floatRight">Bereic..."
The “cellpadding” attribute on the “table” element is obsolete. Use CSS instead.
"...edsearch"><table cellpadding="0" cellspacing="0" border="0"><tr><t..."
The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.
"...edsearch"><table cellpadding="0" cellspacing="0" border="0"><tr><t..."
The “border” attribute on the “table” element is obsolete. Use CSS instead.
"...edsearch"><table cellpadding="0" cellspacing="0" border="0"><tr><t..."
The “align” attribute on the “td” element is obsolete. Use CSS instead.
"...t" /></td><td align="right"> ..."
Attribute “value” not allowed on element “input” at this point.
"...hidden" /><input name="search" src="/fileadmin/template/pix/palliative/arrow_right.png" value="Search" class="searchbox-button" type="image" /> ..."
Element “input” is missing required attribute “alt”.
"...hidden" /><input name="search" src="/fileadmin/template/pix/palliative/arrow_right.png" value="Search" class="searchbox-button" type="image" /> ..."
The “align” attribute on the “div” element is obsolete. Use CSS instead.
"...</div> <div align="left" id="logo-desk"> <..."
Duplicate ID “orangeBox_328”.
"...layout-0"><div id="orangeBox_328"><div c..." Line: 182 Column: 76 - 99
"...layout-0"><div id="orangeBox_328"><div c..." Line: 188 Column: 76 - 99
"...layout-0"><div id="orangeBox_328"><div c..." Line: 191 Column: 76 - 99
"...layout-0"><div id="orangeBox_328"><div c..."
Bogus comment.
"... </div> <!–TYPO3SEARCH_be..." Line: 257 Column: - 6
"... </div> <!–TYPO3SEARCH_en..."
Duplicate ID “c2350”.
"...28_left"> <div id="c2350" class="frame frame-default frame-type-html frame-layout-0"><div i..."
Duplicate ID “c2353”.
"...></div> <div id="c2353" class="frame frame-default frame-type-textmedia frame-layout-0"><div c..."
Duplicate ID “c2330”.
"...></div> <div id="c2330" class="frame frame-default frame-type-html frame-layout-0"><div i..."
Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)
"...layout-0"><style> a.noh..."
No space between attributes.
"...class="nohover"target="_blank"..."
No “p” element in scope but a “p” end tag seen.
"...</div> </p> <d..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"...="_blank"><img style="width:90px" class="heimelig" src="/fileadmin/templates/main/img/heimelig.svg" /></a></..."
Warnings
The “language” attribute on the “script” element is obsolete. You can safely omit it.
"...tive.ch"/><SCRIPT LANGUAGE="JavaScript" SRC="/fileadmin/template/palliative/brainjarmenu.js"></SCRI..."
The “type” attribute is unnecessary for JavaScript resources.
"...></SCRIPT><script type="text/javascript" src="https://fast.fonts.net/jsapi/d51841f8-afbf-40c8-a79b-c4a0f9d551b5.js"></scri..." Line: 360 Column: 1 - 102
"...v> </div> <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js" type="text/javascript"></scri..."
The first occurrence of ID “orangeFont” was here.
"...ich: <span id="orangeFont">PUBLIK..." Line: 66 Column: 24 - 45
"...ich: <span id="orangeFont">PUBLIK..." Line: 66 Column: 24 - 45
"...ich: <span id="orangeFont">PUBLIK..."
The first occurrence of ID “floatRight” was here.
"...uage"> <div class="copytextSmaller" id="floatRight"> ..." Line: 85 Column: 4 - 48
"...uage"> <div class="copytextSmaller" id="floatRight"> ..."
The first occurrence of ID “orangeBox_328” was here.
"...layout-0"><div id="orangeBox_328"><div c..." Line: 127 Column: 76 - 99
"...layout-0"><div id="orangeBox_328"><div c..." Line: 127 Column: 76 - 99
"...layout-0"><div id="orangeBox_328"><div c..." Line: 127 Column: 76 - 99
"...layout-0"><div id="orangeBox_328"><div c..."
The first occurrence of ID “c2350” was here.
"... <p> <div id="c2350" class="frame frame-default frame-type-html frame-layout-0"><div i..."
The first occurrence of ID “c2353” was here.
"...></div> <div id="c2353" class="frame frame-default frame-type-textmedia frame-layout-0"><div c..."
The first occurrence of ID “c2330” was here.
"...></div> <div id="c2330" class="frame frame-default frame-type-html frame-layout-0"><div i..."
palliative.ch similar domains
www.palliative.net
www.palliative.org
www.palliative.info
www.palliative.biz
www.palliative.us
www.palliative.mobi
www.alliative.ch
www.palliative.ch
www.oalliative.ch
www.poalliative.ch
www.opalliative.ch
www.lalliative.ch
www.plalliative.ch
www.lpalliative.ch
www.plliative.ch
www.pqlliative.ch
www.paqlliative.ch
www.pqalliative.ch
www.pwlliative.ch
www.pawlliative.ch
www.pwalliative.ch
www.pslliative.ch
www.paslliative.ch
www.psalliative.ch
www.pzlliative.ch
www.pazlliative.ch
www.pzalliative.ch
www.paliative.ch
www.papliative.ch
www.palpliative.ch
www.paplliative.ch
www.paoliative.ch
www.paloliative.ch
www.paolliative.ch
www.pakliative.ch
www.palkliative.ch
www.paklliative.ch
www.palpiative.ch
www.pallpiative.ch
www.paloiative.ch
www.palloiative.ch
www.palkiative.ch
www.pallkiative.ch
www.pallative.ch
www.palluative.ch
www.palliuative.ch
www.palluiative.ch
www.palljative.ch
www.pallijative.ch
www.palljiative.ch
www.pallkative.ch
www.pallikative.ch
www.palloative.ch
www.pallioative.ch
www.pallitive.ch
www.palliqtive.ch
www.palliaqtive.ch
www.palliqative.ch
www.palliwtive.ch
www.palliawtive.ch
www.palliwative.ch
www.pallistive.ch
www.palliastive.ch
www.pallisative.ch
www.palliztive.ch
www.palliaztive.ch
www.pallizative.ch
www.palliaive.ch
www.palliarive.ch
www.palliatrive.ch
www.palliartive.ch
www.palliafive.ch
www.palliatfive.ch
www.palliaftive.ch
www.palliagive.ch
www.palliatgive.ch
www.palliagtive.ch
www.palliayive.ch
www.palliatyive.ch
www.palliaytive.ch
www.palliatve.ch
www.palliatuve.ch
www.palliatiuve.ch
www.palliatuive.ch
www.palliatjve.ch
www.palliatijve.ch
www.palliatjive.ch
www.palliatkve.ch
www.palliatikve.ch
www.palliatkive.ch
www.palliatove.ch
www.palliatiove.ch
www.palliatoive.ch
www.palliatie.ch
www.palliatice.ch
www.palliativce.ch
www.palliaticve.ch
www.palliatife.ch
www.palliativfe.ch
www.palliatifve.ch
www.palliatige.ch
www.palliativge.ch
www.palliatigve.ch
www.palliatibe.ch
www.palliativbe.ch
www.palliatibve.ch
www.palliativ.ch
www.palliativw.ch
www.palliativew.ch
www.palliativwe.ch
www.palliativs.ch
www.palliatives.ch
www.palliativse.ch
www.palliativd.ch
www.palliatived.ch
www.palliativde.ch
www.palliativr.ch
www.palliativer.ch
www.palliativre.ch
palliative.ch 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.
palliative.ch 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.