framablog.org website information.
framablog.org domain name is registered by .ORG top-level domain registry. See the other sites registred in .ORG domain zone.
No name server records were found.
and probably website framablog.org is hosted by SERVERSTACK-ASN - ServerStack, Inc., US web hosting company. Check the complete list of other most popular websites hosted by SERVERSTACK-ASN - ServerStack, Inc., US hosting company.
According to Alexa traffic rank the highest website framablog.org position was 23339 (in the world). The lowest Alexa rank position was 987884. Now website framablog.org ranked in Alexa database as number 37268 (in the world).
Website framablog.org Desktop speed measurement score (63/100) is better than the results of 39.87% of other sites shows that the page desktop performance can be improved.
framablog.org 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 framablog.org (61/100) is better than the results of 57.04% 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 |
|---|---|---|
| Nov-08-2024 | 37,268 | 222 |
| Nov-07-2024 | 37,490 | 114 |
| Nov-06-2024 | 37,604 | -494 |
| Nov-05-2024 | 37,110 | 37 |
| Nov-04-2024 | 37,147 | -652 |
| Nov-03-2024 | 36,495 | 897 |
| Nov-02-2024 | 37,392 | 131 |
Advertisement
framablog.org 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.
framablog.org 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: framablog.org
Registry Domain ID: 689951c431a749309495af446a89e9be-LROR
Registrar WHOIS Server: http://whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2024-05-03T18:49:08Z
Creation Date: 2006-05-29T21:46:33Z
Registry Expiry Date: 2025-05-29T21:46:33Z
Registrar: Gandi SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: abuse@support.gandi.net
Registrar Abuse Contact Phone: +33.170377661
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Framasoft.org
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: 84
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: FR
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns-112-c.gandi.net
Name Server: ns-218-a.gandi.net
Name Server: ns-80-b.gandi.net
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-10-21T10:09:45Z
framablog.org server information
Servers Location
| IP Address |
|---|
| Country |
|---|
framablog.org desktop page speed rank
Last tested: 2019-01-04
framablog.org Desktop Speed Test Quick Summary
priority - 42 Enable 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 410.1KiB (73% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/ass…ugins-min.js?ver=3.3.2 could save 83.5KiB (71% reduction).
Compressing https://framablog.org/wp-includes/js/jquery/jquery.js?ver=1.12.4 could save 61.9KiB (65% reduction).
Compressing https://framablog.org/wp-includes/css/dist/block-l…tyle.min.css?ver=5.0.2 could save 20.8KiB (83% reduction).
Compressing https://framablog.org/wp-includes/js/masonry.min.js?ver=3.3.2 could save 20KiB (70% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/ass…strap-min.js?ver=3.3.2 could save 19.7KiB (72% reduction).
Compressing https://framablog.org/wp-content/plugins/wp-social…ocialshare.css?ver=1.6 could save 6.5KiB (84% reduction).
Compressing https://framablog.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1 could save 5.9KiB (60% reduction).
Compressing https://framablog.org/wp-includes/js/imagesloaded.min.js?ver=3.2.0 could save 5.4KiB (69% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/ass…/main-min.js?ver=3.3.2 could save 4.3KiB (66% reduction).
Compressing https://framablog.org/wp-content/themes/framavirtue/style.css?ver=5.0.2 could save 4.3KiB (46% reduction).
Compressing https://framablog.org/wp-content/uploads/newtheme.js could save 3.8KiB (66% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/ass…/default.css?ver=3.3.2 could save 2.6KiB (67% reduction).
Compressing https://framablog.org/wp-content/themes/framavirtue/framavirtue.js could save 1.8KiB (64% reduction).
Compressing https://framablog.org/wp-content/plugins/wp-to-twi…ter-feed.css?ver=5.0.2 could save 1.2KiB (69% reduction).
Compressing https://framablog.org/wp-content/plugins/pdf-print…frontend.css?ver=2.0.4 could save 1.1KiB (75% reduction).
Compressing https://framablog.org/wp-content/plugins/better-wp…shield.min.js?ver=4108 could save 967B (50% reduction).
Compressing https://framablog.org/wp-content/plugins/share-on-…pora-css.php?ver=5.0.2 could save 784B (60% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/style.css could save 668B (47% reduction).
Compressing https://framablog.org/wp-includes/js/wp-embed.min.js?ver=5.0.2 could save 650B (47% reduction).
Compressing https://framablog.org/wp-includes/js/hoverIntent.min.js?ver=1.8.1 could save 636B (57% reduction).
Compressing https://framablog.org/wp-content/plugins/dolomon/css/page.css?ver=5.0.2 could save 269B (50% reduction).
Compressing https://framablog.org/wp-content/plugins/dolomon/js/page.js?ver=5.0.2 could save 260B (47% reduction).
Compressing https://framablog.org/wp-content/plugins/dolomon/c…hortcode.css?ver=5.0.2 could save 251B (50% reduction).
Compressing https://framablog.org/wp-content/plugins/wp-first-…ss/style.css?ver=5.0.2 could save 247B (49% reduction).
Compressing https://framablog.org/wp-content/plugins/wp-social…socialshare.js?ver=1.6 could save 102B (30% reduction).
priority - 15 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 148KiB (18% reduction).
Compressing https://framablog.org/wp-content/uploads/2017/10/slide-services.jpg could save 39KiB (38% reduction).
Compressing https://framablog.org/wp-content/uploads/2018/10/s…ge_by-David-Revoy.jpeg could save 21.9KiB (29% reduction).
Compressing https://framablog.org/wp-content/uploads/2018/12/fig_12-407x270.png could save 14KiB (15% reduction).
Compressing https://framablog.org/wp-content/uploads/2017/10/slide-framasite.jpg could save 10.5KiB (18% reduction).
Compressing https://framablog.org/wp-content/uploads/2018/12/figure17-407x270.jpg could save 1.9KiB (11% reduction).
Compressing https://framablog.org/wp-content/uploads/2015/01/framablog.png could save 1.1KiB (22% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/ass…mg/slide_direction.png could save 974B (72% reduction).
priority - 2 Eliminate 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.
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.
Optimize CSS Delivery of the following:
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 3.7KiB (25% reduction).
Minifying https://framablog.org/wp-content/themes/framavirtue/style.css?ver=5.0.2 could save 1.1KiB (12% reduction).
Minifying https://framablog.org/wp-content/plugins/wp-first-…ss/style.css?ver=5.0.2 could save 421B (82% reduction).
Minifying https://framablog.org/wp-content/plugins/wp-to-twi…ter-feed.css?ver=5.0.2 could save 351B (21% reduction).
Minifying https://framablog.org/wp-content/plugins/share-on-…pora-css.php?ver=5.0.2 could save 189B (15% reduction).
Minifying https://framablog.org/wp-content/plugins/dolomon/css/page.css?ver=5.0.2 could save 141B (27% reduction).
Minifying https://framablog.org/wp-content/plugins/dolomon/c…hortcode.css?ver=5.0.2 could save 108B (22% reduction).
priority - 0 Reduce server response time
In our test, your server responded in 0.24 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 - 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 997B (19% reduction).
Minifying https://framablog.org/wp-content/plugins/better-wp…shield.min.js?ver=4108 could save 244B (13% reduction).
Minifying https://framablog.org/wp-content/plugins/dolomon/js/page.js?ver=5.0.2 could save 181B (33% reduction).
framablog.org Desktop Resources
| Total Resources | 47 |
| Number of Hosts | 4 |
| Static Resources | 42 |
| JavaScript Resources | 16 |
| CSS Resources | 12 |
framablog.org Desktop Resource Breakdown
framablog.org mobile page speed rank
Last tested: 2019-01-04
framablog.org Mobile Speed Test Quick Summary
priority - 42 Enable 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 410.1KiB (73% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/ass…ugins-min.js?ver=3.3.2 could save 83.5KiB (71% reduction).
Compressing https://framablog.org/wp-includes/js/jquery/jquery.js?ver=1.12.4 could save 61.9KiB (65% reduction).
Compressing https://framablog.org/wp-includes/css/dist/block-l…tyle.min.css?ver=5.0.2 could save 20.8KiB (83% reduction).
Compressing https://framablog.org/wp-includes/js/masonry.min.js?ver=3.3.2 could save 20KiB (70% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/ass…strap-min.js?ver=3.3.2 could save 19.7KiB (72% reduction).
Compressing https://framablog.org/wp-content/plugins/wp-social…ocialshare.css?ver=1.6 could save 6.5KiB (84% reduction).
Compressing https://framablog.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1 could save 5.9KiB (60% reduction).
Compressing https://framablog.org/wp-includes/js/imagesloaded.min.js?ver=3.2.0 could save 5.4KiB (69% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/ass…/main-min.js?ver=3.3.2 could save 4.3KiB (66% reduction).
Compressing https://framablog.org/wp-content/themes/framavirtue/style.css?ver=5.0.2 could save 4.3KiB (46% reduction).
Compressing https://framablog.org/wp-content/uploads/newtheme.js could save 3.8KiB (66% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/ass…/default.css?ver=3.3.2 could save 2.6KiB (67% reduction).
Compressing https://framablog.org/wp-content/themes/framavirtue/framavirtue.js could save 1.8KiB (64% reduction).
Compressing https://framablog.org/wp-content/plugins/wp-to-twi…ter-feed.css?ver=5.0.2 could save 1.2KiB (69% reduction).
Compressing https://framablog.org/wp-content/plugins/pdf-print…frontend.css?ver=2.0.4 could save 1.1KiB (75% reduction).
Compressing https://framablog.org/wp-content/plugins/better-wp…shield.min.js?ver=4108 could save 967B (50% reduction).
Compressing https://framablog.org/wp-content/plugins/share-on-…pora-css.php?ver=5.0.2 could save 784B (60% reduction).
Compressing https://framablog.org/wp-content/themes/virtue/style.css could save 668B (47% reduction).
Compressing https://framablog.org/wp-includes/js/wp-embed.min.js?ver=5.0.2 could save 650B (47% reduction).
Compressing https://framablog.org/wp-includes/js/hoverIntent.min.js?ver=1.8.1 could save 636B (57% reduction).
Compressing https://framablog.org/wp-content/plugins/dolomon/css/page.css?ver=5.0.2 could save 269B (50% reduction).
Compressing https://framablog.org/wp-content/plugins/dolomon/js/page.js?ver=5.0.2 could save 260B (47% reduction).
Compressing https://framablog.org/wp-content/plugins/dolomon/c…hortcode.css?ver=5.0.2 could save 251B (50% reduction).
Compressing https://framablog.org/wp-content/plugins/wp-first-…ss/style.css?ver=5.0.2 could save 247B (49% reduction).
Compressing https://framablog.org/wp-content/plugins/wp-social…socialshare.js?ver=1.6 could save 102B (30% reduction).
priority - 15 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 147.1KiB (18% reduction).
Compressing https://framablog.org/wp-content/uploads/2017/10/slide-services.jpg could save 39KiB (38% reduction).
Compressing https://framablog.org/wp-content/uploads/2018/10/s…ge_by-David-Revoy.jpeg could save 21.9KiB (29% reduction).
Compressing https://framablog.org/wp-content/uploads/2018/12/fig_12-407x270.png could save 14KiB (15% reduction).
Compressing https://framablog.org/wp-content/uploads/2017/10/slide-framasite.jpg could save 10.5KiB (18% reduction).
Compressing https://framablog.org/wp-content/uploads/2018/12/figure17-407x270.jpg could save 1.9KiB (11% reduction).
Compressing https://framablog.org/wp-content/uploads/2015/01/framablog.png could save 1.1KiB (22% reduction).
priority - 8 Eliminate 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.
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.
Optimize CSS Delivery of the following:
priority - 1 Reduce server response time
In our test, your server responded in 0.26 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 - 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 3.7KiB (25% reduction).
Minifying https://framablog.org/wp-content/themes/framavirtue/style.css?ver=5.0.2 could save 1.1KiB (12% reduction).
Minifying https://framablog.org/wp-content/plugins/wp-first-…ss/style.css?ver=5.0.2 could save 421B (82% reduction).
Minifying https://framablog.org/wp-content/plugins/wp-to-twi…ter-feed.css?ver=5.0.2 could save 351B (21% reduction).
Minifying https://framablog.org/wp-content/plugins/share-on-…pora-css.php?ver=5.0.2 could save 189B (15% reduction).
Minifying https://framablog.org/wp-content/plugins/dolomon/css/page.css?ver=5.0.2 could save 141B (27% reduction).
Minifying https://framablog.org/wp-content/plugins/dolomon/c…hortcode.css?ver=5.0.2 could save 108B (22% 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 997B (19% reduction).
Minifying https://framablog.org/wp-content/plugins/better-wp…shield.min.js?ver=4108 could save 244B (13% reduction).
Minifying https://framablog.org/wp-content/plugins/dolomon/js/page.js?ver=5.0.2 could save 181B (33% reduction).
framablog.org Mobile Resources
| Total Resources | 46 |
| Number of Hosts | 4 |
| Static Resources | 41 |
| JavaScript Resources | 16 |
| CSS Resources | 12 |
framablog.org Mobile Resource Breakdown
framablog.org mobile page usability
Last tested: 2019-01-04
framablog.org 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="https://framab….org/tag/code/" class="tag-cloud-link…ink-position-4">Code</a> and 2 others are close to other tap targets.The tap target
<a href="https://framab…/tag/facebook/" class="tag-cloud-link…nk-position-13">Facebook</a> and 2 others are close to other tap targets.The tap target
<a href="https://framab…g/tag/firefox/" class="tag-cloud-link…nk-position-14">Firefox</a> and 1 others are close to other tap targets.The tap target
<a href="https://framab…ag/innovation/" class="tag-cloud-link…nk-position-21">Innovation</a> is close to 1 other tap targets.The tap target
<a href="https://framab…tag/marketing/" class="tag-cloud-link…nk-position-27">Marketing</a> and 1 others are close to other tap targets.The tap target
<a href="https://framab…tag/microsoft/" class="tag-cloud-link…nk-position-29">Microsoft</a> is close to 1 other tap targets.The tap target
<a href="https://framab…rg/tag/planet/" class="tag-cloud-link…nk-position-32">Planet</a> is close to 1 other tap targets.The tap target
<a href="https://framab…g/tag/rezotic/" class="tag-cloud-link…nk-position-36">RezoTIC</a> is close to 2 other tap targets.The tap target
<a href="https://framab…ag/traduction/" class="tag-cloud-link…nk-position-39">Traduction</a> is close to 1 other tap targets.framablog.org similar domains
www.framablog.net
www.framablog.org
www.framablog.info
www.framablog.biz
www.framablog.us
www.framablog.mobi
www.ramablog.org
www.framablog.org
www.cramablog.org
www.fcramablog.org
www.cframablog.org
www.dramablog.org
www.fdramablog.org
www.dframablog.org
www.rramablog.org
www.frramablog.org
www.rframablog.org
www.tramablog.org
www.ftramablog.org
www.tframablog.org
www.gramablog.org
www.fgramablog.org
www.gframablog.org
www.vramablog.org
www.fvramablog.org
www.vframablog.org
www.famablog.org
www.feamablog.org
www.freamablog.org
www.feramablog.org
www.fdamablog.org
www.frdamablog.org
www.ffamablog.org
www.frfamablog.org
www.fframablog.org
www.ftamablog.org
www.frtamablog.org
www.frmablog.org
www.frqmablog.org
www.fraqmablog.org
www.frqamablog.org
www.frwmablog.org
www.frawmablog.org
www.frwamablog.org
www.frsmablog.org
www.frasmablog.org
www.frsamablog.org
www.frzmablog.org
www.frazmablog.org
www.frzamablog.org
www.fraablog.org
www.franablog.org
www.framnablog.org
www.franmablog.org
www.frajablog.org
www.framjablog.org
www.frajmablog.org
www.frakablog.org
www.framkablog.org
www.frakmablog.org
www.framblog.org
www.framqblog.org
www.framaqblog.org
www.framqablog.org
www.framwblog.org
www.framawblog.org
www.framwablog.org
www.framsblog.org
www.framasblog.org
www.framsablog.org
www.framzblog.org
www.framazblog.org
www.framzablog.org
www.framalog.org
www.framavlog.org
www.framabvlog.org
www.framavblog.org
www.framaglog.org
www.framabglog.org
www.framagblog.org
www.framahlog.org
www.framabhlog.org
www.framahblog.org
www.framanlog.org
www.framabnlog.org
www.framanblog.org
www.framabog.org
www.framabpog.org
www.framablpog.org
www.framabplog.org
www.framaboog.org
www.framabloog.org
www.framabolog.org
www.framabkog.org
www.framablkog.org
www.framabklog.org
www.framablg.org
www.framablig.org
www.framabloig.org
www.framabliog.org
www.framablkg.org
www.framablokg.org
www.framabllg.org
www.framablolg.org
www.framabllog.org
www.framablpg.org
www.framablopg.org
www.framablo.org
www.framablof.org
www.framablogf.org
www.framablofg.org
www.framablov.org
www.framablogv.org
www.framablovg.org
www.framablot.org
www.framablogt.org
www.framablotg.org
www.framablob.org
www.framablogb.org
www.framablobg.org
www.framabloy.org
www.framablogy.org
www.framabloyg.org
www.framabloh.org
www.framablogh.org
www.framablohg.org
framablog.org 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.
framablog.org 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.