[XiTCLUB]

ok let me try..

[XiTCLUB]

ok i hav checked. its working on 4.0.7

[final kaoss]

Yes, the code that they supply to you, it goes before the </body> tag on any cms/forum including the vbulletin/invision/phpbb/smf/mybb/xenforo/wordpress/joomla/phpnuke/blogger etc

[Brandon Sheley]

I had this on my forum for a long time but removed it because it was just one more script running to slow the site down.

[final kaoss]

the tynt.com script shouldn't add that much, though it would be nice if they gave us the scripts used to do this so we can host it locally.

Actually, here's something you should read.

One of the concerns we have heard from publishers is that adding JavaScript slows page load times. It’s understandable that publishers want their users to have a positive experience, and so avoiding slow loading pages makes sense.

Google has stated that page speed will be a factor in their new ranking algorithm this year. And this has caused some publishers to take an even closer look at page load times.

So we wanted to address these questions and help publishers understand the impact of Tynt’s JavaScript on page speed and SEO.

“I’ve seen the load testing, no issues on our end. And we installed the [Tynt] code on Seventeen.com, one of our most heavily trafficked sites, specifically to gauge the performance impact, and there was none.”

- Dan Roberts, Senior SEO Strategist & Analyst, Hearst Digital Media

Relevance Still Trumps Page Weight When it Comes to Page Rank.

First off, what has Google said about page speed and web search ranking? Here are the highlights from the very little that’s been said:

* Page speed is considered a factor because Google wants to emphasize a positive user experience on the Internet. It has nothing to do with the time it takes Google to index sites (crawl) or respond to front-end search queries (when you search Google).
* Page speed is one of 200 factors and doesn’t carry as much weight as the relevance of a page. Page Speed is a “small factor”. Relevance still trumps Page Weight.
* Google advocates speeding up websites by recommending various tools. But they are not advocating the removal of useful JavaScripts.
* Google is, after all, the company behind some of the most popular JavaScript with their AdSense and Analytics scripts. Clearly they’re not advocating that you remove those scripts).

Matt Cutts of Google:


Read more: Tynt » Tynt, Page Speed, & SEO http://www.tynt.com/tynt-page-speed-seo/#ixzz19cxOlCI8

Youtube video with matt cutts http://www.youtube.com/watch?v=UbaU-p2UnkA

“While site speed is a new signal, it doesn’t carry as much weight as the relevance of a page. Currently, fewer than 1% of search queries are affected by the site speed signal in our implementation and the signal for site speed only applies for visitors searching in English on Google.com at this point. We launched this change a few weeks back after rigorous testing. If you haven’t seen much change to your site rankings, then this site speed change possibly did not impact your site.”

- Matt Cutts & Amit Singhal, Google on 9 April 2010

Given the tone and tenor of these statements, it’s clear that this is not an effort to persuade fast sites to obsess about indistinguishable milliseconds, but rather a campaign to deter sluggish sites.
Tynt Boosts In-Bound Links, SEO’s Best Friend

Tynt Insight inserts a backlink into the clipboard when users copy content off your website – thereby boosting your site’s SEO. That’s because when readers paste your content on blogs and other websites in the public view of search engines, these links are indexed. It is widely acknowledged that the accumulation of in-bound links plays a huge part in search engine rankings. Many publishers that use Tynt are accumulating thousands of strong fixed links per month.
So, given the questionable effect of page load on SEO, is it worth foregoing JavaScript and all of the high-quality inbound links Tynt facilitates?

It is not. And Google agrees. They advocate deferring of JavaScript and that’s exactly what we’ve always advised publishers do.
Built for Speed: Tynt is Fast & Efficient

Tynt has long advocated that our script be loaded at the end of the body section, so that we will not be responsible for delays in loading the page. There are two ways that delays could enter into the process:

A) The time it takes to load the JavaScript from the CDN (Tynt’s script loads in 60 milliseconds, on average), or

B) by some activity that the JavaScript undertakes once loaded, such as sending messages back over the web to a server.

As part of the improvements we are releasing this month our script is smaller to download and faster to execute (addressing point A above). We have also signed contracts and begun moving to Akamai, the world’s leading CDN, to deliver our files as fast as possible.

We have also improved our scripts ability to detect user actions sooner. For example, it is not uncommon to load advertisements after the main content, and some of them can take a long time to load. Previously, if the user performed a copy action before everything on the page had finished loading, we would not catch it because our script was still not loaded. We have made changes such that if they choose to load our script ahead of some of the slow loading components (such as other java scripts and ads), we can detect those user actions but will defer sending that information until after the page completes loading, thereby addressing point B above.

We’re confident in saying that we are very fast, careful not to impact page display or user activity, and generally represent only a tiny percent of total page load time.
Conclusion

It is wise for site owners to always be cognizant of the impact that any third party JavaScript will have upon their site from both a search engine ranking and a user experience perspective. Well designed JavaScript that delivers real business benefit is still worth deploying as the net benefit to the site is significant.


Read more: Tynt » Tynt, Page Speed, & SEO http://www.tynt.com/tynt-page-speed-seo/#ixzz19cxvs6As

[Alfa1]

Tynt has two js files, which often load in 300ms each. That's 0.6 seconds load time to each page. Tynt must be busy these days. Such page load time is not acceptable. Even though its a great service, such page load is more trouble than what its worth.