Did change #1 => little bit faster (but not significant)
Didn't do change #2 => not quite sure if it helps that much
Did change #3 on a few pages => performance got quite better, but very limited to the type of page
Is it reasonable to also set caching for articles.html ?
I still think, the size of the images is killing me (article images).... 10-20 pictures of about 100kb is summing up to 2+MB for the first load... this just takes time.... why is IP.content still not able to resize images properly?
with this changes: is it fxed now, that RSVP's showing up in recurring events, do count for all events (so if I RSVP on event on the 1st, do I see myself RSVP'ing on 5th anymore, if this is set-up recurring) - because that's what's happening right now.... still
1.) Article image size - My experience, if i use a 3000x5000 pixel article picture, it will press this 5 megabyte file into 225 pixel wide image... same size, no resizing of the original image but using the original image 1:1 => what does your fix fix exactly? (I also don't really get, where this would be done)
2.) Caching - I'm not aware of setting any time (15 mins as you mention) option for the caching... all I know, is this "cache this page" check-box at the page details - and it says "Cache Lifetime" and I didn't connect lifetime with 15 mins ;).... so this is recommended to use, also if ip.content blocks are involved?
3.) Do you use the body in your listing template? => if you mean the article body, yes ... I don't use the teaser text, only the article body => so this is also recommended to set? (truncate 255)
I manually stripped down every article image and took a look at the filesize... so this is not the root cause for the loading times.
Generating the site itself is the big waiting factor here and I don't know how to optimize it further (no fancy plugins/addons/etc.) - just plain ip.content - where can I turn some screws to optimize these times, except showing not so many articles per page
regarding the caching => as said, when I use a block which should show a random order of articles => this can't be cached, or could it somehow?
I can't find any modification or already existing thread, about integrating a spreadshirt-shop in IPB (or IP.content). Right now I'm using a very ugly Iframe.... are there any best practices or threads/mods I didn't recognize for including shops like spreadshirt on the own board?
I'm not very satisfied with the loading speed of the IP.content articles... for example the overview or particular articles are taking quite some time and are much slower, than the board. I've taken a look at the article images (as they don't get resized properly - resized every article image by manually!) but it's still very slow.
I'm thinking about using the caching of IP.content but this is only available for apges and not for articles.... what else can I do, to get a performance boost in IP.content, as this is already a very relevant SEO-factor
another question about caching: I think I won't be able to cache the index-frontpage, as there is a dynamic article block showing a random order of articles... or?