I have been working with Sharepoint 2013 in our small office. However, i notice the sharepoint is very slow. Not always slow. Intermittent slow. When i first access the page it will take long for the page to appears. Then after that will be okay again. Then after a while when i click a link, the page will load very slow again and so on. Is sharepoint 2013 supposed to be like this?

  • 1
    Do you reboot your servers often? Do the server have the minimum requirements to run SharePoint? Have you modified your CSS? Do you have the minimal download feature activated? Commented Jun 24, 2014 at 6:25
  • What is the configuration of your Sharepoint farm and how many users using this?
    – Aanchal
    Commented Jun 24, 2014 at 6:25
  • 1
    No SharePoint is not supposed to be like that, make sure you have sufficient resources (like memory, disk and CPU). You could have a longer loading time on the first requests in the morning though (SharePoint does a recycle of its Application pools at night) Commented Jun 24, 2014 at 6:30

3 Answers 3


Slowness of sharePoint due to many factors.

  • you dont have enough hardware resources(CPU , RAM)
  • You have heavy customization
  • SQL Server may be
  • Have Antivirus on the servers
  • Network causing the slowness
  • custom queris to database
  • large List or libraries

How we can figured out and fixed it.

You can avoid the issue.


Along with what others have said, there could be a secret culprit that I know I ran into when I had the same things happen to me. If you have any workflows associated with your site, check how many items are currently running. When I first started sharepoint, I assumed that if a workflow is waiting, it wouldn't take up too much resource allocation with the CPU, but every running workflow takes its toll. I had about 100 running workflows, and had to manually stop each one to fix the problem. If these workflows have loops that don't terminate, that would be even worse.

Again, just check how many workflows are running on your site, then check server CPU use and thread # to determine what is slowing everything down.

And, like your problem, when the server was shut off, and turned back on again, everything worked great. But after an hour or so, it would go back to being painfully slow.


Only to add: Views with large numbers of items rendered by JavaScript on the client can be slow, too. Like when you use a lot of Client-Side Rendering transformations or set Item Limit to something like 100 or more items per page, or when you edit a long list using JSGrid.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.