Styling & Publishing Feeds

Feed Loading Speed Optimization

Curator feeds are built for speed using lightweight JavaScript and CDN-hosted assets. These tips will help you maximize performance and ensure fast loading times.

How Curator Optimizes Performance

Curator includes built-in performance optimizations to help balance speed and user experience. You can choose from three lazy loading options:

  1. Show feed when page loads (Default) — The entire feed, including images and content loads as soon as the page opens.

  2. Show feed when it is in view — The feed loads only when it becomes visible on the screen (for example, after scrolling). Both the content and images are lazy-loaded, which helps improve initial page load speed.

  3. Load feed code on page load, and load feed content when in view — This hybrid option loads the feed’s structure (such as titles and layout) when the page opens, while images and media are lazy-loaded and appear only once the feed is visible.

Each option has its own advantages depending on your website’s setup and priorities.

Best Practices for Speed

1. Limit the number of posts displayed Show 12-24 posts initially with "Load More" instead of loading hundreds at once.

2. Choose efficient layouts Grid and List layouts are lighter than complex animations like Carousel or Cover Flow.

3. Minimize custom CSS Keep your style overrides simple. Heavy CSS rules can slow down rendering, especially on mobile.

4. Use lazy loading for multiple feeds If embedding multiple feeds on one page, consider loading secondary feeds only when scrolled into view.

Test your page speed with tools like Google PageSpeed Insights or GTmetrix to measure the impact of your feed and identify optimization opportunities.

Avoid Performance Pitfalls

  • Avoid blocking scripts: Always use the standard async embed code

  • Don't override with heavy JavaScript: Custom JS interactions can slow down your feed

Mobile Performance

Mobile users are especially sensitive to slow loading. Curator's responsive design automatically serves mobile-optimized layouts, but you can further improve mobile speed by:

  • Reducing initial post count on smaller screens

  • Using simpler templates on mobile devices

  • Testing on actual mobile devices, not just browser emulation

Was this helpful?