In the normal course of events while surfing traditional mobile sites, jQuery Mobile will mark each page as the external page, which will cause the page to be removed from the Document Object Model (DOM) once the user navigates away from that page. The idea behind this is that the browser will manage DOM weight because low powered devices may not have as much memory to dedicate to their browsers. External pages will likely still be in the device cache for quick recall. So reloading them should be lightning fast. If you want to learn more about how jQuery Mobile handles this behavior, check out http://api.jquerymobile.com/page/#option-domCache.

jQuery Mobile has done a great job at managing DOM weight through normal means. However, when we dynamically create pages, they are not automatically deleted from the DOM on exit. This can become especially overwhelming if there are a lot of them. We could easily overwhelm the browsers on those low powered devices. If...