I have experienced similar problems when memory has been under perssure.
The OP said they have a 16GB box with 13GB allocated to SQL Server. This may be OK in the OP's environment, but typically allocating 12GB to SQL on a 16GB box is about the upper limit of what is safe.
Over allocating memory a small amount does not always cause SQL Server to run slowly, although large over allocation will affect SQL speed. However, lack of memory may affect other processes on the box that need to conmnect to SQL Server, such as SSIS and backup routines.
One troubleshooting tactic that is definitely worth doing in this situation is reducing the memory available to SQL by maybe 10%, and see if things become stable. If this does work, you can then increase the SQL memory in stages until things start breaking again, to prove that this is a memory starvation issue.
Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 1 Dec 2016
: now over 39,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Quote: "When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist." - Archbishop Hélder Câmara