edge.ca website information.
edge.ca domain name is registered by .CA top-level domain registry. See the other sites registred in .CA domain zone.
Following name servers are specified for edge.ca domain:
- ns-132.awsdns-16.com
- ns-1409.awsdns-48.org
- ns-1644.awsdns-13.co.uk
- ns-805.awsdns-36.net
and probably website edge.ca is hosted by YANDEX LLC web hosting company. Check the complete list of other most popular websites hosted by YANDEX LLC hosting company.
According to Alexa traffic rank the highest website edge.ca position was 65526 (in the world). The lowest Alexa rank position was 961895. Now website edge.ca ranked in Alexa database as number 194672 (in the world).
Website edge.ca Desktop speed measurement score (84/100) is better than the results of 78.07% of other sites and shows that the page is performing great on desktop computers.
edge.ca 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 edge.ca (62/100) is better than the results of 59.44% 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 |
|---|---|---|
| Sep-27-2024 | 194,672 | -1,349 |
| Sep-26-2024 | 193,323 | 655 |
| Sep-25-2024 | 193,978 | 2,876 |
| Sep-24-2024 | 196,854 | -1,278 |
| Sep-23-2024 | 195,576 | 682 |
| Sep-22-2024 | 196,258 | 728 |
| Sep-21-2024 | 196,986 | -2,925 |
Advertisement
edge.ca 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.
edge.ca 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.
Domain Name: edge.ca
Registry Domain ID: D7829-CIRA
Registrar WHOIS Server: whois.ca.fury.ca
Registrar URL: Markmonitor.com
Updated Date: 2020-04-10T09:42:28Z
Creation Date: 2000-10-13T17:37:07Z
Registry Expiry Date: 2022-05-12T04:00:00Z
Registrar: MarkMonitor International Canada Ltd.
Registrar IANA ID: not applicable
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: 16324217-CIRA
Registrant Name: CFNY-FM Limited o/a Edge
Registrant Organization:
Registrant Street: 72 Fraser Avenue
Registrant City: Toronto
Registrant State/Province: ON
Registrant Postal Code: M6K3J7
Registrant Country: CA
Registrant Phone: +1.4164796756
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: zone-admin@corusent.com
Registry Admin ID: 16474346-CIRA
Admin Name: Dan Vogler
Admin Organization: Corus Entertainment Inc.
Admin Street: 72 Fraser Avenue
Admin City: Toronto
Admin State/Province: ON
Admin Postal Code: M6K3J7
Admin Country: CA
Admin Phone: +1.4164796756
Admin Phone Ext:
Admin Fax: +1.4164796756
Admin Fax Ext:
Admin Email: zone-admin@corusent.com
Registry Tech ID: 16474346-CIRA
Tech Name: Dan Vogler
Tech Organization: Corus Entertainment Inc.
Tech Street: 72 Fraser Avenue
Tech City: Toronto
Tech State/Province: ON
Tech Postal Code: M6K3J7
Tech Country: CA
Tech Phone: +1.4164796756
Tech Phone Ext:
Tech Fax: +1.4164796756
Tech Fax Ext:
Tech Email: zone-admin@corusent.com
Registry Billing ID:
Billing Name:
Billing Organization:
Billing Street:
Billing City:
Billing State/Province:
Billing Postal Code:
Billing Country:
Billing Phone:
Billing Phone Ext:
Billing Fax:
Billing Fax Ext:
Billing Email:
Name Server: ns-132.awsdns-16.com
Name Server: ns-1409.awsdns-48.org
Name Server: ns-1644.awsdns-13.co.uk
Name Server: ns-805.awsdns-36.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2021-05-22T09:34:56Z
edge.ca server information
edge.ca desktop page speed rank
Last tested: 2018-01-19
edge.ca Desktop Speed Test Quick Summary
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 4 blocking script resources and 2 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://native.sharethrough.com/assets/sfp.js
https://r-login.wordpress.com/remote-login.php?act…tps%3A%2F%2Fedge.ca%2F
https://s1.wp.com/_static/??-eJyFjtEKwjAMRX/Irk6Qs…aP4dDut33fdf2u9Q+of3PX
Optimize CSS Delivery of the following:
https://s1.wp.com/wp-content/mu-plugins/highlander…7793621h&cssminify=yes
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://dmx.districtm.io/s/10002/qr1TAkVBY6ql (expiration not specified)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://cdn.krxd.net/controltag/KFT16kLA.js (20 minutes)
https://cdn.krxd.net/controltag?confid=KFT16kLA (20 minutes)
https://connect.facebook.net/en_US/sdk.js (20 minutes)
https://cdn.krxd.net/userdata/get?pub=5ae63e71-9e7…corus.kxjsonp_userdata (30 minutes)
https://native.sharethrough.com/assets/sfp.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/show_companion_ad.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 2 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 22.6KiB (50% reduction).
Compressing and resizing https://s0.wp.com/wp-content/themes/vip/plugins/vi…owered-light-small.png could save 1.7KiB (35% reduction).
Compressing https://edge1021.files.wordpress.com/2017/12/nav-logo_210x70_edge.png could save 964B (31% reduction).
priority - 2 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 19.7KiB (15% reduction).
Minifying https://s1.wp.com/_static/??-eJyFjtEKwjAMRX/Irk6Qs…aP4dDut33fdf2u9Q+of3PX could save 6.5KiB (14% reduction) after compression.
Minifying https://s2.wp.com/_static/??/wp-content/js/jquery/…cript.js?m=1516198001j could save 3.3KiB (31% reduction) after compression.
Minifying https://s1.wp.com/_static/??-eJzTLy/QTc7PK0nNK9HPL…toamBpbG5iamaaBQD/AjBY could save 468B (23% reduction) after compression.
priority - 0 Minify 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 234B (13% reduction).
edge.ca Desktop Resources
| Total Resources | 169 |
| Number of Hosts | 62 |
| Static Resources | 48 |
| JavaScript Resources | 61 |
| CSS Resources | 6 |
edge.ca Desktop Resource Breakdown
edge.ca mobile page speed rank
Last tested: 2019-06-14
edge.ca Mobile Speed Test Quick Summary
priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 4 blocking script resources and 1 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://native.sharethrough.com/assets/sfp.js
https://r-login.wordpress.com/remote-login.php?act…tps%3A%2F%2Fedge.ca%2F
https://s1.wp.com/_static/??-eJydjl0KwjAQhC9kGqSk+…M/7pU6tKrrVOseefqKyA==
Optimize CSS Delivery of the following:
priority - 13 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://dmx.districtm.io/s/10007/AAAGXgCz8mvSpQMUu…X0wollPwpph2hVIlshcpBm (expiration not specified)
https://dmx.districtm.io/s/10016/XQQhRQAAAKlKEDve&_test=XQQhRQAAAKlKEDve (expiration not specified)
https://dmx.districtm.io/s/10025/AAKIgk66CEMAACMC92Cbtg (expiration not specified)
https://dmx.districtm.io/s/10026/hwX0CffpQUZyWNS12GR2radjZvg (expiration not specified)
https://dmx.districtm.io/s/v1/buyers (expiration not specified)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://cdn.krxd.net/controltag/KFT16kLA.js (20 minutes)
https://connect.facebook.net/en_US/sdk.js (20 minutes)
https://beacon.krxd.net/cookie2json?callback=Krux.ns.corus.kxjsonp_3pevents (30 minutes)
https://cdn.krxd.net/userdata/get?pub=5ae63e71-9e7…corus.kxjsonp_userdata (30 minutes)
https://consumer.krxd.net/consent/get/5ae63e71-9e7….kxjsonp_consent_get_0 (30 minutes)
https://native.sharethrough.com/assets/sfp.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/show_companion_ad.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.districtm.ca/merge/all.corus.js (4 hours)
https://cdn.districtm.ca/merge/merge.103596.js (4 hours)
https://cdn.districtm.io/ids/idsync.4fd5df3e.js (4 hours)
https://widgets.outbrain.com/outbrain.js?ver=5.2.2-RC2-45535 (4 hours)
https://tcheck.outbrainimg.com/tcheck/check/ZWRnZS5jYQ== (4.8 hours)
priority - 10 Reduce server response time
In our test, your server responded in 0.86 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 - 7 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 65.3KiB (27% reduction).
Compressing https://tpc.googlesyndication.com/daca_images/simgad/15379983756484116745 could save 20.9KiB (19% reduction).
Compressing https://tpc.googlesyndication.com/daca_images/simgad/5944810683048307143 could save 13.9KiB (57% reduction).
Compressing https://tpc.googlesyndication.com/sadbundle/152380…0b5dcd9ffd56ffadba.jpg could save 5.4KiB (14% reduction).
Compressing https://edge1021.files.wordpress.com/2017/12/nav-logo_210x70_edge.png could save 964B (31% reduction).
priority - 2 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 18.8KiB (14% reduction).
Minifying https://s1.wp.com/_static/??-eJydjl0KwjAQhC9kGqSk+…M/7pU6tKrrVOseefqKyA== could save 7KiB (14% reduction) after compression.
Minifying https://connect.facebook.net/en_US/sdk.js could save 671B (39% reduction) after compression.
Minifying https://s1.wp.com/_static/??-eJyNjDEOgCAQwD4knmhQF…q0xkWqvlNynKchvP7LMFE= could save 468B (23% reduction) after compression.
edge.ca Mobile Resources
| Total Resources | 175 |
| Number of Hosts | 65 |
| Static Resources | 65 |
| JavaScript Resources | 50 |
| CSS Resources | 4 |
edge.ca Mobile Resource Breakdown
edge.ca mobile page usability
Last tested: 2019-06-14
edge.ca 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="/player" class="l-module--live__link"> is close to 2 other tap targets.The tap target
<a href="/player" class="l-module--live__link"> is close to 2 other tap targets.The tap target
<a href="/player" class="l-module--live__link"> is close to 2 other tap targets.edge.ca similar domains
www.edge.net
www.edge.org
www.edge.info
www.edge.biz
www.edge.us
www.edge.mobi
www.dge.ca
www.edge.ca
www.wdge.ca
www.ewdge.ca
www.wedge.ca
www.sdge.ca
www.esdge.ca
www.sedge.ca
www.ddge.ca
www.eddge.ca
www.dedge.ca
www.rdge.ca
www.erdge.ca
www.redge.ca
www.ege.ca
www.exge.ca
www.edxge.ca
www.exdge.ca
www.esge.ca
www.edsge.ca
www.eege.ca
www.edege.ca
www.eedge.ca
www.erge.ca
www.edrge.ca
www.efge.ca
www.edfge.ca
www.efdge.ca
www.ecge.ca
www.edcge.ca
www.ecdge.ca
www.ede.ca
www.edfe.ca
www.edgfe.ca
www.edve.ca
www.edgve.ca
www.edvge.ca
www.edte.ca
www.edgte.ca
www.edtge.ca
www.edbe.ca
www.edgbe.ca
www.edbge.ca
www.edye.ca
www.edgye.ca
www.edyge.ca
www.edhe.ca
www.edghe.ca
www.edhge.ca
www.edg.ca
www.edgw.ca
www.edgew.ca
www.edgwe.ca
www.edgs.ca
www.edges.ca
www.edgse.ca
www.edgd.ca
www.edged.ca
www.edgde.ca
www.edgr.ca
www.edger.ca
www.edgre.ca
edge.ca 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.
edge.ca 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.