Tailwind can potentially load tens of thousands of different items in your dashboard. To do this, it requires a lot from your browser. Unfortunately, if there is too much content trying to be loaded, it could slow down or crash the browser. If this happens, there may be one or more areas needing adjustment. Here are some common reasons for this problem and ways to improve them.

If there is a very high number of scheduled pins, typically in the thousands, there might be some slow downs. This is because the browser is working very hard to try to load thousands of timeslots/images at once. Additionally, if there are scheduled pins far out into the future, years even, then this too might cause issues, as all time slots between now and the last-scheduled pin are being loaded. 

To address this, you might consider a few options: waiting until the scheduled pins get published, adding the pins that are scheduled far into the future back to the Drafts page, or deleting some pins. Fortunately, even if the dashboard has problems loading, your pins will still be published! 

One way you can help improve this is by adjusting the number of Pins shown in the schedule at any given time. Head over to the Advanced Settings tab in the dashboard and you can limit the number of Pins shown. Generally, the less the better!

Note: If you make any changes to the grid like shuffling or filling in time slots, only those being displayed will be affected.

Another potential reason why the dashboard could be having issues is if there are a very high number of Draft pins, usually in the thousands. Similar to having too many scheduled pins, it might be worth considering either scheduling or removing some. 

If there are hundreds of time slots per day, this could cause the dashboard to load slowly due to the number of calculations running in the background to generate the schedule. Navigating over to the Your Schedule page, you can see how many time slots there are. If there are hundreds or thousands of timeslots listed per day, reducing this number could speed things up a bit.

Interval pins can also cause issues. For example, if we set one interval pin going to several boards that took a few months to complete, it could break the dashboard, as all the time slots in-between each board pinning will be loaded. 

This is a much less common situation, but it's essentially the same as a post being scheduled too far in the future. Having a draft with a custom time set far into the past will add additional time slots that the dashboard needs to load and can cause a dashboard timeout.

Generally, SmartLoop loads at least 6 weeks into the future. Heading over to the Your Schedule page, if you count how many SmartLoop timeslots are listed for the week and then multiply by 6, the dashboard may have issues loading if the result is above ~15,000. 

Additionally, if there are several thousand Active SmartLoop Posts, this might also cause problems for the browser. There are several variables at play, but generally, reaching above ~10,000 Active SmartLoop Posts might result in errors when trying to load the SmartLoop page. If this is happening, just write into us and we'd be happy to help get you rolling again!

SmartLoop posts are calculated by pins x boards. So there could be 100 pins going to 10 boards, or 1,000 pins going to 1 board. With either combination, these will still be counted as 1,000 Active SmartLoop Posts.

One of the simplest ways to reduce the number of SmartLoop posts is to make sure that the same pin isn't in multiple loops. You might also consider removing boards from pins, removing pins from loops, or deleting loops entirely. 

To keep SmartLoop posts in a healthy range, we always like to advise using SmartLoop Best Practices. By ensuring that only pins that get the most engagement are looping, it can help by not only boosting the reach of those pins, but also by keeping SmartLoop posts from slowing things down too much. 

Failed pins usually happen when pins are scheduled to a board that either no longer exists or that you have left. This makes failed pins appear in the failed pin section of the Scheduled Pins page.

Failed pins seem to cause more slowdown on the dashboard than other pins, and they're generally an easy first thing to delete in order clear up some memory on the browser. 

Tailwind is designed to run on desktop and laptop computers in the Chrome, Firefox, and Safari browsers. Tailwindapp.com may function partially on mobile devices, but not all functions may be available. Older or lower spec computers such as Chromebooks may have difficulty running the Tailwind dashboard quickly.

Finally, the issue could be a combination of two or more of the above causes.

If you're still noticing issues, just write into us and we'd be happy to get you back up and running again!