1GB is a bit low these days, but usually ok enough, but that many apps might still pose a problem depending on the permissions they got. the more apps you got that have permissions such as 'prevent phone from going to sleep' or 'run in background' might end up trying to remain in memory doing things. the more apps that load in memory and the lower the memory gets, the more likely Android will call up the task killer built into Android and start shutting things down so there's enough for everything. the lag happens often when multiple kill calls are being done, and when those particular apps attempt to restart shortly after. in reality it's not Android that's at fault, it's the app's developer who set the priority so high that it's 'never close/kill' or is placed on the list of apps that Android kills last, so they end up being RAM hogs.
Many apps will in fact shut down for the most part if you use the 'back' button or softkey to get out of them, but if you hit the home button/softkey, it will often run in a minimized state, using memory when it shouldn't or when it's not efficient, awaiting you to resume it and have it load faster. the more apps you got 'minimized' the more the device might slow down as things get filled up.
You should be able to get a logcat viewer in the Play Store, it will be an app you load up and a live-updating maintenance log similar to Airbus maintenence messages will scroll as things happen. pay special attention to alerts in red 'with an E: designator meaning ERROR' or in yellow with a 'W:' designator for WARNING. the latter often shows messages like 'low memory--no more background processes' and if you see that, there's something wrong. if it displays the app's name or service, i'd go through and uninstall that app and/or any heavier apps to see what happens. for the most part, logcats are nonsensical, but those entries are ways of pointing to where the problem might be. if the device suddenly reboots itself, it's often followed by a short 'E: OOM Panic occurred, restarting'. Android usually will restart when it officially runs out of available memory and the kernel crashes, or panics. but you'll only see that message for a split second before it reboots, which will often clear the log.