Performance Optimization: CSS Classes vs. Configurable Components in WeWeb

Ask us anything Tips and Hacks
1

Hi everyone,

I’m trying to better understand how WeWeb builds/renders elements from the editor, specifically in terms of performance and best practices.

Context

  • When creating elements in WeWeb, I want to ensure that my project is optimized for performance.
  • I’m unsure whether it’s better to rely on CSS class configurations or use configurable components for styling and functionality.

Questions

  1. Are there any performance differences between using CSS classes versus configurable components?
  2. Is there a best practice in WeWeb for ensuring faster rendering and maintaining a clean project structure?
  3. Does the WeWeb rendering engine prioritize one method over the other, or does it depend on the use case?
2

I don’t have concrete data to back this up, but from experience, I don’t think it matters either way. Even old devices can run a WeWeb app extremely smoothly regardless of approach.

The things that make a much more noticeable impact are your workflows and application logic. Also managing the amount of rendered elements per page.

If you have well thought-out logic and efficient use of containers and divs, this will ensure everything stays speedy.

1 Like