Last post May 25, 2014 09:05 AM by AidyF
May 24, 2014 11:18 PM|CASPartan|LINK
Interested to hear other people's opinion...
I'm redesigning a news website for a client. Traffic is about 6,000+ visitors a day.
We'll be putting up a new section on the site (which will appear on the homepage and inside pages). LATEST News and MOST POPULAR News tab.
I'm debating whether to use ajax .load to populate these 2 sections of the site, or just pre-populate these sections completely before sending the complete page to the user.
Pros of Ajax loading:
Smaller initial download of page. The Latest and Popular News section will then be downloaded via 2 separate ajax calls to load the DIV with content.
The main content of the site is immediately populated, and these extra sections will be delayed by a few milliseconds (due to ajax call) -- giving faster appearance/performance
Possible impact to SEO. Spiders may not see the dynamically loaded content. (There's a workaround for this though.)
(2) extra calls to the server, per user, per page load.... but I'm thinking these 2 pages may be cached by IIS, so future calls to the same page will be served from memory by server?
Interested to hear your opinions... what would you choose and why?
May 25, 2014 09:05 AM|AidyF|LINK
I don't really see how your pros are pros. The additional data has to be downloaded anyway, only you're also downloading the relevant script in orther to populate the news. I'd only consider ajax if retrieving the news takes a long time to do. Or if the
news automatically updates over time, you could do the initial download normally and then use ajax to update the news. Changing content is usually a good thing in terms of SEO and using js to populate content means that search engines don't see your content