Why We Shouldn’t Embed Twitter
Here are my concerns about embedding Twitter:
- Because we embed Twitter into our homepage, we carry an extra load, which slows down our homepage performance.
- Twitter design doesn’t blend well with our design. We don’t have any control of how it looks. The typefaces and colors are different. Twitter’s blue doesn’t go with our brand colors. Although we both use sans serif typefaces, our sans has a friendly, humanist quality to it. Twitter’s sans is geometric and corporate.
- Privacy worries me the most. By embedding Twitter on our site, we give Twitter permission to track our users.
Here’s Twitter’s policy on privacy:
When you view Twitter content such as embedded Tweets, buttons, or timelines integrated into other websites using Twitter for Websites, Twitter may receive information, including the web page you visited, your IP address, browser type, operating system, and cookie information.
Instead of embedding Twitter, why don’t we do it like the podcasts? We list all of the Twitter accounts, including the centers so they can also get exposure on our homepage. Here’s the implementation.