Out-of-the-box, Smoobu sites are developed for optimization, focusing on real-world interactions and, ultimately, Google's Core Web Vitals.
Optimizing is an ongoing practice at Smoobu. We continue to stay up to date and implement changes to ensure continuous improvements.
Here’s an overview of the built-in optimizations that occur automatically. While this list highlights many key processes, it's not exhaustive.
-
Image Optimization
-
Video Optimization
-
Lazy load images (for more information, see Lazy Loading and Fonts)
-
Lazy load heavy widgets
-
CDN Static Resources
-
Defer non-critical CSS
-
Minify CSS
-
Extract Critical CSS
-
Avoid invisible text during font loading
-
Optimize WebFont loading and rendering
-
Reduce WebFont Size
-
Reduce JavaScript payloads with code splitting
-
Minify and compress network payloads
-
Preload critical assets to improve loading speed
-
Serve static assests with efficient cache policy
-
Preconnect to required origins
-
Initial server response time is short; <250 ms
-
Avoid multiple page redirects
-
Preload key requests
-
Avoids enormous network payloads (files larger than 5mb)
-
Minimize third-party usage
-
Third-party code blocked the main thread for 180 ms
-
Avoid large layout shifts
-
Use passive listeners to improve scrolling performance
-
WebP images (all images have a WebP generated version)
-
Brotoli compression
-
Continued improvements of lazy loading for new widgets
-
Improvement in how custom widgets load
-
Videos with auto compress
-
Moved nearly all assets to CDN
-
Concatenating CSS files (fewer requests)
-
Continued Critical CSS improvements
Comments
0 comments
Article is closed for comments.