Twitter has announced the launch of a feature called embedded Tweets. This gives bloggers the chance to paste a short piece of flat-HTML into a post and BOOM – you have a clickable tweet right there on your site. It’s going to make life a lot easier.
So, smart idea, right?
Well, maybe not!
Google announced last month that sites that load slowly will be penalised with a lower search ranking. Twitter is known for poor reliability (fail whales) and slow load times. See where I’m going here? So, by pasting code on your site which is having to wait for twitter to get moving, you may be slowing your overall load speed and thus, get penalised by Google.
Whilst it’s a pain in the ass to manually do a screen-grab of a tweet and then upload it to a post, at least there’s nothing in that process to slow your load time down; especially if you compress the image and are hosted on a nice, quick server. It will be interesting to see what the feedback is once people have been using the new embeded tweet feature for a while.
Thoughts?
Good point Jim – many folks probably don’t realize embedding directly from the Twitter site could potentially slow the load time for your website… thanks for sharing :)
Yeah, looking at the performance of Twitter, especially right now, it could slow your site down to a crawl, (IF) the same servers at Twitter need to be accessed to display the embedded stuff.
Let’s see!
Very good to know as a casual blogger! While my content is mostly shared with friends and Twitter followers I find it interesting technologically!
Indeed. It’s going to be interesting to see if it really does make much of a difference, Lonnie.
I don’t see the point of this function. Seeing Twitter only allows the most recent tweets to be accessed, odds are it’s going to return a “tweet not found” message once the tweet is more than a few days old.
Best way is to copy the tweet, then paste, AND take a screen grab. Yes, it’s a bit more trouble, but nobody can say you changed the tweet. And providing you’re not one of the people who can’t resize a picture, the post will load much faster, making you more Google-accessible.
Hey Sheila, thanks for the feedback.
I think the old tweets will still be linked to.
I also thin people will use the feature, as it’s a pain in the butt to have to clip, compress and then upload every tweet – this is so much easier.
For me, the main issue is going to be the speed of the server where these tweets are stored and how that “may” impact the speed / performance of the sites that use it.
I’m gonna use it here soon and will report back!
Will Twitter's new embedded tweets make your site rank lower in Google search? http://j.mp/a8lHMF http://bit.ly/bgTeMb
Will Twitter's new embedded tweets lower your Google search rank? – http://b2l.me/sq3hc (via @TheTechNewsBlog)
RT @Twitter_Tips: Will Twitter's new embedded tweets make your site rank lower in Google search? http://j.mp/a8lHMF
RT @Twitter_Tips: Will Twitter's new embedded tweets make your site rank lower in Google search? http://j.mp/a8lHMF
RT @Twitter_Tips: Will Twitter's new embedded tweets make your site rank lower in Google search? http://j.mp/a8lHMF
RT @Twitter_Tips Will Twitter's new embedded tweets make your site rank lower in Google search? http://j.mp/a8lHMF
Verlieren Sie durch Twitter's #Blackbird #Pie Positionen im Google Ranking? http://j.mp/a8lHMF
Will Twitter's new embedded tweets lower your Google search rank? | The Tech News Blog http://bit.ly/aPNjGL
Will Twitter's new embedded tweets lower your Google search rank? http://is.gd/bUqm9
From what I’ve seen, the Tweet itself is preloaded into the site, so, it doesn’t have to look up the tweet everytime someone looks at your blog. I could be wrong about this….
RT @Twitter_Tips: Will Twitter's new embedded tweets make your site rank lower in Google search? http://j.mp/a8lHMF ouch?
RT @Twitter_Tips: Will Twitter's new embedded tweets make your site rank lower in Google search? http://j.mp/a8lHMF ouch?
All depens of the server where tweets are being stored. So this may vary on speed and the types of websites that will make use of it
From a web development point of view, there is no need to wait for a page to load (and thus keep Google happy) before displaying other information.
You may have heard of AJAX technology; this is more often used to grab information from a server when you do something, without re-display the whole page (remember how web pages used to refresh the whole page!). But it can also be used to process information synchronously thereby eliminating potential performance hot spots.
This is not a basic cut and paste operation, though, you would need to have some web development expertise or, at least, not be afraid to try….