TheWorldNewsMedia.org

It might seem a little odd starting a blog on increasing Invision Community's speed with the word "lazy",  but I'll explain why this is a good word for performance shortly.
Earlier this year, Google announced that page speed is a ranking factor.
Simply put, if your site is slow, it will be ranked lower in Google's search results.
It is always a challenge making a large application like Invision Community as efficient as possible per page load. A single Invision Community page can pull in widgets from multiple applications as well as a lot of user-generated content with attachments, movies and images used heavily. 
This is where being lazy helps.
Lazy loading is a method by which attachments, embeds and images are not loaded by default. They are only loaded when the viewer scrolls down enough to make them visible.
This allows the page to load a good deal faster now it doesn't have to load megabytes of images before the page is shown as completely rendered.
I was going to take a fancy video showing it in action, but it's hard to capture as the system loads the media just before you get to it, so it looks fairly seamless, even with sluggish connections.

Not the most dynamic image, but this shows the placeholder retains the size of the image
In addition to image attachments, we have also added this lazy loading to maps and Twitter emoji images.
Improving non-image attachments
Once we had implemented the lazy loading framework, an area we wanted to improve was non-image attachments.
We have listened to a lot of the feedback we had on this area, and have now made it very clear when you add an attachment into a post. We've even returned the download count now it's being loaded on demand.

Using attachments when posting
All the letters
When we first implemented the letter avatars in 4.3, we discussed whether to use CSS styling or use an image.
We decided to go with an image as it was more stable over lots of different devices, including email.
We've revisited this in 4.4, and switched the letter avatars to SVG, which are much faster to render now that the browser doesn't have to load the image files.
Other performance improvements
We've taken a pass at most areas with an eye for performance, here is a list of the most significant items we've improved.
Several converter background tasks have been improved, so they work on less data Duplicate query for fetching clubs was removed in streams Notifications / follower management has been improved Member searches have been sped up (API, ACP live search, member list in ACP, mentions, etc.). Stream performance has been improved UTF8 conversions have been sped up Elasticsearch has been sped up by using pre-compiled queries and parameterisation, as well as the removal of view filtering (and tracking) HTTP/2 support with prefetch/preload has been added Several PHP-level performance improvements have been made Implemented rel=noopener when links open a new window (which improves browser memory management) Several other performance improvements for conversions were implemented that drastically reduce conversion time IP address lookups now fetch IP address details from us en-masse instead of one request per address Cache/data store management has been streamlined and centralised for efficiency Many background tasks and the profile sync functionality have all been improved for performance Brotli compression is now supported automatically if the server supports it Redis encryption can now be disabled if desired, which improves performance Phew, as you can see, we've spent a while tinkering under the hood too.
We'd love to hear your thoughts. Let us know below!
This blog is part of our series introducing new features for Invision Community 4.4.

We are well into development on IPS Community Suite 4.2 and are excited to start announcing all the new features and improvements.
Our next big release is focused on engagement with your members. You will see enhancements to our Reputation system, new ways to encourage people to register on your community, and enhancements to existing features to make them more interactive. There are also entirely new capabilities we cannot wait to show you ranging from new ways to organize content to tools to help promote your community.
Version 4.2 also features a refreshed AdminCP and default front-end design. Theme changes in 4.2 are mostly in the CSS framework so your existing themes will either work without issue or require minor changes to work in the new version.
Over the next several weeks we will be posting news entries with previews of upcoming features fairly often. Be sure to follow our News section, our Facebook, or Twitter to stay up to date.
We expect IPS Community Suite 4.2 to be out in mid-2017 with a public preview available sooner.
Everyone at IPS has worked very hard on this update and we think you will love it!

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite comes with a default profile photo which is used when members have not set a profile photo for their account. While this model has served the software well for years, we felt it was time for an update to the software to keep pace with current internet trends. This has led to one of the latest changes you can expect to see with version 4.2: letter profile photos
When upgrading you will be asked if you wish to use letter profile photos, or if you wish to stick with the generic per-theme default profile photo that is used presently. You can change your mind any time after upgrading by adjusting the setting in the AdminCP as well.

AdminCP members list
We have tested many languages to ensure maximum compatibility. The font used in the image is automatically selected based upon the characters to be written to the image, so sites that have more than one language will see compatibility for all of the profile photos that are created automatically.
The colors are not set for each letter. You will notice in the screenshot that each "A" letter photo has a different color. They are chosen randomly when generated.

Letter photos in a sidebar widget
We hope that this change helps bring your communities to life with a little more style, flair, and uniqueness for each new user on your site.
 
Developer Note
The code is structured in such a manner that third party developers can further extend the feature with plugins. The methods for writing text to images are exposed through our central \IPS\Image class introducing new possibilities in your own custom code.

This entry is about our IPS Community Suite 4.2 release.
Social Sign In has long been a feature of the IPS Community Suite but we are always looking for ways to make interaction easier for your visitors. A small but significant improvement we are able to add for 4.2 is to include social sign in links directly at the point where your customers are ready to contribute.
 

Hassle free inline sign in brings your customers right back where they need to be to comment
Visitors are much more likely to comment when the registration process is as fluid as possible and social sign in has fast become a familiar and efficient way of doing so. After signing up via these methods users are logged in and brought right back to where they started ready to comment.
Feedback from our testers has already shown that this change has an immediate effect on the volume of new registrations and we look forward to making it widely available with 4.2.