Tweet
Changes have been made to how vBulletin 5 handles images (and linked videos). Previously they resized images with CSS. This isn't a good method when it comes to performance because download sizes are still the same. However it is a reliable method for showing multiple image sizes in different locations. We've since changed this (don't think it is deployed yet) where we store multiple sizes per image to cut the download down. So unless images are being embedded fullsize, it should become more friendly. The trade off though is additional storage, either in the file system or the database for the multiple images.
With linked videos, we used to immediately embed the iframe from the provider like YouTube. Now the system will retrieve a thumbnail image and show it as well. Clicking on the image will load the video, replace the image and play the video. This lowers perceived issues from embedding third-party content in a page.
Here is a "bucket" with a few of the things they've done for front-end performance:
With linked videos, we used to immediately embed the iframe from the provider like YouTube. Now the system will retrieve a thumbnail image and show it as well. Clicking on the image will load the video, replace the image and play the video. This lowers perceived issues from embedding third-party content in a page.
Here is a "bucket" with a few of the things they've done for front-end performance:
Comment