Dynamically loading content through the use of AJAX (
xmlHttpRequests) is a common feature in most websites. Almost everywhere you go, you’ll see dynamically loaded content, in various shapes and forms, and of differing scales. To many, this is a great advantage; it is an advantage to the user, since they spend less time waiting for pages to load, since the page does not have to be refreshed. For the individual or business, this saves bandwidth, since after the initial page is loaded, only further required content is sent to the user, not the entire page.
In this sense it’s important that if parts of your website that rely on dynamically loading content are fundamental to the operation of your site, you include static methods of allowing the user to access that content. Twitter does this very well:
This is worked around by actually making the “More” button a link, which has the
href set to a static page representing the “page” of data that would be returned if the AJAX function was called; for example, the static page for the second page on my Twitter profile is:
Obviously, implementing static pages for certain features of your site isn’t always necessary; but if the feature allows the user to access content or data that is fundamental to the working of your site, you should. In this way you cater to a larger proportion of your users, and do not simply block them out.