The content method does not do anything special apart from setting the html contents of a particular element, and re-calculating the pager.
Here is the actual implementation:
However, putting up to 100 images in the widget (and scrolling through them) will affect the browser performance for sure. A thing which might
help would be to recycle older pages somehow - by replacing them with hollow placeholders, for instance.
The other thing which comes to mind (much more complicated, though) is to hide the pager and cycle and dynamically rotate 3 (or maybe 5) items, changing their contents (something like endless scrolling).
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI