Also, if you’re not preloading the next/prev post, the slide effect is going to be lost because a script will have to query the database via http, retrieve the data, parse/format it, and replace the current page’s content AFTER the user clicks next/prev. The user will likely see their cursor spinning as this occurs, and the user may never see the next page if there’s a problem while the script is trying to pull this data together dynamically.
If you’re hoping for your content to be indexed by Google or any Search engine at all, replacing a page’s main content via http, as you’re suggesting, is the worst thing you can do. The method will make it impossible for a search engine to see your page’s content if the content isn’t simply hidden from humans or the content isn’t retrieved/written as the page is reloaded to a new page. The bot will see a blank page because the content will not be hardcoded in the source. It won’t find the next/prev pages either if you pull a post via http and have it magically replace the current page’s center content without creating the physical html. This approach would create an illusion of content, visible by humans only. Sliders preload to enable the smooth sliding effect. There’s no delay if the content exists in hidden form. This preload method allows users who have javascript turned off to still see all of the posts (no slide show but there’s still content), and it allows search engines & screen readers to see all of the content in the category, as well. If you’re not reloading the page by simply clicking “next/prev” to a new page of content and you’re not sliding hidden content into view, then you’re setting yourself up for a whole bunch of issues, like zero content for any visitor who is not using a modern visual browser with javascript and xml http+ajax enabled.
With all this said, don’t be silly — you don’t want what you think you want. There’s a very good reason for why sliders preload & hide/unhide content.
