I dont work for answerbank, and have no idea of the actual problem, but here is my comment on it.
Like many web sites that store lots of data (Amazon, BBC etc) there are two main parts of it.
There is the "front end" which is the bit we see - the web page, the topics, the adverts, all the text on the screen etc.
Then there is the "back end". This is normally a relational database.
When you select a topic the "front end" has to go to the "back end" and say "give me all the entries for topic xzy"
This ovbiously takes some time. On a powerful system it could take less than a second.
But suppose 100 people are all asking the "back end" to do something at the same time.
This will obvously slow down the system and instead of taking a second it can take 5 seconds, or 10 seconds or whatever.
The more users you have the slower the system gets.
There are ways round this.
Get a faster server, get a better database, redesign the web site, spread the database over more than one server and so on.
None of these are quick, easy or cheap and all cost money.
I have no idea if that is why there are problems, but it may help you understand why there is no "quick fix".