CANALBLOG.COM Blog photo, blog audio ou video. Creer un blog gratuit


canalblog.com website information.

canalblog.com website servers are located in France and are responding from following IP address 195.137.184.103. Check the full list of most visited websites located in France.

canalblog.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for canalblog.com domain:

  • a3-67.akam.net
  • a28-66.akam.net
  • a7-64.akam.net
  • a20-65.akam.net
  • a1-69.akam.net
  • a12-64.akam.net

and probably website canalblog.com is hosted by akam.net web hosting company. Check the complete list of other most popular websites hosted by akam.net hosting company.

According to Alexa traffic rank the highest website canalblog.com position was 2612 (in the world). The lowest Alexa rank position was 72259. Now website canalblog.com ranked in Alexa database as number 12263 (in the world).

Website canalblog.com Desktop speed measurement score (75/100) is better than the results of 62.53% of other sites shows that the page desktop performance can be improved.

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

Mobile speed measurement score of canalblog.com (67/100) is better than the results of 71.47% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Sep-21-2019 12,263-5,620
Sep-20-2019 6,64310,067
Sep-19-2019 16,710-5,110
Sep-18-2019 11,600-2,034
Sep-17-2019 9,566-4,767
Sep-16-2019 4,7991,940
Sep-15-2019 6,7393,596

Advertisement

canalblog.com 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.


canalblog.com 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: CANALBLOG.COM
Registry Domain ID:
Registrar WHOIS Server: whois.namebay.com
Registrar URL: www.namebay.com
Updated Date: 2010-12-29 00:00:00Z
Creation Date: 2003-01-27 00:00:00Z
Registrar Registration Expiration Date: 2019-01-27 00:00:00Z
Registrar: NAMEBAY
Registrar IANA ID: 88
Registrar Abuse Contact Email: abuse@namebay.com
Registrar Abuse Contact Phone: +377.97706164
Reseller: https://www.namebay.com
Domain Status: clientTransferProhibited
Registry Registrant ID:
Registrant Name: JEAN-BAPTISTE CLOT
Registrant Organization: PINACOLAWEB SARL
Registrant Street: Hotel d'entreprises Z.A DU PONT PEYRIN
Registrant City: L'ISLE JOURDAIN
Registrant State/Province:
Registrant Postal Code: 32600
Registrant Country: FR
Registrant Phone: +33.547747000
Registrant Phone Ext:
Registrant Fax: +33.153013118
Registrant Fax Ext:
Registrant Email: DNS-ADMIN@PINACOLAWEB.COM
Registry Admin ID:
Admin Name: Jean-baptiste CLOT
Admin Organization: PINACOLAWEB
Admin Street: Hotel d'entreprises Z.A DU PONT PEYRIN
Admin City: L'ISLE JOURDAIN
Admin State/Province:
Admin Postal Code: 32600
Admin Country: FR
Admin Phone: +33.547747000
Admin Phone Ext:
Admin Fax: +33.153013118
Admin Fax Ext:
Admin Email: DNS-ADMIN@PINACOLAWEB.COM
Registry Tech ID:
Tech Name: Jean-baptiste CLOT
Tech Organization: PINACOLAWEB
Tech Street: Hotel d'entreprises Z.A DU PONT PEYRIN
Tech City: L'ISLE JOURDAIN
Tech State/Province:
Tech Postal Code: 32600
Tech Country: FR
Tech Phone: +33.547747000
Tech Phone Ext:
Tech Fax: +33.153013118
Tech Fax Ext:
Tech Email: DNS-ADMIN@PINACOLAWEB.COM
Name Server: NS0.PINACOLAWEB.COM
Name Server: NS1.PINACOLAWEB.COM
Name Server: NS2.PINACOLAWEB.COM
Name Server: NS3.PINACOLAWEB.COM
Name Server: NS4.PINACOLAWEB.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System:
http://wdprs.internic.net/
>>> Last update of WHOIS database: 2010-12-29 00:00:00Z

canalblog.com server information

Servers Location

canalblog.com desktop page speed rank

Last tested: 2016-06-12


Desktop Speed Medium
75/100

canalblog.com Desktop Speed Test Quick Summary


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

http://www.canalblog.com/sharedDocs/css/autocomplete.css (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/ico-01.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/ico-02.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/ico-03.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/ico-04.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/ico-06.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/ico-07.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/screenblogs.png (expiration not specified)
http://www.canalblog.com/sharedDocs/images/old_logo.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/webedia.png (expiration not specified)
http://www.canalblog.com/sharedDocs/js/disclaimerCookie.js (expiration not specified)
http://www.canalblog.com/sharedDocs/js/jquery.autocomplete.js (expiration not specified)
http://www.canalblog.com/sharedDocs/js/jquery.tools.min.js (expiration not specified)
http://www.canalblog.com/sharedDocs/js/main.js (expiration not specified)
http://www.canalblog.com/sharedDocs/js/mobilebrowsersdetect.js (expiration not specified)
https://syndication.twitter.com/widgets/followbutt…screen_names=CanalBlog (10 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-PXZQ89 (16.2 minutes)
http://cdn.krxd.net/controltag/KO96Fuv_.js (20 minutes)
http://cdn.krxd.net/controltag?confid=KO96Fuv_ (20 minutes)
http://connect.facebook.net/fr_FR/sdk.js (20 minutes)
http://beacon.krxd.net/cookie2json?callback=Krux.n…bedia.kxjsonp_3pevents (30 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
http://w.estat.com/js/whap.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
http://storage.canalblog.com/38/08/309591/111063579_q.jpg (31.1 hours)
http://storage.canalblog.com/71/32/546839/111067590_q.jpeg (41.9 hours)
http://storage.canalblog.com/38/93/1032368/104964837_q.jpg (3.5 days)
http://storage.canalblog.com/59/26/437273/111105069_q.jpg (3.8 days)
http://storage.canalblog.com/25/45/775031/110472940_q.jpg (4.2 days)
http://storage.canalblog.com/85/07/172403/110934425_q.jpg (4.4 days)
http://storage.canalblog.com/56/62/581044/111108013.jpg (4.4 days)
http://storage.canalblog.com/25/20/892764/103317743_q.jpg (5.3 days)
http://storage.canalblog.com/91/51/829392/111131687_q.jpg (5.4 days)
http://storage.canalblog.com/63/28/341599/110375972_q.png (5.4 days)
http://storage.canalblog.com/06/14/1115593/111114928_q.jpg (5.7 days)
http://storage.canalblog.com/38/85/892013/110809520_q.jpg (5.8 days)
http://storage.canalblog.com/75/36/785252/111127244_q.jpg (5.8 days)
http://storage.canalblog.com/03/56/1059240/111133754_q.png (5.9 days)
http://storage.canalblog.com/18/15/142677/111032770_q.jpg (6.1 days)
http://storage.canalblog.com/46/97/1127088/111032542_q.jpg (6.2 days)
http://storage.canalblog.com/05/69/668246/111025106_q.jpg (6.2 days)
http://storage.canalblog.com/29/58/1093247/111133352_q.jpg (6.3 days)
http://storage.canalblog.com/52/81/313253/111086372_q.jpg (6.4 days)
http://storage.canalblog.com/23/38/476214/110497499_q.jpg (6.4 days)
http://storage.canalblog.com/27/79/736494/111144854_q.jpg (6.5 days)
http://storage.canalblog.com/08/17/549609/110912302_q.jpg (6.5 days)
http://storage.canalblog.com/57/43/655930/111144383_q.jpg (6.7 days)
http://storage.canalblog.com/78/93/49081/111141850_q.jpg (6.7 days)
http://storage.canalblog.com/48/51/905117/111142908_q.jpg (6.7 days)
http://storage.canalblog.com/40/28/404254/111147914_q.jpg (6.8 days)
http://storage.canalblog.com/96/39/1460896/111129864_q.jpg (6.9 days)
http://storage.canalblog.com/19/56/421949/110840070_q.jpg (6.9 days)
http://storage.canalblog.com/31/80/1460910/111134492_q.jpg (6.9 days)

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

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

http://www.canalblog.com/sharedDocs/js/main.js
http://www.canalblog.com/sharedDocs/js/mobilebrowsersdetect.js
http://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js
http://www.canalblog.com/sharedDocs/js/jquery.colorbox-min.js?1459954800
http://www.canalblog.com/sharedDocs/js/jquery.tools.min.js
http://www.canalblog.com/sharedDocs/js/jquery.autocomplete.js

Optimize CSS Delivery of the following:

http://www.canalblog.com/sharedDocs/css/all.css?1459954800
http://www.canalblog.com/sharedDocs/css/colorbox.css?1459954800
http://www.canalblog.com/sharedDocs/css/autocomplete.css

priority - 7 Optimize images

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

Optimize the following images to reduce their size by 67.9KiB (76% reduction).

Compressing and resizing http://www.canalblog.com/sharedDocs/images/webedia.png could save 33.3KiB (96% reduction).
Compressing and resizing http://storage.canalblog.com/52/81/313253/111086372_q.jpg could save 6.6KiB (87% reduction).
Compressing and resizing http://storage.canalblog.com/27/79/736494/111144854_q.jpg could save 5.7KiB (87% reduction).
Compressing and resizing http://storage.canalblog.com/96/39/1460896/111129864_q.jpg could save 5.4KiB (85% reduction).
Compressing and resizing http://storage.canalblog.com/31/80/1460910/111134492_q.jpg could save 4.9KiB (84% reduction).
Losslessly compressing https://static.xx.fbcdn.net/rsrc.php/v2/yl/r/exzGWwKEETI.png could save 4.5KiB (36% reduction).
Compressing and resizing http://storage.canalblog.com/78/93/49081/111141850_q.jpg could save 2.4KiB (77% reduction).
Compressing and resizing http://storage.canalblog.com/23/38/476214/110497499_q.jpg could save 1.7KiB (73% reduction).
Losslessly compressing http://static.canalblog.com/sharedDocs/images/intro-btn.gif could save 1.3KiB (54% reduction).
Losslessly compressing http://static.canalblog.com/sharedDocs/images/btn-submit2.gif could save 1.1KiB (50% reduction).
Losslessly compressing http://static.canalblog.com/sharedDocs/images/frontend/bg-body.gif could save 930B (20% reduction).

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 2.2KiB (35% reduction).

Minifying http://www.canalblog.com/sharedDocs/js/jquery.autocomplete.js could save 2.2KiB (35% 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 786B (12% reduction).

Minifying http://www.canalblog.com/sharedDocs/css/all.css?1459954800 could save 786B (12% reduction) after compression.

canalblog.com Desktop Resources

Total Resources148
Number of Hosts28
Static Resources121
JavaScript Resources42
CSS Resources6

canalblog.com Desktop Resource Breakdown

canalblog.com mobile page speed rank

Last tested: 2016-06-12


Mobile Speed Medium
67/100

canalblog.com Mobile Speed Test Quick Summary


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

Your page has 8 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:

http://static.canalblog.com/sharedDocs/js/mobile/jquery-1.8.0.min.js
http://static.canalblog.com/sharedDocs/js/mobile/jquery.mobile-1.3.0.min.js
http://static.canalblog.com/sharedDocs/js/blog/jqu…comments.js?1320746401
http://static.canalblog.com/sharedDocs/js/blog/Z70-comments.js?1320746401
http://static.canalblog.com/sharedDocs/js/blog/jqu…validate.js?1320746401
http://static.canalblog.com/sharedDocs/js/klass.min.js
http://static.canalblog.com/sharedDocs/js/code.pho…pe.jquery-3.0.5.min.js
http://w.estat.com/js/whap.js

Optimize CSS Delivery of the following:

http://static.canalblog.com/sharedDocs/css/mobile/mob.css
http://static.canalblog.com/sharedDocs/css/mobile/…tructure-1.3.0.min.css

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

http://www.canalblog.com/sharedDocs/images/frontend/ico-01.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/ico-03.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/ico-04.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/frontend/ico-05.gif (expiration not specified)
http://www.canalblog.com/sharedDocs/images/mobile/logo.png (expiration not specified)
http://www.googletagmanager.com/gtm.js?id=GTM-PXZQ89 (16.2 minutes)
http://cdn.krxd.net/controltag/KO96Fuv_.js (20 minutes)
http://cdn.krxd.net/controltag?confid=KO96Fuv_ (20 minutes)
http://beacon.krxd.net/cookie2json?callback=Krux.n…bedia.kxjsonp_3pevents (30 minutes)
http://w.estat.com/js/whap.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
http://storage.canalblog.com/38/08/309591/111063579_q.jpg (31.1 hours)
http://storage.canalblog.com/71/32/546839/111067590_q.jpeg (41.9 hours)
http://storage.canalblog.com/56/62/581044/111108013_q.jpg (4.6 days)
http://storage.canalblog.com/75/36/785252/111127244_q.jpg (5.8 days)
http://storage.canalblog.com/03/56/1059240/111133754_q.png (5.8 days)
http://storage.canalblog.com/46/97/1127088/111032542_q.jpg (6.1 days)
http://storage.canalblog.com/18/15/142677/111032770_q.jpg (6.1 days)
http://storage.canalblog.com/57/43/655930/111144383_q.jpg (6.7 days)
http://storage.canalblog.com/48/51/905117/111142908_q.jpg (6.7 days)

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 23% of the final above-the-fold content could be rendered with the full HTML response.

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 4.1KiB (29% reduction).

Minifying http://static.canalblog.com/sharedDocs/js/blog/jqu…validate.js?1320746401 could save 3.2KiB (33% reduction) after compression.
Minifying http://static.canalblog.com/sharedDocs/js/blog/Z70-comments.js?1320746401 could save 999B (20% 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 1.2KiB (32% reduction).

Minifying http://static.canalblog.com/sharedDocs/css/mobile/mob.css could save 1.2KiB (32% reduction) after compression.

priority - 0 Optimize images

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

Optimize the following images to reduce their size by 855B (88% reduction).

Losslessly compressing http://static.canalblog.com/sharedDocs/images/mobile/menubut.png could save 855B (88% reduction).

canalblog.com Mobile Resources

Total Resources41
Number of Hosts10
Static Resources33
JavaScript Resources16
CSS Resources2

canalblog.com Mobile Resource Breakdown

canalblog.com mobile page usability

Last tested: 2016-06-12


Mobile Usability Good
99/100

canalblog.com 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 <a href="#mypanel" class="ui-icon-mapa u…-btn-icon-left"></a> is close to 1 other tap targets.

canalblog.com Mobile Resources

Total Resources41
Number of Hosts10
Static Resources33
JavaScript Resources16
CSS Resources2

canalblog.com Mobile Resource Breakdown

canalblog.com similar domains

Similar domains:
www.canalblog.com
www.canalblog.net
www.canalblog.org
www.canalblog.info
www.canalblog.biz
www.canalblog.us
www.canalblog.mobi
www.analblog.com
www.canalblog.com
www.xanalblog.com
www.cxanalblog.com
www.xcanalblog.com
www.danalblog.com
www.cdanalblog.com
www.dcanalblog.com
www.fanalblog.com
www.cfanalblog.com
www.fcanalblog.com
www.vanalblog.com
www.cvanalblog.com
www.vcanalblog.com
www.cnalblog.com
www.cqnalblog.com
www.caqnalblog.com
www.cqanalblog.com
www.cwnalblog.com
www.cawnalblog.com
www.cwanalblog.com
www.csnalblog.com
www.casnalblog.com
www.csanalblog.com
www.cznalblog.com
www.caznalblog.com
www.czanalblog.com
www.caalblog.com
www.cabalblog.com
www.canbalblog.com
www.cabnalblog.com
www.cahalblog.com
www.canhalblog.com
www.cahnalblog.com
www.cajalblog.com
www.canjalblog.com
www.cajnalblog.com
www.camalblog.com
www.canmalblog.com
www.camnalblog.com
www.canlblog.com
www.canqlblog.com
www.canaqlblog.com
www.canqalblog.com
www.canwlblog.com
www.canawlblog.com
www.canwalblog.com
www.canslblog.com
www.canaslblog.com
www.cansalblog.com
www.canzlblog.com
www.canazlblog.com
www.canzalblog.com
www.canablog.com
www.canapblog.com
www.canalpblog.com
www.canaplblog.com
www.canaoblog.com
www.canaloblog.com
www.canaolblog.com
www.canakblog.com
www.canalkblog.com
www.canaklblog.com
www.canallog.com
www.canalvlog.com
www.canalbvlog.com
www.canalvblog.com
www.canalglog.com
www.canalbglog.com
www.canalgblog.com
www.canalhlog.com
www.canalbhlog.com
www.canalhblog.com
www.canalnlog.com
www.canalbnlog.com
www.canalnblog.com
www.canalbog.com
www.canalbpog.com
www.canalblpog.com
www.canalbplog.com
www.canalboog.com
www.canalbloog.com
www.canalbolog.com
www.canalbkog.com
www.canalblkog.com
www.canalbklog.com
www.canalblg.com
www.canalblig.com
www.canalbloig.com
www.canalbliog.com
www.canalblkg.com
www.canalblokg.com
www.canalbllg.com
www.canalblolg.com
www.canalbllog.com
www.canalblpg.com
www.canalblopg.com
www.canalblo.com
www.canalblof.com
www.canalblogf.com
www.canalblofg.com
www.canalblov.com
www.canalblogv.com
www.canalblovg.com
www.canalblot.com
www.canalblogt.com
www.canalblotg.com
www.canalblob.com
www.canalblogb.com
www.canalblobg.com
www.canalbloy.com
www.canalblogy.com
www.canalbloyg.com
www.canalbloh.com
www.canalblogh.com
www.canalblohg.com
www.canalblog.con

canalblog.com 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.


canalblog.com 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.