Matt

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

I was fortunate enough to be invited to speak on the Expert Focus podcast,  hosted by experienced community manager and public speaker, Claire Dowdall.
Claire has significant experience in managing and developing strategies for increasing Facebook Group engagement for high profile speakers and entrepreneurs, while my background is with independent communities.

This set us up nicely for a lively conversation to really pull apart what makes for a successful community, and what platforms to consider when starting out.
From Expert Focus:

I really enjoyed speaking with Claire, and I hope you find a little time to tune in.

Listen now:
iTunes link for Apple devices On Spotify On all other devices

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

I was fortunate enough to be invited to speak on the Expert Focus podcast,  hosted by experienced community manager and public speaker, Claire Dowdall.
Claire has significant experience in managing and developing strategies for increasing Facebook Group engagement for high profile speakers and entrepreneurs, while my background is with independent communities.

This set us up nicely for a lively conversation to really pull apart what makes for a successful community, and what platforms to consider when starting out.
From Expert Focus:

I really enjoyed speaking with Claire, and I hope you find a little time to tune in.

Listen now:
iTunes link for Apple devices On Spotify On all other devices

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

I was fortunate enough to be invited to speak on the Expert Focus podcast,  hosted by experienced community manager and public speaker, Claire Dowdall.
Claire has significant experience in managing and developing strategies for increasing Facebook Group engagement for high profile speakers and entrepreneurs, while my background is with independent communities.

This set us up nicely for a lively conversation to really pull apart what makes for a successful community, and what platforms to consider when starting out.
From Expert Focus:

I really enjoyed speaking with Claire, and I hope you find a little time to tune in.

Listen now:
iTunes link for Apple devices On Spotify On all other devices

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

I was fortunate enough to be invited to speak on the Expert Focus podcast,  hosted by experienced community manager and public speaker, Claire Dowdall.
Claire has significant experience in managing and developing strategies for increasing Facebook Group engagement for high profile speakers and entrepreneurs, while my background is with independent communities.

This set us up nicely for a lively conversation to really pull apart what makes for a successful community, and what platforms to consider when starting out.
From Expert Focus:

I really enjoyed speaking with Claire, and I hope you find a little time to tune in.

Listen now:
iTunes link for Apple devices On Spotify On all other devices

I was fortunate enough to be invited to speak on the Expert Focus podcast,  hosted by experienced community manager and public speaker, Claire Dowdall.
Claire has significant experience in managing and developing strategies for increasing Facebook Group engagement for high profile speakers and entrepreneurs, while my background is with independent communities.

This set us up nicely for a lively conversation to really pull apart what makes for a successful community, and what platforms to consider when starting out.
From Expert Focus:

I really enjoyed speaking with Claire, and I hope you find a little time to tune in.

Listen now:
iTunes link for Apple devices On Spotify On all other devices

I was fortunate enough to be invited to speak on the Expert Focus podcast,  hosted by experienced community manager and public speaker, Claire Dowdall.
Claire has significant experience in managing and developing strategies for increasing Facebook Group engagement for high profile speakers and entrepreneurs, while my background is with independent communities.

This set us up nicely for a lively conversation to really pull apart what makes for a successful community, and what platforms to consider when starting out.
From Expert Focus:

I really enjoyed speaking with Claire, and I hope you find a little time to tune in.

Listen now:
iTunes link for Apple devices On Spotify On all other devices

I was fortunate enough to be invited to speak on the Expert Focus podcast,  hosted by experienced community manager and public speaker, Claire Dowdall.
Claire has significant experience in managing and developing strategies for increasing Facebook Group engagement for high profile speakers and entrepreneurs, while my background is with independent communities.

This set us up nicely for a lively conversation to really pull apart what makes for a successful community, and what platforms to consider when starting out.
From Expert Focus:

I really enjoyed speaking with Claire, and I hope you find a little time to tune in.

Listen now:
iTunes link for Apple devices On Spotify On all other devices

I was fortunate enough to be invited to speak on the Expert Focus podcast,  hosted by experienced community manager and public speaker, Claire Dowdall.
Claire has significant experience in managing and developing strategies for increasing Facebook Group engagement for high profile speakers and entrepreneurs, while my background is with independent communities.

This set us up nicely for a lively conversation to really pull apart what makes for a successful community, and what platforms to consider when starting out.
From Expert Focus:

I really enjoyed speaking with Claire, and I hope you find a little time to tune in.

Listen now:
iTunes link for Apple devices On Spotify On all other devices

I was fortunate enough to be invited to speak on the Expert Focus podcast,  hosted by experienced community manager and public speaker, Claire Dowdall.
Claire has significant experience in managing and developing strategies for increasing Facebook Group engagement for high profile speakers and entrepreneurs, while my background is with independent communities.

This set us up nicely for a lively conversation to really pull apart what makes for a successful community, and what platforms to consider when starting out.
From Expert Focus:

I really enjoyed speaking with Claire, and I hope you find a little time to tune in.

Listen now:
iTunes link for Apple devices On Spotify On all other devices

Are you a vBulletin admin looking to stay on the leading edge of online communities? 
As an IPS client who frequents the Invision Community support forums on a daily basis, I often run across existing or former vBulletin admins looking to migrate to IPS.  In fact, based on my not-so-scientific survey, vBulletin is one of the most popular platforms from where admins migrate. Many of the vBulletin users are professional administrators looking for a stable company, rapid development, and a trusted platform to power their communities into the future. 
I interviewed 6 former vBulletin admins who are now Invision Community clients.  Most of these vBulletin admins have 10+ years of experience running successful forums, so their input was especially insightful.   
“I love the design of the admin and moderation back-end, a real treat after living with the antiquated and confusing vBulletin back-end.” -- @cfish
“I like the well-thought concept, the details, and abundance of features and functions.” --@Ramsesx
I’ve compiled the top 10 questions and answers from their interviews and the forums specifically for vBulletin admins for an insider’s perspective on how to convert from vBulletin to Invision Community.  You can also read their full interviews in my Community Guide attached at the bottom.
10. What is the typical lifecycle of Invision Community and what new features come out?
Invision Community is currently on 4.4.  It’s a great time to be migrating as both the software and converter are very mature.  You’ll be able to take advantage of all the new features from Invision Community 4.x such as Social Clubs, Subscriptions, SEO updates, and GDPR updates. 
In general, IPS publishes one major update like 4.4 once a year, with several bug fixes, security updates, and enhancements throughout the year.  The best place to read about Product Updates is the official IPS Blog in Product Updates.
9. What are the pricing options and how do they compare to vBulletin?
IPS is comparable in pricing when compared to vBulletin depending on your choice of apps.  The self-hosted option is cheaper when considering support and upgrades.    
The pricing for an active license is simple, easy, and comprehensive.  A new license includes professional ticket support, forum support, access to new upgrades, and managed spam service for 6 months.  Renew again in six months to continue those benefits.  If you choose not to renew, your software will continue to work.
8.  Is the software mobile ready like vBulletin?
Yes, the software is responsive by design.  This means the community naturally fits and beautifully displays in any device size, giving you a consistent look-and-feel across all devices.  Try it now by resizing your window! 
It also means you don’t need to pay for any extra “mobile bundles.”  This approach to mobile design was one of the reasons why @cfish chose IPS: “I didn’t like vBulletin’s approach to mobile. The IPS approach to responsive web design was inline with my own thinking.”
7.  What are the official Invision Community apps and how do they compare to vBulletin? 
@Steve Bullman converted to IPS because “IPS seemed to offer a better all-round package for what I needed.”  One of the biggest reasons for considering IPS is a broader approach to community.  Whereas vBulletin focuses only on Forums and Blogs, IPS empowers you to build a suite of applications customized to your needs.  Mix and match apps like Gallery, Blogs, Downloads, Pages, and Commerce to build a modern community with resource directories, databases, paid subscriptions, albums and more that go beyond forums.   
You can read more about the apps in Features. Calendar and Clubs are included for free! 
6.  What will be migrated from vBulletin? 
The free converter app will migrate all of your member and content items from vBulletin 3.8.x, 4.x, and 5.x.  This includes members, private messages, member groups, ranks, forums, topics, posts, and attachments.  You can view the full list on Migrate and choose your vBulletin version from the list of choices.
Obviously, you will not be able to migrate any custom themes or custom modifications.  @ChristForums adds, “I wish I had known that the converter was so easy to use and migrate from Vbulletin 5.”
5.  What are the channels for support? 
Every active license comes with professional ticket support, which should always be your first source of contact.  @Markus Jung highlights “fast support” as the item he appreciates the most about his license.  You can also obtain help from the community forums, help guides, release notes, and other public resources. 
If you’re not an IPS client yet, you can post in Pre-Sales forum or email sales@invisionpower.com. 
4.  How do I prepare my community?
The six admins that I interviewed offered several tips for new Invision Community owners.  Prior to the conversion, you should read through the converter package to see what will convert and redirect.  You should purchase other Invision Community apps in advance to fully convert vBulletin items as needed; not delete any old content since Invision Community includes an archive function; and not make drastic changes to allow members a chance to become accustomed to the new forum. 
3.  What will happen to my traffic and URL redirects? 
The free converter app will redirect your existing URLs.  This includes forums, topics, posts, member profiles, print view pages, archived content, attachments, and tags.  You need to leave your converter installed after migration to ensure the redirects will work.   
AlexWebsites wrote, “the converter came with built-in redirects and I was able to redirect most of my traffic. Traffic recovered within a few months.”
2. What are the server configuration and database requirements?    
If you choose cloud, then Invision Community will manage the hosting. 
If you choose on-premise, you can use the free ‘Get Ready’ compatibility file to check your server.  The latest version of Invision Community 4.4 requires:
PHP 7.1.0 or higher (7.3.x is supported) MySQL 5.5.3 or higher (5.6.2 recommended).  1. How stable is the company? 
Other companies lost their development talent. Other companies were bought and sold by multi-media conglomerates. Other companies have a history of lawsuits.
Through it all, Charles, Lindy and Matt have been here since the beginning providing steady leadership to Invision Communities everywhere.  If you’re looking for stability, it’s nice to know you can rely on the same people who started the company.  For serious and professional vBulletin admins looking to transition, you know you’re not just buying into the software, but investing in the development team, staff, and platform for years to come. Ramsesx shared his personal story: “I always prefer the best for my community from where I earn my income.  An important aspect was the longtime outlook.  Invision Community gave me the feeling of being trustworthy, they are more than 17 years in the forum software market.” 
It’s no wonder that so many successful vBulletin admins feel the same after moving to Invision Community.  You get stability, years of experience, a deep understanding of online communities, and a dedication to development that continues to innovate.  It’s time to bring your vBulletin community over to Invision Community! 
Bookmark this page for future reference and download the Community Guide for experiences from real clients who converted from vBulletin.  Much appreciation to @AlexWebsites @cfish @Christforums @Markus Jung @Ramsesx @Steve Bullman for participating in the interviews.  
- Joel R
Community Guide vBulletin Migration to Invision Community.pdf

I'm only one month in to starting a new community and I've already learned a huge amount. I was a little apprehensive at first but I'm taking things one step at a time and I'm happy with how things are going so far.
The points I'm going to raise are working for me but I'm a beginner and running a website of any description is new. Nothing here is guaranteed and I hope to receive comments from established community admins so I can continue to improve.

The first thing I realised is that I wasn't actually starting a community but instead I'm going to be bringing new tools and ideas to an already existing one. My chosen subject is broad (Dogs) so there is already a well established real life community globally. My aim therefore is not to replicate already available content but to reach this community with unique content and encourage them to contribute their own. More on that later but before I could do that I needed something they could visit.

The new community site
Get Started
You can spend days and weeks planning and writing business plans and these are all good things to do alongside everything else but they shouldn't stop you getting started. The only thing that really mattered to me was starting on the actual idea and to do that all I needed was a platform. You've probably already guessed but Invision Community was chosen for this as it offered multiple apps that would allow me to have both long form articles and forum content. There's also the monetisation options that appealed to me but I am not yet using. It's good to know they are there when I'm ready though. 
I also considered Wordpress but it lacked the community tools I was already sold on.
Rope in friends and family and use their skill sets
I'm not scared to admit where I need help and as I have hit problems or things I don't know I have called in favours. I don't have a large budget for stock photography subscriptions so a friend is providing photos in exchange for attribution. My fiance is more technically minded so he has helped with some of the set up and help with Invision Community features is only a support ticket away.
There is plenty of general information a quick web search away too but some topics are complex and I thought that if I could free up at least some of my time I can keep focussed on the direction. 
Help can be as simple as nudging friends into posting new topics or comments to get some initial activity and momentum. It's also a good test to make sure you have everything set up with your registration process and identify some potential problems.
These helpers are also now active members of the site of course so it's a two for one. I'm sure they'll be calling in return favours at some point but that's fine, they've earned it.
Encourage all contributions even if you don't agree with them
Coming from a primary school teaching background I see kids come up with lots of crazy and novel ideas all the time, they might sound silly but you never know, they may grow into something bigger. My aim is to foster a sense of community and belonging and people of all ages who have their ideas valued tend to stick around. If an idea doesn't work that's fine but you never know what will work so I'm trying lots of things and encouraging innovation. The forums are a great tool for this as everything doesn't need to be rigidly structured.
Be passionate and confident about your subject matter
Perhaps my top tip…If you don't value your own thoughts and actions then how can you expect others to? Show your enthusiasm and knock away negative thoughts and doubts. 
Use all of your tools
Once you've encouraged your initial core group of members, you need to keep them coming back. So far I've had success using the bulk mail feature for a monthly newsletter to rekindle the interest of early members who may no longer be as active. I was warned about bad email practices so I have our notification defaults set very loosely as I want to build trust by not spamming. Everything I send is opt-in and using the newsletter signup block I've been able to make this prominent but not obtrusive. I'm worried I might be missing out by not being aggressive enough with email but it's a risk I'm taking to hopefully get better long term members.
Get involved with your member activities and conversations
Join in with conversations on your community where it makes sense and be as active as possible. You're running a website but to do so you don't always need to be in front of a computer. Speak to your members face to face as well as through the keyboard. I've been going on local dog walks with clubs and other community groups which is a great chance to network and give your members and potential members the chance to see the people behind the website. If there are events or shows in your field get involved and spread the word verbally. I'm talking to dog owners face to face about behavioural issues and always in the back of my mind is the fact this could be discussed on the website to help others and build activity. Over time these "real world" relationships should also be represented on the website too.
Don't get distracted
I've got into the habit of using a reminders app to keep track of future things I want to do. It is tempting to start lots of things every time you have a new idea but that can take your mind off what is actually important right now. Don't forget about these ideas though, make a note and come back to them later.
Approvals and applications for things can also take time. I found myself sometimes sitting around waiting for adsense accounts to be approved or Facebook apps to be verified for sign in. Don't let this downtime be unproductive.
Keep writing new content
What we have started as new community admins isn't easy, it's going to be a long haul so you need to be consistent and regular with updates. On that note I have a breed profile about Chow Chows to write.
Thanks for listening to my ramblings and if you have any more tips please let me know in the comments.
Helen is a year 3 international primary school teacher currently living in Slovakia. She loves dogs (of course), books, and reading whenever possible. She has travelled extensively for work, particularly in South East Asia and has experienced many amazing cultures. She is a qualified Zumba dance fitness instructor and is now building what she hopes to be an invaluable resource for dog owners.
https://doglymail.com/

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

I'm sure that most reading this blog are running an up-to-date Invision Community and enjoying all the benefits of a modern community platform.
Little things that get taken for granted now, like being able to view your community on a mobile phone without pinching and zooming just to read a few posts and having multiple automated tools to deal with community toxicity and spam.
However, a little wander around the web soon uncovers some really old forum systems still somehow creaking along.
Amazingly, most of these communities are still used daily, often with millions of posts in the archives.
It might be tempting to ask why keep upgrading and investing in new versions of the software?
After all, if the community is still running just fine and getting daily visitors, then it's ok to do nothing, right?
But there is a hidden cost in doing nothing.
Security
This is the main one for me. Old platforms often have several published security vulnerabilities. Often these vulnerabilities are exploited by scripts that are shared around hacker communities. This means exploiting a website running an old version of a forum system is as simple as running a script and pointing it at your site.
Older forums are also less sophisticated. They rely on unsafe hashing methods to store passwords and lack vital features like two-factor authentication.
Also, consider that the server environment has to be maintained with out of date PHP and MySQL versions. It's a recipe for disaster.
Could your community survive a major exploit where data is downloaded into the hands of a hacker?
The cost could be fatal to your community.
Declining engagement
Even the most ardent of fans on your community will eventually tire of struggling to access your site on mobile devices.
I think back to 2002 when we created the first version of our software. We only had to focus on how it looked on a computer, so naturally, that influenced the design of the forum.
It's not so simple now. More and more of us are using mobile phones to access the internet. A recent statistic showed that mobile internet access outstrips desktop use 2 to 1; and for some countries, mobile internet access is almost the only way people get online.
It's just a matter of time before new members stop registering and engagement tails off.
Competition
At the end of 2018, there were 1.8 billion websites (I Googled it). The competition for attention has never been as fierce.
Your community may be the go-to place for your niche, but what if another community popped up running the latest version of a platform with all the features your members have been desperately asking for?
It may not take long until there is a massive drain from your community.
I'm sure there's a dozen reasons to make sure you're always re-investing in your community by upgrading to a modern platform. This blog merely scratches the surface.
For those of you that do invest and upgrade? You reap the benefits daily by ensuring you are doing the very best for your community by keeping it secure and accessible for most.
If you are on an older platform, now is the time to put some serious thought into making the move to something better.
I put together a little downloadable guide that might help too.
What do you think? Let me know in the comments below.

I'm sure that most reading this blog are running an up-to-date Invision Community and enjoying all the benefits of a modern community platform.
Little things that get taken for granted now, like being able to view your community on a mobile phone without pinching and zooming just to read a few posts and having multiple automated tools to deal with community toxicity and spam.
However, a little wander around the web soon uncovers some really old forum systems still somehow creaking along.
Amazingly, most of these communities are still used daily, often with millions of posts in the archives.
It might be tempting to ask why keep upgrading and investing in new versions of the software?
After all, if the community is still running just fine and getting daily visitors, then it's ok to do nothing, right?
But there is a hidden cost in doing nothing.
Security
This is the main one for me. Old platforms often have several published security vulnerabilities. Often these vulnerabilities are exploited by scripts that are shared around hacker communities. This means exploiting a website running an old version of a forum system is as simple as running a script and pointing it at your site.
Older forums are also less sophisticated. They rely on unsafe hashing methods to store passwords and lack vital features like two-factor authentication.
Also, consider that the server environment has to be maintained with out of date PHP and MySQL versions. It's a recipe for disaster.
Could your community survive a major exploit where data is downloaded into the hands of a hacker?
The cost could be fatal to your community.
Declining engagement
Even the most ardent of fans on your community will eventually tire of struggling to access your site on mobile devices.
I think back to 2002 when we created the first version of our software. We only had to focus on how it looked on a computer, so naturally, that influenced the design of the forum.
It's not so simple now. More and more of us are using mobile phones to access the internet. A recent statistic showed that mobile internet access outstrips desktop use 2 to 1; and for some countries, mobile internet access is almost the only way people get online.
It's just a matter of time before new members stop registering and engagement tails off.
Competition
At the end of 2018, there were 1.8 billion websites (I Googled it). The competition for attention has never been as fierce.
Your community may be the go-to place for your niche, but what if another community popped up running the latest version of a platform with all the features your members have been desperately asking for?
It may not take long until there is a massive drain from your community.
I'm sure there's a dozen reasons to make sure you're always re-investing in your community by upgrading to a modern platform. This blog merely scratches the surface.
For those of you that do invest and upgrade? You reap the benefits daily by ensuring you are doing the very best for your community by keeping it secure and accessible for most.
If you are on an older platform, now is the time to put some serious thought into making the move to something better.
I put together a little downloadable guide that might help too.
What do you think? Let me know in the comments below.

We want to ensure that converting from your existing community platform to ours is as seamless as possible.
While we do have a migration service available where we take care of everything for you, we do also offer a DIY option.
We took some time to overhaul the conversion process for those opting to convert using our free tools.
Ready to convert?
So you've just purchased your first copy of Invision Community, and you're ready to convert your existing site over from another software package. Great! We're glad you've made the decision to take your community to the next level!
You've already checked out our Migrations page, confirmed the software you wish to convert from is supported, and you're confident in your ability to work through the process. You install the Converters package and you're ready to go. 
Lets get started!
We have overhauled the converters to simplify the process. Beginning with 4.4, you will take the following steps to convert from another software package:
Rather than choose the application you wish to convert first, you will now choose what software you are converting from, which is a much more logical start to a conversion. Next, you will supply the database details for your source database (the database you wish to convert into your new Invision Community). Then, you will see a list of all applications that can be converted for the software package you are converting from. If any applications cannot be converted (perhaps because you were not previously using the corresponding application in your source software), a message will be shown indicating there is nothing to convert. If any steps require additional configuration, you will be able to specify those details here. And finally, when you submit that form - that's it! You're done, and you can sit back and let the conversion process on its own. Each step for each application will be completed automatically, and the conversion will be finalized automatically at the end. A progress bar will be shown, along with a textual indicator that outlines exactly what is being converted. What does it look like?
conversion.mp4 Here's a quick video to illustrate the new conversion process.
The system even remembers where you were at and automatically picks back up where you left off. Closing your browser, losing internet connectivity, or some other unforeseen issue won't stop you dead in your tracks and force you to start all over again.
We hope that these updates make it even easier to switch from another community platform.
 

I'm sure that most reading this blog are running an up-to-date Invision Community and enjoying all the benefits of a modern community platform.
Little things that get taken for granted now, like being able to view your community on a mobile phone without pinching and zooming just to read a few posts and having multiple automated tools to deal with community toxicity and spam.
However, a little wander around the web soon uncovers some really old forum systems still somehow creaking along.
Amazingly, most of these communities are still used daily, often with millions of posts in the archives.
It might be tempting to ask why keep upgrading and investing in new versions of the software?
After all, if the community is still running just fine and getting daily visitors, then it's ok to do nothing, right?
But there is a hidden cost in doing nothing.
Security
This is the main one for me. Old platforms often have several published security vulnerabilities. Often these vulnerabilities are exploited by scripts that are shared around hacker communities. This means exploiting a website running an old version of a forum system is as simple as running a script and pointing it at your site.
Older forums are also less sophisticated. They rely on unsafe hashing methods to store passwords and lack vital features like two-factor authentication.
Also, consider that the server environment has to be maintained with out of date PHP and MySQL versions. It's a recipe for disaster.
Could your community survive a major exploit where data is downloaded into the hands of a hacker?
The cost could be fatal to your community.
Declining engagement
Even the most ardent of fans on your community will eventually tire of struggling to access your site on mobile devices.
I think back to 2002 when we created the first version of our software. We only had to focus on how it looked on a computer, so naturally, that influenced the design of the forum.
It's not so simple now. More and more of us are using mobile phones to access the internet. A recent statistic showed that mobile internet access outstrips desktop use 2 to 1; and for some countries, mobile internet access is almost the only way people get online.
It's just a matter of time before new members stop registering and engagement tails off.
Competition
At the end of 2018, there were 1.8 billion websites (I Googled it). The competition for attention has never been as fierce.
Your community may be the go-to place for your niche, but what if another community popped up running the latest version of a platform with all the features your members have been desperately asking for?
It may not take long until there is a massive drain from your community.
I'm sure there's a dozen reasons to make sure you're always re-investing in your community by upgrading to a modern platform. This blog merely scratches the surface.
For those of you that do invest and upgrade? You reap the benefits daily by ensuring you are doing the very best for your community by keeping it secure and accessible for most.
If you are on an older platform, now is the time to put some serious thought into making the move to something better.
I put together a little downloadable guide that might help too.
What do you think? Let me know in the comments below.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

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.

I'm sure that most reading this blog are running an up-to-date Invision Community and enjoying all the benefits of a modern community platform.
Little things that get taken for granted now, like being able to view your community on a mobile phone without pinching and zooming just to read a few posts and having multiple automated tools to deal with community toxicity and spam.
However, a little wander around the web soon uncovers some really old forum systems still somehow creaking along.
Amazingly, most of these communities are still used daily, often with millions of posts in the archives.
It might be tempting to ask why keep upgrading and investing in new versions of the software?
After all, if the community is still running just fine and getting daily visitors, then it's ok to do nothing, right?
But there is a hidden cost in doing nothing.
Security
This is the main one for me. Old platforms often have several published security vulnerabilities. Often these vulnerabilities are exploited by scripts that are shared around hacker communities. This means exploiting a website running an old version of a forum system is as simple as running a script and pointing it at your site.
Older forums are also less sophisticated. They rely on unsafe hashing methods to store passwords and lack vital features like two-factor authentication.
Also, consider that the server environment has to be maintained with out of date PHP and MySQL versions. It's a recipe for disaster.
Could your community survive a major exploit where data is downloaded into the hands of a hacker?
The cost could be fatal to your community.
Declining engagement
Even the most ardent of fans on your community will eventually tire of struggling to access your site on mobile devices.
I think back to 2002 when we created the first version of our software. We only had to focus on how it looked on a computer, so naturally, that influenced the design of the forum.
It's not so simple now. More and more of us are using mobile phones to access the internet. A recent statistic showed that mobile internet access outstrips desktop use 2 to 1; and for some countries, mobile internet access is almost the only way people get online.
It's just a matter of time before new members stop registering and engagement tails off.
Competition
At the end of 2018, there were 1.8 billion websites (I Googled it). The competition for attention has never been as fierce.
Your community may be the go-to place for your niche, but what if another community popped up running the latest version of a platform with all the features your members have been desperately asking for?
It may not take long until there is a massive drain from your community.
I'm sure there's a dozen reasons to make sure you're always re-investing in your community by upgrading to a modern platform. This blog merely scratches the surface.
For those of you that do invest and upgrade? You reap the benefits daily by ensuring you are doing the very best for your community by keeping it secure and accessible for most.
If you are on an older platform, now is the time to put some serious thought into making the move to something better.
I put together a little downloadable guide that might help too.
What do you think? Let me know in the comments below.

I'm sure that most reading this blog are running an up-to-date Invision Community and enjoying all the benefits of a modern community platform.
Little things that get taken for granted now, like being able to view your community on a mobile phone without pinching and zooming just to read a few posts and having multiple automated tools to deal with community toxicity and spam.
However, a little wander around the web soon uncovers some really old forum systems still somehow creaking along.
Amazingly, most of these communities are still used daily, often with millions of posts in the archives.
It might be tempting to ask why keep upgrading and investing in new versions of the software?
After all, if the community is still running just fine and getting daily visitors, then it's ok to do nothing, right?
But there is a hidden cost in doing nothing.
Security
This is the main one for me. Old platforms often have several published security vulnerabilities. Often these vulnerabilities are exploited by scripts that are shared around hacker communities. This means exploiting a website running an old version of a forum system is as simple as running a script and pointing it at your site.
Older forums are also less sophisticated. They rely on unsafe hashing methods to store passwords and lack vital features like two-factor authentication.
Also, consider that the server environment has to be maintained with out of date PHP and MySQL versions. It's a recipe for disaster.
Could your community survive a major exploit where data is downloaded into the hands of a hacker?
The cost could be fatal to your community.
Declining engagement
Even the most ardent of fans on your community will eventually tire of struggling to access your site on mobile devices.
I think back to 2002 when we created the first version of our software. We only had to focus on how it looked on a computer, so naturally, that influenced the design of the forum.
It's not so simple now. More and more of us are using mobile phones to access the internet. A recent statistic showed that mobile internet access outstrips desktop use 2 to 1; and for some countries, mobile internet access is almost the only way people get online.
It's just a matter of time before new members stop registering and engagement tails off.
Competition
At the end of 2018, there were 1.8 billion websites (I Googled it). The competition for attention has never been as fierce.
Your community may be the go-to place for your niche, but what if another community popped up running the latest version of a platform with all the features your members have been desperately asking for?
It may not take long until there is a massive drain from your community.
I'm sure there's a dozen reasons to make sure you're always re-investing in your community by upgrading to a modern platform. This blog merely scratches the surface.
For those of you that do invest and upgrade? You reap the benefits daily by ensuring you are doing the very best for your community by keeping it secure and accessible for most.
If you are on an older platform, now is the time to put some serious thought into making the move to something better.
I put together a little downloadable guide that might help too.
What do you think? Let me know in the comments below.

I'm sure that most reading this blog are running an up-to-date Invision Community and enjoying all the benefits of a modern community platform.
Little things that get taken for granted now, like being able to view your community on a mobile phone without pinching and zooming just to read a few posts and having multiple automated tools to deal with community toxicity and spam.
However, a little wander around the web soon uncovers some really old forum systems still somehow creaking along.
Amazingly, most of these communities are still used daily, often with millions of posts in the archives.
It might be tempting to ask why keep upgrading and investing in new versions of the software?
After all, if the community is still running just fine and getting daily visitors, then it's ok to do nothing, right?
But there is a hidden cost in doing nothing.
Security
This is the main one for me. Old platforms often have several published security vulnerabilities. Often these vulnerabilities are exploited by scripts that are shared around hacker communities. This means exploiting a website running an old version of a forum system is as simple as running a script and pointing it at your site.
Older forums are also less sophisticated. They rely on unsafe hashing methods to store passwords and lack vital features like two-factor authentication.
Also, consider that the server environment has to be maintained with out of date PHP and MySQL versions. It's a recipe for disaster.
Could your community survive a major exploit where data is downloaded into the hands of a hacker?
The cost could be fatal to your community.
Declining engagement
Even the most ardent of fans on your community will eventually tire of struggling to access your site on mobile devices.
I think back to 2002 when we created the first version of our software. We only had to focus on how it looked on a computer, so naturally, that influenced the design of the forum.
It's not so simple now. More and more of us are using mobile phones to access the internet. A recent statistic showed that mobile internet access outstrips desktop use 2 to 1; and for some countries, mobile internet access is almost the only way people get online.
It's just a matter of time before new members stop registering and engagement tails off.
Competition
At the end of 2018, there were 1.8 billion websites (I Googled it). The competition for attention has never been as fierce.
Your community may be the go-to place for your niche, but what if another community popped up running the latest version of a platform with all the features your members have been desperately asking for?
It may not take long until there is a massive drain from your community.
I'm sure there's a dozen reasons to make sure you're always re-investing in your community by upgrading to a modern platform. This blog merely scratches the surface.
For those of you that do invest and upgrade? You reap the benefits daily by ensuring you are doing the very best for your community by keeping it secure and accessible for most.
If you are on an older platform, now is the time to put some serious thought into making the move to something better.
I put together a little downloadable guide that might help too.
What do you think? Let me know in the comments below.

The Internet is a fierce battleground for users, clicks, attention, and audience.  Competition surrounds your community from all angles and new threats constantly emerge.
The Internet has leveled the playing field for local businesses, solopreneurs, and small organizations which means more people than ever are competing for users.  Online communities are no different, and as companies realize the growing power of communities, you too may face more challenges. 
Online communities are growing faster than ever:
 IDC predicts worldwide online communities market to grow to $1.2 billion in 2019 According to research by Leader Networks,  twenty-three percent of marketers who have online communities indicate that the size of their communities doubled in the past year.   How is your community competing against your competitors?  Is your community growing or stagnating relative to your competitors?   
In this blog post, we identify core concepts of competitive strategy that stretch from traditional theory to unique methods of winning for communities.   
Theory of Competition
The broadly-accepted understanding of competition in the business world rests on the seminal work by Professor Michael Porter, when he mapped out the origins of competitive forces in his 1979 book “How Competitive Forces Shape Strategy.”  Fundamentally, all strategies for Porter distill into two basic options: Build on what you already do, or do something no one else can do.  
You can compete by doing what everyone else is doing but be more efficient, such as offering higher quality content, a better user experience, or having a lower price of member acquisition.  Or, you can expand the pie by forging a new position in the marketplace, such as staking out an untapped niche or developing a unique service.    
What’s your current competitive strategy: be better at what you’re already doing and your competitors, or to do something completely new?  
Emerging Theories
A new strategy on competition is emerging that is just as potent as Porter’s competitive forces. It’s especially relevant for online communities in the digital age: reacting opportunistically to emerging possibilities.  
Discovery-driven planning is the field’s most recent thinking.  It was introduced 20 years ago in works like Tim Luehrman’s “Strategy as a Portfolio of Real Options” that talked about flexibility as a strategy.  The idea was also introduced in the more recent “Stop Making Plans: Start Making Decisions” by Michael Mankins and Richard Steel, which argued for continuous strategic planning cycles.   
Online communities are impacted by – and can seize advantage of – fluctuating factors:
Technical advances and digital disruptions  Disruptions in your industry  The faster you react to market or technological change, the greater your advantage will become over time.  What disruption recently impacted your industry or niche?  How can you capitalize on the opportunity?  
Application to Online Communities
Online communities are at an especially powerful intersection of customers, superusers, industry experts, and brand representatives.  By assembling a broad mix of users, you gain a source of competitive knowledge and crowd wisdom unmatched by traditional businesses.  
Market intelligence – Harness the power of crowds by letting your members feed you real-time market intelligence on the industry, market trends, and competitors.   Use technology to your advantage – Become an expert on utilizing your Invision platform as a technological advantage, whether you’re increasing visitor registrations with Post Before Registering, adding in store filters in Commerce, or enabling the application manifest settings for faster access on smartphones. Collaborative ideation – Collaborate with users early in the design process to create services or products that are highly-differentiated. Co-Creation – Channel your user’s expertise, enthusiasm, and product knowledge into co-created content such as tutorials, support answers, industry news, contests, and more.  Brand Ambassadors – Turn your membership’s most passionate users into brand ambassadors to provide outreach and personalized connections.   Conclusion
Communities are challenged and tested every day by a multitude of competitors that compete for users. Competition is fierce, and as the web continues to proliferate and level the playing field, competition will only get stronger. 
It’s no longer enough to host a general discussion forum.  Successful communities envision a clear competitive strategy.  
Although competition is fierce, there are winners on the Internet who consistently gain market share. 
The winners are those who understand the fundamental drivers of competition: to create sustainable advantages over their competitors, to offer unique services and experiences, and to react opportunistically.  They also leverage all facets of their community for maximum value.      
Join me in 2019 in defining your competitive strategy and becoming a Community of Excellence. 
- Joel R
Joel R is a mystery wrapped inside an enigma. When he's not running his own successful community, he's peppering Invision Community's private Slack channel with his feedback, community management experience and increasingly outrageous demands (everything is true except the last part).

The Internet is a fierce battleground for users, clicks, attention, and audience.  Competition surrounds your community from all angles and new threats constantly emerge.
The Internet has leveled the playing field for local businesses, solopreneurs, and small organizations which means more people than ever are competing for users.  Online communities are no different, and as companies realize the growing power of communities, you too may face more challenges. 
Online communities are growing faster than ever:
 IDC predicts worldwide online communities market to grow to $1.2 billion in 2019 According to research by Leader Networks,  twenty-three percent of marketers who have online communities indicate that the size of their communities doubled in the past year.   How is your community competing against your competitors?  Is your community growing or stagnating relative to your competitors?   
In this blog post, we identify core concepts of competitive strategy that stretch from traditional theory to unique methods of winning for communities.   
Theory of Competition
The broadly-accepted understanding of competition in the business world rests on the seminal work by Professor Michael Porter, when he mapped out the origins of competitive forces in his 1979 book “How Competitive Forces Shape Strategy.”  Fundamentally, all strategies for Porter distill into two basic options: Build on what you already do, or do something no one else can do.  
You can compete by doing what everyone else is doing but be more efficient, such as offering higher quality content, a better user experience, or having a lower price of member acquisition.  Or, you can expand the pie by forging a new position in the marketplace, such as staking out an untapped niche or developing a unique service.    
What’s your current competitive strategy: be better at what you’re already doing and your competitors, or to do something completely new?  
Emerging Theories
A new strategy on competition is emerging that is just as potent as Porter’s competitive forces. It’s especially relevant for online communities in the digital age: reacting opportunistically to emerging possibilities.  
Discovery-driven planning is the field’s most recent thinking.  It was introduced 20 years ago in works like Tim Luehrman’s “Strategy as a Portfolio of Real Options” that talked about flexibility as a strategy.  The idea was also introduced in the more recent “Stop Making Plans: Start Making Decisions” by Michael Mankins and Richard Steel, which argued for continuous strategic planning cycles.   
Online communities are impacted by – and can seize advantage of – fluctuating factors:
Technical advances and digital disruptions  Disruptions in your industry  The faster you react to market or technological change, the greater your advantage will become over time.  What disruption recently impacted your industry or niche?  How can you capitalize on the opportunity?  
Application to Online Communities
Online communities are at an especially powerful intersection of customers, superusers, industry experts, and brand representatives.  By assembling a broad mix of users, you gain a source of competitive knowledge and crowd wisdom unmatched by traditional businesses.  
Market intelligence – Harness the power of crowds by letting your members feed you real-time market intelligence on the industry, market trends, and competitors.   Use technology to your advantage – Become an expert on utilizing your Invision platform as a technological advantage, whether you’re increasing visitor registrations with Post Before Registering, adding in store filters in Commerce, or enabling the application manifest settings for faster access on smartphones. Collaborative ideation – Collaborate with users early in the design process to create services or products that are highly-differentiated. Co-Creation – Channel your user’s expertise, enthusiasm, and product knowledge into co-created content such as tutorials, support answers, industry news, contests, and more.  Brand Ambassadors – Turn your membership’s most passionate users into brand ambassadors to provide outreach and personalized connections.   Conclusion
Communities are challenged and tested every day by a multitude of competitors that compete for users. Competition is fierce, and as the web continues to proliferate and level the playing field, competition will only get stronger. 
It’s no longer enough to host a general discussion forum.  Successful communities envision a clear competitive strategy.  
Although competition is fierce, there are winners on the Internet who consistently gain market share. 
The winners are those who understand the fundamental drivers of competition: to create sustainable advantages over their competitors, to offer unique services and experiences, and to react opportunistically.  They also leverage all facets of their community for maximum value.      
Join me in 2019 in defining your competitive strategy and becoming a Community of Excellence. 
- Joel R
Joel R is a mystery wrapped inside an enigma. When he's not running his own successful community, he's peppering Invision Community's private Slack channel with his feedback, community management experience and increasingly outrageous demands (everything is true except the last part).

The Internet is a fierce battleground for users, clicks, attention, and audience.  Competition surrounds your community from all angles and new threats constantly emerge.
The Internet has leveled the playing field for local businesses, solopreneurs, and small organizations which means more people than ever are competing for users.  Online communities are no different, and as companies realize the growing power of communities, you too may face more challenges. 
Online communities are growing faster than ever:
 IDC predicts worldwide online communities market to grow to $1.2 billion in 2019 According to research by Leader Networks,  twenty-three percent of marketers who have online communities indicate that the size of their communities doubled in the past year.   How is your community competing against your competitors?  Is your community growing or stagnating relative to your competitors?   
In this blog post, we identify core concepts of competitive strategy that stretch from traditional theory to unique methods of winning for communities.   
Theory of Competition
The broadly-accepted understanding of competition in the business world rests on the seminal work by Professor Michael Porter, when he mapped out the origins of competitive forces in his 1979 book “How Competitive Forces Shape Strategy.”  Fundamentally, all strategies for Porter distill into two basic options: Build on what you already do, or do something no one else can do.  
You can compete by doing what everyone else is doing but be more efficient, such as offering higher quality content, a better user experience, or having a lower price of member acquisition.  Or, you can expand the pie by forging a new position in the marketplace, such as staking out an untapped niche or developing a unique service.    
What’s your current competitive strategy: be better at what you’re already doing and your competitors, or to do something completely new?  
Emerging Theories
A new strategy on competition is emerging that is just as potent as Porter’s competitive forces. It’s especially relevant for online communities in the digital age: reacting opportunistically to emerging possibilities.  
Discovery-driven planning is the field’s most recent thinking.  It was introduced 20 years ago in works like Tim Luehrman’s “Strategy as a Portfolio of Real Options” that talked about flexibility as a strategy.  The idea was also introduced in the more recent “Stop Making Plans: Start Making Decisions” by Michael Mankins and Richard Steel, which argued for continuous strategic planning cycles.   
Online communities are impacted by – and can seize advantage of – fluctuating factors:
Technical advances and digital disruptions  Disruptions in your industry  The faster you react to market or technological change, the greater your advantage will become over time.  What disruption recently impacted your industry or niche?  How can you capitalize on the opportunity?  
Application to Online Communities
Online communities are at an especially powerful intersection of customers, superusers, industry experts, and brand representatives.  By assembling a broad mix of users, you gain a source of competitive knowledge and crowd wisdom unmatched by traditional businesses.  
Market intelligence – Harness the power of crowds by letting your members feed you real-time market intelligence on the industry, market trends, and competitors.   Use technology to your advantage – Become an expert on utilizing your Invision platform as a technological advantage, whether you’re increasing visitor registrations with Post Before Registering, adding in store filters in Commerce, or enabling the application manifest settings for faster access on smartphones. Collaborative ideation – Collaborate with users early in the design process to create services or products that are highly-differentiated. Co-Creation – Channel your user’s expertise, enthusiasm, and product knowledge into co-created content such as tutorials, support answers, industry news, contests, and more.  Brand Ambassadors – Turn your membership’s most passionate users into brand ambassadors to provide outreach and personalized connections.   Conclusion
Communities are challenged and tested every day by a multitude of competitors that compete for users. Competition is fierce, and as the web continues to proliferate and level the playing field, competition will only get stronger. 
It’s no longer enough to host a general discussion forum.  Successful communities envision a clear competitive strategy.  
Although competition is fierce, there are winners on the Internet who consistently gain market share. 
The winners are those who understand the fundamental drivers of competition: to create sustainable advantages over their competitors, to offer unique services and experiences, and to react opportunistically.  They also leverage all facets of their community for maximum value.      
Join me in 2019 in defining your competitive strategy and becoming a Community of Excellence. 
- Joel R
Joel R is a mystery wrapped inside an enigma. When he's not running his own successful community, he's peppering Invision Community's private Slack channel with his feedback, community management experience and increasingly outrageous demands (everything is true except the last part).

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

One of the first things I do when visiting a site that I know has a community is to try and find it.
More often than not, it's hidden away in the footer links or buried in several sub-menus and labelled something relatively obscure like "Fans" or "Support".
This is a massive lost opportunity!
We all know that social proof is incredibly important when making a purchasing decision.
When I buy something on Amazon or book a holiday, the first thing I do is scour the reviews. Are the reviews mostly positive? What did other people think about the product after receiving it?
I might see two almost identical products and the reviews, not the price that'll always sway me.
It's that urge to herd to keep safe at play.
So why bury all that out of the way?
Your community should be full of fantastic social proof — hundreds of customers using your product and creating a buzz.
Is it a fear of criticism? We all have had bad experiences with clients who are less than rational with feedback, but that's OK.
The Harry Potter series of books are beloved by millions, made J.K Rowling a fortune, made a celebrated movie series and opened up several themed attractions which are always busy.
Yet, there are a significant number of 1-star reviews on Amazon.

Not everyone will get you or your business.
You always have the opportunity to reply and explain your side, and you are always in control with moderation tools.
Let's face it; if you are to handle negative feedback, it's better to manage it on your community than see it all over social media, Google reviews and review sites like TripAdvisor.
Maybe you're a little embarrassed because the community platform is old and doesn't match your branding.
If that's the case, then come and talk to us! We specialise in migrating communities from legacy platforms with poor mobile support. We offer brand matching services too.
Maybe it's just that you're unsure of what to do with your community.
I get that too. It can be hard to know how it fits in with your brand. I'm happy to help there also. Feel free to drop a comment below.
Our product has several ways to pull content from the community and feature it on your site.
We've helped big brands like LEGO®, Sega, Warner Bros. and more nurture a prosperous community that enhances their business.
The bottom line is that a well manage community should be central to your brand and website.
Hiding it among the "Privacy Policy" links is a huge missed opportunity.
- Matt

One of the first things I do when visiting a site that I know has a community is to try and find it.
More often than not, it's hidden away in the footer links or buried in several sub-menus and labelled something relatively obscure like "Fans" or "Support".
This is a massive lost opportunity!
We all know that social proof is incredibly important when making a purchasing decision.
When I buy something on Amazon or book a holiday, the first thing I do is scour the reviews. Are the reviews mostly positive? What did other people think about the product after receiving it?
I might see two almost identical products and the reviews, not the price that'll always sway me.
It's that urge to herd to keep safe at play.
So why bury all that out of the way?
Your community should be full of fantastic social proof — hundreds of customers using your product and creating a buzz.
Is it a fear of criticism? We all have had bad experiences with clients who are less than rational with feedback, but that's OK.
The Harry Potter series of books are beloved by millions, made J.K Rowling a fortune, made a celebrated movie series and opened up several themed attractions which are always busy.
Yet, there are a significant number of 1-star reviews on Amazon.

Not everyone will get you or your business.
You always have the opportunity to reply and explain your side, and you are always in control with moderation tools.
Let's face it; if you are to handle negative feedback, it's better to manage it on your community than see it all over social media, Google reviews and review sites like TripAdvisor.
Maybe you're a little embarrassed because the community platform is old and doesn't match your branding.
If that's the case, then come and talk to us! We specialise in migrating communities from legacy platforms with poor mobile support. We offer brand matching services too.
Maybe it's just that you're unsure of what to do with your community.
I get that too. It can be hard to know how it fits in with your brand. I'm happy to help there also. Feel free to drop a comment below.
Our product has several ways to pull content from the community and feature it on your site.
We've helped big brands like LEGO®, Sega, Warner Bros. and more nurture a prosperous community that enhances their business.
The bottom line is that a well manage community should be central to your brand and website.
Hiding it among the "Privacy Policy" links is a huge missed opportunity.
- Matt

One of the first things I do when visiting a site that I know has a community is to try and find it.
More often than not, it's hidden away in the footer links or buried in several sub-menus and labelled something relatively obscure like "Fans" or "Support".
This is a massive lost opportunity!
We all know that social proof is incredibly important when making a purchasing decision.
When I buy something on Amazon or book a holiday, the first thing I do is scour the reviews. Are the reviews mostly positive? What did other people think about the product after receiving it?
I might see two almost identical products and the reviews, not the price that'll always sway me.
It's that urge to herd to keep safe at play.
So why bury all that out of the way?
Your community should be full of fantastic social proof — hundreds of customers using your product and creating a buzz.
Is it a fear of criticism? We all have had bad experiences with clients who are less than rational with feedback, but that's OK.
The Harry Potter series of books are beloved by millions, made J.K Rowling a fortune, made a celebrated movie series and opened up several themed attractions which are always busy.
Yet, there are a significant number of 1-star reviews on Amazon.

Not everyone will get you or your business.
You always have the opportunity to reply and explain your side, and you are always in control with moderation tools.
Let's face it; if you are to handle negative feedback, it's better to manage it on your community than see it all over social media, Google reviews and review sites like TripAdvisor.
Maybe you're a little embarrassed because the community platform is old and doesn't match your branding.
If that's the case, then come and talk to us! We specialise in migrating communities from legacy platforms with poor mobile support. We offer brand matching services too.
Maybe it's just that you're unsure of what to do with your community.
I get that too. It can be hard to know how it fits in with your brand. I'm happy to help there also. Feel free to drop a comment below.
Our product has several ways to pull content from the community and feature it on your site.
We've helped big brands like LEGO®, Sega, Warner Bros. and more nurture a prosperous community that enhances their business.
The bottom line is that a well manage community should be central to your brand and website.
Hiding it among the "Privacy Policy" links is a huge missed opportunity.
- Matt

One of the first things I do when visiting a site that I know has a community is to try and find it.
More often than not, it's hidden away in the footer links or buried in several sub-menus and labelled something relatively obscure like "Fans" or "Support".
This is a massive lost opportunity!
We all know that social proof is incredibly important when making a purchasing decision.
When I buy something on Amazon or book a holiday, the first thing I do is scour the reviews. Are the reviews mostly positive? What did other people think about the product after receiving it?
I might see two almost identical products and the reviews, not the price that'll always sway me.
It's that urge to herd to keep safe at play.
So why bury all that out of the way?
Your community should be full of fantastic social proof — hundreds of customers using your product and creating a buzz.
Is it a fear of criticism? We all have had bad experiences with clients who are less than rational with feedback, but that's OK.
The Harry Potter series of books are beloved by millions, made J.K Rowling a fortune, made a celebrated movie series and opened up several themed attractions which are always busy.
Yet, there are a significant number of 1-star reviews on Amazon.

Not everyone will get you or your business.
You always have the opportunity to reply and explain your side, and you are always in control with moderation tools.
Let's face it; if you are to handle negative feedback, it's better to manage it on your community than see it all over social media, Google reviews and review sites like TripAdvisor.
Maybe you're a little embarrassed because the community platform is old and doesn't match your branding.
If that's the case, then come and talk to us! We specialise in migrating communities from legacy platforms with poor mobile support. We offer brand matching services too.
Maybe it's just that you're unsure of what to do with your community.
I get that too. It can be hard to know how it fits in with your brand. I'm happy to help there also. Feel free to drop a comment below.
Our product has several ways to pull content from the community and feature it on your site.
We've helped big brands like LEGO®, Sega, Warner Bros. and more nurture a prosperous community that enhances their business.
The bottom line is that a well manage community should be central to your brand and website.
Hiding it among the "Privacy Policy" links is a huge missed opportunity.
- Matt

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

Release parties at Invision Community are a fairly tame affair. You'd think after months of planning, coding and testing we'd want to cut loose and dance the night away.
The reality is we send each other a few amusing GIFs in Slack and then wait for support tickets to start appearing while our developers crack their knuckles and prepare for bug reports to be filed.

It's a nightmare trying to get a photo of our team, so here's a stock image. Just pretend it's us. That's me looking at a report of how much code Mark Wade has refused during reviews
I did manage to find five minutes to ask the team what their favourite feature of 4.4 was.

Here's what they said.
Marc S
Support, Guides and Keen Cyclist @Marc Stridgen
I'm going to go with 'Post before registering', because it allows for more effective onboarding of new members on your site. People are much more likely to register after just having written a topic, then they are if they have to register before getting started. It also gives you the opportunity to see how many people are not actually registering, and maybe address that on the site.

Ryan
Developer, T3 support and reluctant AWS wrangler @Ryan Ashbrook
My favorite 4.4 feature is the progressive web app settings. I now have our site pinned to my phones home screen for quick access, and use our site on mobile even more now that I can just hit the icon to pull up our site.

Mark H
Support, Beta Tester and remembers this when it was fields @Mark H
While this isn’t “a” favorite feature, I most like the steady small improvements to Gallery in the 4.x series. Photography-centric sites should especially like the additions to extended EXIF data in 4.4 so that authors can provide the most detail about their submitted photos…. where it was taken, what camera, which lens, shutter speed and aperture, etc.

Daniel
Developer, T2 support and airport security fan @Daniel F
As IPS4 consumer, I'm going to say that Lazy Loading and mobile create menu are my favorite enhancement.
As community owner, I'm most excited about post before register and email advertisements.. That's going to bring the $$$

Brandon
Developer, Enterprise Support and proud of his thorough code reviews @bfarber
My favorite change in 4.4 (besides the overall performance improvements, as I'm a geek for that sort of thing) is the overhauled Conversion experience (which we haven't even blogged about). We took converters and flipped them on their head for 4.4, so you now choose what software you want to convert from, what applications from that software you want to convert, fill in any required details, and the conversion process just launches and runs from beginning to end right then and there. You no longer need to convert each application and each type of data within each application individually, making for an easier and overall smoother experience.

Stuart
Developer, Conversion Specialist and PC enthusiast @Stuart Silvester
This is actually hard to answer than it seems, there are so many great changes and features in 4.4. The combined performance improvements including HTTP/2 Push, More aggressive caching, SVG letter photos, lazy loading are definitely some of my favourites. After all, time is money. (A smaller favourite is the browser notification prompt change, especially with visiting as many customer sites as I do in Tier 2).

Jim
Support, Beta Tester and suspiciously quiet in staff chat @Jim M
The communities I run are about cars and very heavily image based. Whether it's "I have an issue" or simple sharing of car builds, topics get image heavy very quickly and doing anything to improve moving throughout that topic more quickly is going to go far. I feel a lot of communities can relate and why lazy load of images is my favorite 4.4 feature.

Jennifer
Designer, Enterprise Theme Specialist, owner of several super powers @Jennifer M
There are so many changes with 4.4 it's actually really hard to choose just one change that is my absolutely favorite. I would probably say a lot of the more micro features are my favorites. Colored usernames everywhere, lazy load for images, improved notifications experience, text or URLs for announcements, reordering of club tabs, ability to hide widgets/blocks from mobile etc. They are all quality of life improvements that I love and appreciate on so many levels.

We're Steve Ballmer levels of excited about 4.4.

It looks like Rikki's lazy loading is a clear winner. I'm not surprised, it's a real boost for page speed and reduces hosting costs. Personally I'm a fan of the progressive web app settings which, like Ryan, enables me to have our community on my phone's home page.

Let us know what your favourites are below! 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

We're thrilled to announce that Invision Community 4.4 is available to download now.
After months of development, over 1650 separate code commits and quite a few mugs of questionable coffee you can now get your hands on the beta release from the client centre.

Not our office
Invision Community 4.4 brings numerous new features, over 450 bug fixes and a lot of refinement.
We've been talking about the highlights since September on our blog.
Here's a recap of all that we've added.
We'd love to know which is your favourite feature so far!

Drop a line below and let us know!
 

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

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.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

It's been said that the best place to hide a dead body is on page 2 of Google.
While we can't promise to get you to page 1 for a generic search term, we have taken some time for Invision Community 4.4 to do an SEO sweep.
Moz.com defines SEO as "a marketing discipline focused on growing visibility in organic (non-paid) search engine results. SEO encompasses both the technical and creative elements required to improve rankings, drive traffic, and increase awareness in search engines."
We have the technical skills and were fortunate enough to have Jono Alderson of Yoast lend his time, knowledge and vast experience to improve our SEO.
This blog article gets a little technical. It's completely fine to leave at this point with the comfort of knowing that Google will be a little happier on your site with Invision Community 4.4.
The majority of the changes are designed to send stronger signals to Google and friends over which content to slurp and which to look at a bit later.
Still here? Good. Let us roll up our sleeves and open the hood.

 
Pagination
The most visible change is that we've taken pagination out of query strings and placed it in the path.
For example, the current pagination system looks a little like:
yoursite.com/community/forums/123-forum/?page=3
Which is fine but it gets a little confusing when you add in a bunch of sort filters like so:
yoursite.com/community/forums/123-forum/?sort=asc&field=topic&page=3
A better approach would be to make a clear signal to both Google and humans that pagination is a separate thing.
Invision Community 4.4 does this:
yoursite.com/community/forums/123-forum/page/3/?sort=asc&field=topic
Not only is this good for search engines, but it's also good for the humans too as it is more readable and no longer confused with filter parameters.

Of course, we ensure that the old style pagination is redirected (via a 301 header) to the new pagination URL automatically so nothing breaks.
Canonical Tags
These tags are a way of telling search engines that a specific URL is the 'master copy' of a page. This helps prevent duplicate content from being indexed.
Without it, you are leaving it up to the search engine to choose which is the master copy of the page.
For example:
yoursite.com/community/forums/123-forum/ and yoursite.com/community/forums/123-forum/?sort=desc&field=time may show the same content but have different URLs.
By setting the canonical tag to point to yoursite.com/community/forums/123-forum/ regardless of filters sends a strong signal to the search engines that this is the page you want to be spidered.
Invision Community sets these tags in many places, but we audited these in 4.4 and found a few areas where they were missing.
For example, viewing a member's profile doesn't always set a canonical tag which may confuse search engines when you click on "View Activity" and get a list of content items.
Soft 404s
When an application or website wants to tell the visitor that the page they are looking for doesn't exist, it sends a 404 header code along with a page that says something "We could not find that item" or "No rows available".
If a search engine spiders a page that looks like a 404 page, but it doesn't have the 404 header code, it logs it as a "soft 404".
Given the short amount of time Google has on your site to discover new content, you don't want it to hit many soft 404s.
Invision Community 4.4 omits containers (such as forums, blogs, etc.) that have no content (such as a new forum without any topics yet) from the sitemap, and also adds a 'noindex, follow' meta tag into the HTML source.
Google will periodically check to see if the status of the page has changed and happily slurp away when content has been added.
Other changes
Although the changes listed here don't deserve their own section in this article, they are no less important.
We have audited the new JSON-LD markup added to Invision Community 4.3 to help search engines better understand the relationship between pages.
The "truncate" method that is used to display a snippet of text in areas such as the activity stream now only sends the first 500 characters to the javascript method to reduce page loads and page 'noise'.
The profile view in Invision Community contains a mix of information pertinent to the member and content they've authored.
We've ensured that the content areas are using a specific URL, with appropriate canonical tags. This will help reduce confusion for search engines.
If you made it this far, then well done. It's time to slam the hood closed and mop our collective brows.
These changes will certainly help Google and friends spider your site a little more efficiently and have a clearer idea about what pages and data you want to be indexed which can only improve your ranking.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.

Communication has come a long way since those very early humans grunted at each other to determine if they wanted more mammoth for lunch.
The course of human history has seen cave paintings, hieroglyphics, the written word, emoji and now GIFs.
GIFs have been around since the dawn of the internet. Many websites proudly displayed a 'man at work' animated GIF when they were under construction.
Now, GIFs are now mostly used to express complex thoughts and emotions by showing a short animation.

Mind Blown
 
Invision Community has allowed GIPHY to be used as an embed for a while now, but we craved something much more straightforward.
Behold, the GIF button!
Now your members can reply with the majesty of animation.
Of course, GIFs won't replace real and meaningful conversation, but they are a fun way to express yourself quickly and encourage more engagement.
The GIPHY functionality is enabled via the 'Community Enhancements' page in the Admin CP.

GIPHY is enabled from the enhancements page
All you need to do is grab a key from GIPHY, and you're all set!

Configuration
You'll notice a "MPAA style rating" option.
This allows you to select a maximum rating for the GIFs as some will have adult themes and language that may not be suitable for your community.
For example, you can choose "G" for general audiences, "PG" or "PG-13" to limit what is shown.

Yes!
Drop your favourite GIF below to show us how you feel about this new feature.
This is a blog about our upcoming Invision Community 4.4 release, due later this year.