You have built an application where there was a taxonomy or options field with more values defined in them than what was really being used after release. And these fields are being used as exposed filters in a View. This basically means that you end up with an option in an exposed filter that yields no results when selected. Not a good UI behaviour, and confusing for the end user.
It is frequent that customers approach us asking for help to rescue their projects from site builders. Sometimes they have technological issues (mainly slow sites) but sometimes it's just plain bad usability os some wrong marketing concepts.
We recently were asked for help from a site that gets about 5,000 unique visitors a day. Despite the not so bad visitor numbers for their niche, this page was getting very low user interaction. They barely got a handful (<10) of comments and forum posts in a whole year timespan.
In this article I will try to find out if there is any performance lead in running Drupal on IIS over Apache. I will not run any benchmarks on my own (for the moment), just analyze what I could find about this surfing the web. Type "iis vs apache drupal" in Google and this is what I found.
Drupal Performance on IIS7 vs Apache
Date: Mid 2012
-----------------------------
This post is outdated.
A new post has been updated with specific instructions for Drupal 8 and PHP7 here
