DOMINION.GAMES Dominion Online

dominion.games Website Information

Daily Unique Visits: 1,374

Daily Page Views: 2,748

Income Per Day: $9

Estimated Value: $2,160

dominion.games is registered under .GAMES top-level domain. Please check other sites in .GAMES zone.

No name server records were found.

and is probably hosted by Combell NV. See the full list of other websites hosted by Combell NV.

The highest website dominion.games position in Alexa rank database was 12834 and the lowest rank position was 970887. Current position of dominion.games in Alexa rank database is 521800.

Desktop speed score of dominion.games (20/100) is better than the results of 4.13% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of dominion.games (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.

Mobile speed score of dominion.games (17/100) is better than the results of 3.39% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

dominion.games 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.


dominion.games 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.


dominion.games domain is not supported

dominion.games server information

Servers Location

dominion.games desktop page speed rank

Last tested: 2017-12-29


Desktop Speed Bad
20/100

dominion.games Desktop Speed Test Quick Summary


priority - 307Enable 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 2.9MiB (79% reduction).

Compressing https://dominion.games/js/dominion-webclient-body-1.3.9.min.js could save 2.1MiB (80% reduction).
Compressing https://dominion.games/css/dominion-webclient-body-1.3.9.min.css could save 427KiB (88% reduction).
Compressing https://dominion.games/js/dominion-webclient-head-1.3.9.min.js could save 415.1KiB (70% reduction).
Compressing https://dominion.games/ could save 2.1KiB (72% reduction).
Compressing https://dominion.games/css/dominion-webclient-head-1.3.9.min.css could save 1.5KiB (64% reduction).

priority - 47Optimize images

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

Optimize the following images to reduce their size by 456.2KiB (59% reduction).

Compressing https://dominion.games/images/large/overgrown-estate.jpg could save 455.5KiB (59% reduction).
Compressing https://dominion.games/images/dom-icon-black.png could save 690B (14% reduction).

priority - 6Leverage 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://dominion.games/connection-properties.js (expiration not specified)
https://dominion.games/css/dominion-webclient-body-1.3.9.min.css (expiration not specified)
https://dominion.games/css/dominion-webclient-head-1.3.9.min.css (expiration not specified)
https://dominion.games/images/dom-icon-black.png (expiration not specified)
https://dominion.games/images/elements/red_cross.png (expiration not specified)
https://dominion.games/images/large/overgrown-estate.jpg (expiration not specified)
https://dominion.games/images/large/title.png (expiration not specified)
https://dominion.games/images/spear-left.png (expiration not specified)
https://dominion.games/images/spear-right.png (expiration not specified)
https://dominion.games/js/dominion-webclient-body-1.3.9.min.js (expiration not specified)
https://dominion.games/js/dominion-webclient-head-1.3.9.min.js (expiration not specified)

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 671B (23% reduction).

Minifying https://dominion.games/ could save 671B (23% reduction).

dominion.games Desktop Resource Breakdown

Total Resources14
Number of Hosts2
Static Resources11
JavaScript Resources3
CSS Resources2

dominion.games mobile page speed rank

Last tested: 2018-07-16


Mobile Speed Bad
17/100

dominion.games Mobile Speed Test Quick Summary


priority - 344Enable 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 3.3MiB (79% reduction).

Compressing https://dominion.games/js/dominion-webclient-body-1.3.14.min.js could save 2.4MiB (80% reduction).
Compressing https://dominion.games/js/dominion-webclient-head-1.3.14.min.js could save 462.7KiB (70% reduction).
Compressing https://dominion.games/css/dominion-webclient-body-1.3.14.min.css could save 434.7KiB (87% reduction).
Compressing https://dominion.games/ could save 2.2KiB (72% reduction).
Compressing https://dominion.games/css/dominion-webclient-head-1.3.14.min.css could save 1.5KiB (64% reduction).
Compressing https://dominion.games/connection-properties.js could save 245B (48% reduction).

priority - 47Optimize images

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

Optimize the following images to reduce their size by 456.2KiB (59% reduction).

Compressing https://dominion.games/images/large/overgrown-estate.jpg could save 455.5KiB (59% reduction).
Compressing https://dominion.games/images/dom-icon-black.png could save 690B (14% reduction).

priority - 8Leverage 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://dominion.games/connection-properties.js (expiration not specified)
https://dominion.games/css/dominion-webclient-body-1.3.14.min.css (expiration not specified)
https://dominion.games/css/dominion-webclient-head-1.3.14.min.css (expiration not specified)
https://dominion.games/images/dom-icon-black.png (expiration not specified)
https://dominion.games/images/elements/red_cross.png (expiration not specified)
https://dominion.games/images/large/overgrown-estate.jpg (expiration not specified)
https://dominion.games/images/large/title.png (expiration not specified)
https://dominion.games/images/spear-left.png (expiration not specified)
https://dominion.games/images/spear-right.png (expiration not specified)
https://dominion.games/js/dominion-webclient-body-1.3.14.min.js (expiration not specified)
https://dominion.games/js/dominion-webclient-head-1.3.14.min.js (expiration not specified)

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 667B (22% reduction).

Minifying https://dominion.games/ could save 667B (22% reduction).

dominion.games Mobile Resource Breakdown

Total Resources14
Number of Hosts2
Static Resources11
JavaScript Resources3
CSS Resources2

dominion.games mobile page usability

Last tested: 2018-07-16


Mobile Usability Good
100/100

dominion.games HTML validation

Errors

Bad value “expires” for attribute “http-equiv” on element “meta”.

Line: 10 Column: 9 - 47
"...> <meta http-equiv="expires" content="0"> ..."

Attribute “ng-controller” not allowed on element “body” at this point.

Line: 17 Column: 5 - 87
"...head> <body data-ng-app="Webclient" ng-controller="PageDisplayController as pageDisplay"> ..."

Attribute “ng-if” not allowed on element “img” at this point.

Line: 19 Column: 13 - 122
"... <img class="dom-icon unselectable" ng-if="pageDisplay.shouldShowLoadingPage" src="images/dom-icon-black.png"/> ..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 19 Column: 13 - 122
"... <img class="dom-icon unselectable" ng-if="pageDisplay.shouldShowLoadingPage" src="images/dom-icon-black.png"/> ..."

Attribute “ng-if” not allowed on element “div” at this point.

Line: 20 Column: 13 - 96
"... <div class="loading-spinner unselectable" ng-if="pageDisplay.shouldShowLoadingPage"></div>..." Line: 27 Column: 9 - 65
"...> <div class="login-page" ng-include="'html/login-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLoginPage" ng-controller="LoginController as login" ng-style="pageDisplay.loginStyle" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 36 Column: 9 - 65
"...> <div class="lobby-page" ng-include="'html/lobby-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLobbyPage" ng-show="pageDisplay.lobbyPageIsReady" ng-style="pageDisplay.lobbyStyle" ng-controller="LobbyController as lobby" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 38 Column: 9 - 49
"...> <div ng-if="!pageDisplay.shouldKillGame"> ..." Line: 46 Column: 13 - 69
"... <div class="game-page" ng-include="'html/game-page-1.3.4.html'" ng-if="pageDisplay.shouldShowGamePage" ng-show="pageDisplay.gamePageIsReady" ng-controller="GameDisplayController as gameDisplay" ng-style="pageDisplay.gameStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 54 Column: 9 - 65
"...> <div class="score-page" ng-include="'html/score-page-1.3.4.html'" ng-if="pageDisplay.shouldShowScorePage" ng-style="pageDisplay.scoreStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..."

Attribute “ng-include” not allowed on element “div” at this point.

Line: 27 Column: 9 - 65
"...> <div class="login-page" ng-include="'html/login-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLoginPage" ng-controller="LoginController as login" ng-style="pageDisplay.loginStyle" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 36 Column: 9 - 65
"...> <div class="lobby-page" ng-include="'html/lobby-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLobbyPage" ng-show="pageDisplay.lobbyPageIsReady" ng-style="pageDisplay.lobbyStyle" ng-controller="LobbyController as lobby" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 46 Column: 13 - 69
"... <div class="game-page" ng-include="'html/game-page-1.3.4.html'" ng-if="pageDisplay.shouldShowGamePage" ng-show="pageDisplay.gamePageIsReady" ng-controller="GameDisplayController as gameDisplay" ng-style="pageDisplay.gameStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 54 Column: 9 - 65
"...> <div class="score-page" ng-include="'html/score-page-1.3.4.html'" ng-if="pageDisplay.shouldShowScorePage" ng-style="pageDisplay.scoreStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..."

Attribute “ng-controller” not allowed on element “div” at this point.

Line: 27 Column: 9 - 65
"...> <div class="login-page" ng-include="'html/login-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLoginPage" ng-controller="LoginController as login" ng-style="pageDisplay.loginStyle" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 36 Column: 9 - 65
"...> <div class="lobby-page" ng-include="'html/lobby-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLobbyPage" ng-show="pageDisplay.lobbyPageIsReady" ng-style="pageDisplay.lobbyStyle" ng-controller="LobbyController as lobby" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 46 Column: 13 - 69
"... <div class="game-page" ng-include="'html/game-page-1.3.4.html'" ng-if="pageDisplay.shouldShowGamePage" ng-show="pageDisplay.gamePageIsReady" ng-controller="GameDisplayController as gameDisplay" ng-style="pageDisplay.gameStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..."

Attribute “ng-style” not allowed on element “div” at this point.

Line: 27 Column: 9 - 65
"...> <div class="login-page" ng-include="'html/login-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLoginPage" ng-controller="LoginController as login" ng-style="pageDisplay.loginStyle" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 36 Column: 9 - 65
"...> <div class="lobby-page" ng-include="'html/lobby-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLobbyPage" ng-show="pageDisplay.lobbyPageIsReady" ng-style="pageDisplay.lobbyStyle" ng-controller="LobbyController as lobby" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 46 Column: 13 - 69
"... <div class="game-page" ng-include="'html/game-page-1.3.4.html'" ng-if="pageDisplay.shouldShowGamePage" ng-show="pageDisplay.gamePageIsReady" ng-controller="GameDisplayController as gameDisplay" ng-style="pageDisplay.gameStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 54 Column: 9 - 65
"...> <div class="score-page" ng-include="'html/score-page-1.3.4.html'" ng-if="pageDisplay.shouldShowScorePage" ng-style="pageDisplay.scoreStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..."

Attribute “ng-show” not allowed on element “div” at this point.

Line: 36 Column: 9 - 65
"...> <div class="lobby-page" ng-include="'html/lobby-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLobbyPage" ng-show="pageDisplay.lobbyPageIsReady" ng-style="pageDisplay.lobbyStyle" ng-controller="LobbyController as lobby" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 46 Column: 13 - 69
"... <div class="game-page" ng-include="'html/game-page-1.3.4.html'" ng-if="pageDisplay.shouldShowGamePage" ng-show="pageDisplay.gamePageIsReady" ng-controller="GameDisplayController as gameDisplay" ng-style="pageDisplay.gameStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..."

Attribute “ng-click” not allowed on element “div” at this point.

Line: 36 Column: 9 - 65
"...> <div class="lobby-page" ng-include="'html/lobby-page-1.3.4.html'" ng-if="pageDisplay.shouldShowLobbyPage" ng-show="pageDisplay.lobbyPageIsReady" ng-style="pageDisplay.lobbyStyle" ng-controller="LobbyController as lobby" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 46 Column: 13 - 69
"... <div class="game-page" ng-include="'html/game-page-1.3.4.html'" ng-if="pageDisplay.shouldShowGamePage" ng-show="pageDisplay.gamePageIsReady" ng-controller="GameDisplayController as gameDisplay" ng-style="pageDisplay.gameStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..." Line: 54 Column: 9 - 65
"...> <div class="score-page" ng-include="'html/score-page-1.3.4.html'" ng-if="pageDisplay.shouldShowScorePage" ng-style="pageDisplay.scoreStyle" ng-click="pageDisplay.onClick()" oncontextmenu="return shouldEnableRightContextMenu"> ..."

dominion.games similar domains

Similar domains:
www.dominion.com
www.dominion.net
www.dominion.org
www.dominion.info
www.dominion.biz
www.dominion.us
www.dominion.mobi
www.ominion.games
www.dominion.games
www.xominion.games
www.dxominion.games
www.xdominion.games
www.sominion.games
www.dsominion.games
www.sdominion.games
www.eominion.games
www.deominion.games
www.edominion.games
www.rominion.games
www.drominion.games
www.rdominion.games
www.fominion.games
www.dfominion.games
www.fdominion.games
www.cominion.games
www.dcominion.games
www.cdominion.games
www.dminion.games
www.diminion.games
www.doiminion.games
www.diominion.games
www.dkminion.games
www.dokminion.games
www.dkominion.games
www.dlminion.games
www.dolminion.games
www.dlominion.games
www.dpminion.games
www.dopminion.games
www.dpominion.games
www.doinion.games
www.doninion.games
www.domninion.games
www.donminion.games
www.dojinion.games
www.domjinion.games
www.dojminion.games
www.dokinion.games
www.domkinion.games
www.domnion.games
www.domunion.games
www.domiunion.games
www.domuinion.games
www.domjnion.games
www.domijnion.games
www.domknion.games
www.domiknion.games
www.domonion.games
www.domionion.games
www.domoinion.games
www.domiion.games
www.domibion.games
www.dominbion.games
www.domibnion.games
www.domihion.games
www.dominhion.games
www.domihnion.games
www.domijion.games
www.dominjion.games
www.domimion.games
www.dominmion.games
www.domimnion.games
www.dominon.games
www.dominuon.games
www.dominiuon.games
www.dominuion.games
www.dominjon.games
www.dominijon.games
www.dominkon.games
www.dominikon.games
www.dominkion.games
www.dominoon.games
www.dominioon.games
www.dominoion.games
www.dominin.games
www.dominiin.games
www.dominioin.games
www.dominiion.games
www.dominikn.games
www.dominiokn.games
www.dominiln.games
www.dominioln.games
www.dominilon.games
www.dominipn.games
www.dominiopn.games
www.dominipon.games
www.dominio.games
www.dominiob.games
www.dominionb.games
www.dominiobn.games
www.dominioh.games
www.dominionh.games
www.dominiohn.games
www.dominioj.games
www.dominionj.games
www.dominiojn.games
www.dominiom.games
www.dominionm.games
www.dominiomn.games

dominion.games 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.


dominion.games 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.