Was hoping someone from the WeWeb team could clarify a couple points on static vs. cached collections.
How do they compare for:
My assumption is that they’re the same on the SEO side, but will load much faster because of the caching.
Thanks!
Actually, static is better for SEO, as every page using a static collection will be pre-rendered (and you’ll be able to use the collection to create static collection pages).
Cached works like dynamic, but fetches data from our servers. It’s helpful when your backend has strong rate limits or slow response times (like Airtable).
@Quentin is there a limit to static pages? We’re building a directory-style site of events with dynamic information from a database. I would imagine we’d eventually have tens of thousands of static pages for historical reference on everything related to an event. Is that supported / is there a better way to do that? Load speed is of utmost importance for our users, as well as build / publish update time for us developing it long term.
Thanks for the reply.
Is there a way to cache the content on my site through static collections/pages?
I’m trying to improve page load speed, and I think caching is the main issue (but happy to apply any other recommendations).
Is it possible to cache static images?
I’m seeing the images being pulled from Xano every time I load the page, but I don’t think that’s optimal.
You could host your images elsewhere for better performance.
How many images are you talking about here and when are they displayed.
Appreciate you taking the time to reply @jaredgibb
The amount of images depends on the page, but anywhere from 1-125 (75x75 pixels each)
Asides from the images, another thing that stands out is tablet + mobile css loads on desktop (which seems pretty strange)?
Figured out how to improve image load speed. In case other people come across this same issue, here’s what I did:
I’ve been playing with storing images in a google cloud storage bucket and it’s working phenomenally for me!
Hey guys, thanks for the contribution. I seem to be having a similar issue when loading content on mobile/tab. The only difference from the suggestions provided so far to improve load times, seem to be that I use ImageKit as my CDN for the background images within my collection cards. The current behaviour is one that loads correctly, but when I start scrolling down, the entire site (except nav bar) appears white before they slowly start appearing after about 5-10 secs. Likewise, when I scroll back up, it has the same white bg effect.
Should I be doing some form of caching or dynamic loading or pagination? The current assumption is that each user could have about 10-15 of these cards on their page. With my test account, I am trying to load about 30 of these and I must say the experience is rather dismal.
Any help or tip is appreciated. Thanks in advance!
Hey, are your images lazyloaded?
You can see it in the editor here:
