games.ch Website Information
Daily Unique Visits: 5,686
Daily Page Views: 22,744
Income Per Day: $64
Estimated Value: $34,560
games.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 Host Europe GmbH. See the full list of other websites hosted by Host Europe GmbH.
The highest website games.ch position in Alexa rank database was 220698 and the lowest rank position was 329776. Current position of games.ch in Alexa rank database is 220698.
Desktop speed score of games.ch (66/100) is better than the results of 44.37% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of games.ch (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.
Mobile speed score of games.ch (52/100) is better than the results of 37.6% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
games.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.
games.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.
games.ch server information
Servers Location
games.ch desktop page speed rank
Last tested: 2018-12-10
games.ch Desktop Speed Test Quick Summary
priority - 32Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 311.8KiB (63% reduction).
Compressing https://ad.games.ch/images/50871a87de2ce86994c2ac0093ed10c4.jpg could save 85KiB (74% reduction).
Compressing https://games.ch/img/529.176.kgiig.1.jpg could save 17.2KiB (36% reduction).
Compressing and resizing https://games.ch/img/640.435.kggQ.0.jpg could save 16.6KiB (83% reduction).
Compressing and resizing https://games.ch/img/640.433.kgSb.0.jpg could save 13.2KiB (83% reduction).
Compressing and resizing https://games.ch/img/640.433.htah.0.jpg could save 12.7KiB (85% reduction).
Compressing and resizing https://games.ch/img/640.433.kgVb.0.jpg could save 12.5KiB (82% reduction).
Compressing and resizing https://games.ch/img/640.433.kgQf.0.jpg could save 12.4KiB (83% reduction).
Compressing and resizing https://games.ch/img/640.433.hto.0.jpg could save 12.3KiB (86% reduction).
Compressing and resizing https://games.ch/img/640.350.kgMi.0.jpg could save 9KiB (81% reduction).
Compressing and resizing https://games.ch/img/640.433.kgRa.0.jpg could save 7.6KiB (79% reduction).
Compressing https://games.ch/img/529.176.kgiah.1.jpg could save 7.1KiB (37% reduction).
Compressing https://games.ch/img/242.80.kgghb.1.jpg could save 4.8KiB (34% reduction).
Compressing and resizing https://games.ch/img/640.435.kgMa.0.jpg could save 2.9KiB (69% reduction).
Compressing https://games.ch/img/242.80.kgggg.1.jpg could save 2.7KiB (33% reduction).
Compressing https://games.ch/img/640.433.kgiig.0.jpg could save 1.5KiB (14% reduction).
Compressing https://games.ch/tpl/footer/scn.png could save 1.5KiB (14% reduction).
Compressing https://games.ch/img/640.433.kgghb.0.jpg could save 1.5KiB (12% reduction).
Compressing https://games.ch/img/640.433.kgiah.0.jpg could save 1.3KiB (22% reduction).
Compressing https://games.ch/img/640.433.kgggg.0.jpg could save 1.2KiB (20% reduction).
priority - 16Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 8 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://ad.games.ch/delivery/ajs.php?zoneid=37&cb=…oc=https%3A//games.ch/
https://ad.games.ch/delivery/ajs.php?zoneid=71&cb=…oc=https%3A//games.ch/
https://www.googletagservices.com/dcm/dcmads.js
https://www.googletagservices.com/dcm/impl_v45.js
https://ad.doubleclick.net/ddm/adj/N963588.3423254…6Jhj!hJ;sttr=1;prcl=s?
https://ad.games.ch/delivery/ajs.php?zoneid=47&cb=…oc=https%3A//games.ch/
https://ad.games.ch/delivery/ajs.php?zoneid=62&cb=…oc=https%3A//games.ch/
Optimize CSS Delivery of the following:
https://games.ch/css/desktop.css
https://fonts.googleapis.com/css?family=Raleway:400,200
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://ad.games.ch/images/92d7bd108181bd6de2761db6f8b37f3f.jpg (expiration not specified)
https://ad.games.ch/images/e57bf98d08ae5123ca89125dd8ca0116.jpg (expiration not specified)
https://pagead2.googlesyndication.com/pagead/js/lidar.js (60 minutes)
https://www.googletagservices.com/dcm/dcmads.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 2Prioritize 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.
priority - 1Minify 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 5KiB (26% reduction).
Minifying https://s0.2mdn.net/ads/richmedia/studio/15584/155…062809368_bootstrap.js could save 1.3KiB (36% 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 535B (28% reduction).
games.ch Desktop Resource Breakdown
Total Resources | 70 |
Number of Hosts | 12 |
Static Resources | 47 |
JavaScript Resources | 24 |
CSS Resources | 5 |
games.ch mobile page speed rank
Last tested: 2018-12-10
games.ch Mobile Speed Test Quick Summary
priority - 58Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 564.7KiB (39% reduction).
Compressing https://ad.games.ch/images/50871a87de2ce86994c2ac0093ed10c4.jpg could save 85KiB (74% reduction).
Compressing https://games.ch/img/1040.347.kgSb.1.jpg could save 71.7KiB (37% reduction).
Compressing https://s0.2mdn.net/8690493/FIFA19_Holiday_CH_300x250_DSK_Sony_HTML5_G.jpg could save 65.4KiB (69% reduction).
Compressing https://games.ch/img/1040.347.kgVb.1.jpg could save 62.7KiB (38% reduction).
Compressing https://games.ch/img/1040.347.kgQf.1.jpg could save 53.4KiB (30% reduction).
Compressing https://games.ch/img/1040.347.kgiig.1.jpg could save 50.5KiB (33% reduction).
Compressing https://games.ch/img/1040.347.kgRa.1.jpg could save 26.2KiB (30% reduction).
Compressing https://games.ch/img/1040.347.kgiah.1.jpg could save 18KiB (37% reduction).
Compressing https://games.ch/img/1040.347.kgMa.1.jpg could save 11KiB (16% reduction).
Compressing https://games.ch/img/640.435.kggQ.0.jpg could save 4.6KiB (24% reduction).
Compressing https://games.ch/img/640.433.hto.0.jpg could save 3.1KiB (22% reduction).
Compressing https://games.ch/img/640.433.kgVb.0.jpg could save 2.5KiB (17% reduction).
Compressing https://games.ch/img/640.433.kgSb.0.jpg could save 2.4KiB (16% reduction).
Compressing https://games.ch/img/640.433.htah.0.jpg could save 2.2KiB (15% reduction).
Compressing https://games.ch/img/640.350.kgMi.0.jpg could save 2.2KiB (20% reduction).
Compressing https://games.ch/img/640.433.kgRa.0.jpg could save 1.6KiB (17% reduction).
Compressing https://games.ch/img/640.433.kgiig.0.jpg could save 1.5KiB (14% reduction).
Compressing https://games.ch/tpl/footer/scn.png could save 1.5KiB (14% reduction).
Compressing https://games.ch/img/640.433.kgghb.0.jpg could save 1.5KiB (12% reduction).
Compressing https://games.ch/img/640.433.kgiah.0.jpg could save 1.3KiB (22% reduction).
Compressing https://games.ch/img/640.433.kgggg.0.jpg could save 1.2KiB (20% reduction).
priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 7 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://ad.games.ch/delivery/ajs.php?zoneid=71&cb=…oc=https%3A//games.ch/
https://ad.games.ch/delivery/ajs.php?zoneid=47&cb=…oc=https%3A//games.ch/
https://www.googletagservices.com/dcm/dcmads.js
https://www.googletagservices.com/dcm/impl_v45.js
https://ad.doubleclick.net/ddm/adj/N7657.279138GAM…6Jhj!hJ;sttr=1;prcl=s?
https://ad.games.ch/delivery/ajs.php?zoneid=62&cb=…oc=https%3A//games.ch/
Optimize CSS Delivery of the following:
https://games.ch/css/tablet.css
https://fonts.googleapis.com/css?family=Raleway:400,200
priority - 8Prioritize 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.
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://ad.games.ch/images/92d7bd108181bd6de2761db6f8b37f3f.jpg (expiration not specified)
https://www.googletagservices.com/activeview/js/cu…dar.js?cache=r20110914 (50 minutes)
https://www.googletagservices.com/dcm/dcmads.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
games.ch Mobile Resource Breakdown
Total Resources | 70 |
Number of Hosts | 16 |
Static Resources | 49 |
JavaScript Resources | 23 |
CSS Resources | 5 |
games.ch mobile page usability
Last tested: 2018-12-10
games.ch Mobile Usability Test Quick Summary
priority - 3Size 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.
<li class="">Alle Spiele</li>
and 14 others are close to other tap targets.<a id="23" href="/spiele.html" class="">Alle Spiele</a>
and 10 others are close to other tap targets.<a id="20" class="trigger">Channels</a>
and 1 others are close to other tap targets.The tap target
<a id="33" class="trigger">Community</a>
is close to 4 other tap targets.<a href="/index.html" class="act home float-shadow">Home</a>
is close to 2 other tap targets.<a href="/index.html" class="act home float-shadow">Home</a>
is close to 2 other tap targets.<a href="/artikel.html" class="float-shadow">Artikel</a>
and 4 others are close to other tap targets.<div class="owl-pagination"></div>
is close to 2 other tap targets.<a href="/artikel/vorschau.html">Vorschau</a>
is close to 1 other tap targets.games.ch HTML validation
Warnings
Consider avoiding viewport values that prevent users from resizing documents.
"...nt="320"> <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1.0"> <meta..."
Document uses the Unicode Private Use Area(s), which should not be used in publicly exchanged documents. (Charmod C073)
"...search"></a> <div ..."
The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.
"...='_blank'><img src='http://ad.games.ch/delivery/avw.php?zoneid=37&cb=425832&n=a4b0080a' border='0' alt='' /></a></..." Line: 474 Column: 109 - 217
"...='_blank'><img src='http://ad.games.ch/delivery/avw.php?zoneid=71&cb={$random}&n=a4d4afec' border='0' alt='' /></a></..." Line: 516 Column: 106 - 211
"...='_blank'><img src='http://ad.games.ch/delivery/avw.php?zoneid=47&cb=425832&n=a1dfde75' border='0' alt='' /></a></..." Line: 650 Column: 104 - 207
"...='_blank'><img src='http://ad.games.ch/delivery/avw.php?zoneid=62&cb=5633&n=a01b7a20' border='0' alt='' /></a></..."
Errors
Attribute “content” not allowed on element “time” at this point.
"...> <time itemprop="datePublished" content="2018-04-10 06:00:00" datetime="2018-04-10 06:00:00">10. Ap..." Line: 185 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 06:05:00" datetime="2018-04-09 06:05:00">09. Ap..." Line: 197 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-06 06:00:00" datetime="2018-04-06 06:00:00">06. Ap..." Line: 209 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-05 06:00:00" datetime="2018-04-05 06:00:00">05. Ap..." Line: 221 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-04 06:00:00" datetime="2018-04-04 06:00:00">04. Ap..." Line: 233 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-03 06:00:00" datetime="2018-04-03 06:00:00">03. Ap..." Line: 245 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-02 06:00:00" datetime="2018-04-02 06:00:00">02. Ap..." Line: 257 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-03-30 06:00:00" datetime="2018-03-30 06:00:00">30. Mä..." Line: 273 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 19:10:00" datetime="2018-04-09 19:10:00">09. Ap..." Line: 282 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 19:00:00" datetime="2018-04-09 19:00:00">09. Ap..." Line: 291 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 18:30:00" datetime="2018-04-09 18:30:00">09. Ap..." Line: 300 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 18:05:00" datetime="2018-04-09 18:05:00">09. Ap..." Line: 309 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 17:00:00" datetime="2018-04-09 17:00:00">09. Ap..." Line: 318 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 16:30:00" datetime="2018-04-09 16:30:00">09. Ap..." Line: 327 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 16:20:00" datetime="2018-04-09 16:20:00">09. Ap..." Line: 336 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 16:05:00" datetime="2018-04-09 16:05:00">09. Ap..." Line: 345 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 15:40:00" datetime="2018-04-09 15:40:00">09. Ap..." Line: 354 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 15:00:00" datetime="2018-04-09 15:00:00">09. Ap..." Line: 363 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 15:00:00" datetime="2018-04-09 15:00:00">09. Ap..." Line: 372 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 14:00:00" datetime="2018-04-09 14:00:00">09. Ap..." Line: 381 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 13:05:00" datetime="2018-04-09 13:05:00">09. Ap..." Line: 390 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 12:55:00" datetime="2018-04-09 12:55:00">09. Ap..." Line: 399 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 12:50:00" datetime="2018-04-09 12:50:00">09. Ap..." Line: 408 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 10:20:00" datetime="2018-04-09 10:20:00">09. Ap..." Line: 417 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 10:05:00" datetime="2018-04-09 10:05:00">09. Ap..." Line: 426 Column: 9 - 100
"...> <time itemprop="datePublished" content="2018-04-09 10:00:00" datetime="2018-04-09 10:00:00">09. Ap..." Line: 523 Column: 57 - 117
"...ss="date"><time itemprop="datePublished" content="2018-04-10 01:40:31">10. Ap..." Line: 530 Column: 57 - 117
"...ss="date"><time itemprop="datePublished" content="2018-04-09 15:40:30">09. Ap..." Line: 537 Column: 26 - 86
"...ss="date"><time itemprop="datePublished" content="2018-04-09 14:05:05">09. Ap..." Line: 544 Column: 26 - 86
"...ss="date"><time itemprop="datePublished" content="2018-04-09 11:58:15">09. Ap..." Line: 551 Column: 26 - 86
"...ss="date"><time itemprop="datePublished" content="2018-04-08 16:55:02">08. Ap..." Line: 558 Column: 26 - 86
"...ss="date"><time itemprop="datePublished" content="2018-04-08 08:37:55">08. Ap..."
Bad value “http://ad.games.ch/delivery/ck.php?n=a4d4afec&cb={$random}” for attribute “href” on element “a”: Illegal character in query: “{” is not allowed.
"...<noscript><a href='http://ad.games.ch/delivery/ck.php?n=a4d4afec&cb={$random}' target='_blank'><img s..."
Bad value “http://ad.games.ch/delivery/avw.php?zoneid=71&cb={$random}&n=a4d4afec” for attribute “src” on element “img”: Illegal character in query: “{” is not allowed.
"...='_blank'><img src='http://ad.games.ch/delivery/avw.php?zoneid=71&cb={$random}&n=a4d4afec' border='0' alt='' /></a></..."
The text content of element “time” was not in the required format: The literal did not satisfy the time-datetime format.
"...pr / 01:40</time></span..." Line: 530 Column: 133 - 139
"...pr / 15:40</time></span..." Line: 537 Column: 102 - 108
"...pr / 14:05</time></span..." Line: 544 Column: 102 - 108
"...pr / 11:58</time></span..." Line: 551 Column: 102 - 108
"...pr / 16:55</time></span..." Line: 558 Column: 102 - 108
"...pr / 08:37</time></span..."
No “li” element in scope but a “li” end tag seen.
"...</a></li> </li> </ul>..."
games.ch similar domains
www.games.net
www.games.org
www.games.info
www.games.biz
www.games.us
www.games.mobi
www.ames.ch
www.games.ch
www.fames.ch
www.gfames.ch
www.fgames.ch
www.vames.ch
www.gvames.ch
www.vgames.ch
www.tames.ch
www.gtames.ch
www.tgames.ch
www.bames.ch
www.gbames.ch
www.bgames.ch
www.yames.ch
www.gyames.ch
www.ygames.ch
www.hames.ch
www.ghames.ch
www.hgames.ch
www.gmes.ch
www.gqmes.ch
www.gaqmes.ch
www.gqames.ch
www.gwmes.ch
www.gawmes.ch
www.gwames.ch
www.gsmes.ch
www.gasmes.ch
www.gsames.ch
www.gzmes.ch
www.gazmes.ch
www.gzames.ch
www.gaes.ch
www.ganes.ch
www.gamnes.ch
www.ganmes.ch
www.gajes.ch
www.gamjes.ch
www.gajmes.ch
www.gakes.ch
www.gamkes.ch
www.gakmes.ch
www.gams.ch
www.gamws.ch
www.gamews.ch
www.gamwes.ch
www.gamss.ch
www.gamess.ch
www.gamses.ch
www.gamds.ch
www.gameds.ch
www.gamdes.ch
www.gamrs.ch
www.gamers.ch
www.gamres.ch
www.game.ch
www.gamew.ch
www.gamesw.ch
www.gamee.ch
www.gamese.ch
www.gamees.ch
www.gamed.ch
www.gamesd.ch
www.gamez.ch
www.gamesz.ch
www.gamezs.ch
www.gamex.ch
www.gamesx.ch
www.gamexs.ch
www.gamea.ch
www.gamesa.ch
www.gameas.ch
games.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.
games.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.