Wordpress
Google insights on Drupal
Recently, Google launched Google Insights. Like with Google Trends, you can just type in a search term to see search volume patterns over time, as well as the top related and rising searches. You’ll also have the ability to compare search volume trends across multiple search terms, categories (commonly referred to as verticals), geographic regions, or specific time ranges. Great for marketing people.
Below are some examples specific to Drupal ...
The numbers on the graph reflect how many searches have been done for a particular term, relative to the total number of searches done on Google over time. See Google Insights results for Drupal.
In China, Wordpress is winning hands down. See Google Insights results for Drupal.
In my home country, Belgium, Drupal is almost as strong as Wordpress but not nearly as strong as Joomla. See Google Insights results for Drupal.
Regional Drupal interest by country. Google uses the term 'search volume index' for these heatmaps, meaning that they normalized the data by the total traffic from each respective region. In other words, just because two regions show the same percentage for a particular term doesn't mean that their absolute search volumes are the same. See Google Insights results for Drupal.
In the US, the west coast beats the east coast. Based on 'search volume index'. See Google Insights results for Drupal.
Regional Drupal interest by city. Based on 'search volume index'. See Google Insights results for Drupal.
The top search on Drupal -- great for marketing people. Breakout means that the search term has experienced a change in growth greater than 5000%. See Google Insights results for Drupal.
Mollom for Wordpress
Matthias Vandermaesen released a Mollom plugin for Wordpress. You can read more about it on his blog or you can download WP-Mollom from the Wordpress.org plugin directory. Thanks for all the hard work, Matthias!
YSlow
Yahoo! released YSlow, a Firefox extension that integrates with the popular Firebug tool. YSlow was originally developed as an internal tool at Yahoo! with the help of Steve Souders, Chief Performance at Yahoo! and author of O'Reilly's High Performance Websites book.
YSlow analyzes the front-end performance of your website and tells you why it might be slow. For each component of a page (images, scripts, stylesheets) it checks its size, whether it was gzipped, the Expires-header, the ETag-header, etc. YSlow takes all this information into account and computes a performance grade for the page you are analyzing.
The current YSlow score for the drupal.org front page is 74 (C). YSlow suggests that we reduce the number of CSS background images using CSS sprites, that we use a Content Delivery Network (CDN) like Akamai for delivering static files, and identifies an Apache configuration issue that affects the Entity Tags or ETags of static files. The problem is that, by default, Apache constructs ETags using attributes that make them unique to a specific server. A stock Apache embeds inode numbers in the ETag which dramatically reduces the odds of the validity test succeeding on web sites with multiple servers; the ETags won't match when a browser gets the original component from server A and later tries to validate that component on server B.
Here are some other YSlow scores (higher is better):
- http://wordpress.org: 78 (C)
- http:/drupal.org: 74 (C)
- http://plone.org: 64 (D)
- http://postnuke.com: 63 (D)
- http://typo3.org: 56 (F)
- http://mamboserver.com: 56 (F)
- http://joomla.org: 53 (F)
From what I have seen, Apache configuration issues, and not CMS implementation issues, are the main source of low YSlow scores. Be careful not to draw incorrect conclusions from these numbers; they are often not representative for the CMS software itself.
And it doesn't change the fact that drupal.org is currently a lot slower than most of these other sites. That is explained by drupal.org's poor back-end performance, and not by the front-end performance as measured by YSlow. (We're working on adding a second database server to drupal.org.)
CMS code base comparison
Drupal
Source: Drupal statistics at Ohloh.
Joomla!
Source: Joomla! statistics at Ohloh.
Wordpress
Source: Wordpress statistics at Ohloh.
Plone
Source: Plone statistics at Ohloh.
(These graphs depict statistics for the core of each project, and do not include contributed modules, extensions or third-party plugins.)
Conclusions
- All projects have been growing in size. No exceptions.
- Drupal has, by far, the smallest code base. It's lean and mean. Joomla!'s code base is about 8 times bigger than Drupal's. Even Wordpress's code base is larger than Drupal's.
- Of all tools, the Wordpress code has the fewest code comments. Drupal and Joomla!, on the other hand, have the best documented code.