You will need to find out what these slow queries look like. One way to do this is to use Profiler, filtered for a particular user, so that you only see the queries that user submits. This can be difficult it the application is using an application login. In that case, it may be better to run an idle test environment where you can run without a filter.
You talk about a table as if there is only one, but I would guess that these queries join to other tables and that affects the query plan.
Tables are not really slow in themselves, but queries can be slow if there are not appropriate indexes. However, the table could be heavily fragmented with many pages almost empty. Heaps are particularly prone to this. So if you want to shoot from the hip, you can do
ALTER TABLE tbl REBUILD
The table will not be available when the command is running.