Greetings,

I have a few things.

1:  Your thumbnails are not a consistant size.  This makes the page look very tacky.  Basic UX says to use a consistant layout, and you are already breaking that.

2:  Your search system seems to be very percise, and as a result limits the return set.  Additionally,the left nav filtering does not appear unless you search, leaving it fully unavailable on the default page load of the marketplace.

The customer should be able to filter on any result set, including the default one.

The next part is going to sound a bit preachy, but really, it's getting old.   I am a front end web developer for a major retailer (LLBean).  I work on design, and coding with a sharp focus on personalization, promotions and A/B testing.  In fact, I am writing this from a hotel room while I attend Google I/O which is one of the largest tech events of the year, and it's focused on performance, testing, mobile and wearable tech.

As near as I can tell, your testing methods are woefully inadequate.  Granted bugs do slip by and enter production from time to time, but the last three major releases that have happened to this site have resulted in entire sections of the site not working properly for sometimes days.   Errors of that magnitude should never happen on such a regular basis.

Additionally, it is fully evident that the staff does not know how to handle development and deployment.   Proper development does not get deployed unless it passes testing.  It can't even go to testing unless it's considered to be complete.   It being COMPLETE prior to going to production is how you avoid this kind of feedback.

When you deploy code, it should be transparent to the user as possible. Sure, the layout may switch one time when they move from one page to the next, but this isn't a ongoing battle where customers continue to see broken content for days.  You, as a company, should be able to force a hard refresh on the client side without forcing the customer to take action.   

Further, it's typically done during off hours when the server load is the lowest so anything that may go wrong impacts the least number of people possible.

If for some reason it goes into production and it's clearly buggy, you should roll it back until a time all the known issues are fixed.  If a company the size of Etsy can do 50 deployments a day, or Google can rollback an app update, there is no reason at all that this company can't revert code, unless for some reason you are not backing up the codebase before deployment to begin with.

I am telling you flat out.  Fix your development and deployment steps, and you will totally eliminate 90% of the negative feedback you get whenever you update your site.

-Fenier