Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Google Chrome

This site may earn commission on affiliate links.
I have NoScript blocking Twitter and Facebook (among other things I don't care for) and therefore don't even see the links. I temporarily allowed scripts from all domains and was shocked by the difference.

If you're using Firefox, don't want to muck with your hosts file or a local caching DNS server, and don't care about Twitter et al, you can grab NoScript and just blacklist twitter.com.

Thank you! I just got the extension "NotScripts" for Google Chrome and black listed platform.twitter.com and things load about 10 or 15 times faster! I can also view more than 4 or 5 tabs now... I just had 10 open no problem! :biggrin:

Edit: This does screw up Twitter, but I practically never use Twitter anyway.
 
Last edited:
I'm going to give NotScripts a try as well.

I have to admit, there are couple of bugs (and they're on my plate): http://crbug.com/16581 and http://crbug.com/74721 that make things worse when something slow like the Twitter or Facebook buttons hold things up.

I even got mad enough that I wrote a Chrome extension to scrape the 'new post in thread' links and open them carefully one at a time to minimize the stalls. Should just get better with Twitter blocked. I didn't want to block everything, since I know the ads support the site.
 
We put the Tweet-this and Facebook links in over a year ago as a convenience to share an article.

Both pull data directly from their respective systems, Facebook was so dreadful that it was pulled really quickly!

All the tweet buttons take about 700mS for me on a typical page (here in NJ) - looking at the waterfall chart on Safari. That's quite a reasonable chunk of the overall time. Plus, the resource http://platform.twitter.com/widgets/images/t.gif is used to form the tweet payload and so isn't cached.

Looking at the analytics that we've gathered, people do use the tweet buttons (we're grateful for that) but there is more traffic from the 'Auto-tweet' out of the @TeslaMotorsClub account and RT's of that than personal tweeting of a post. I'm happy to drop the per-post tweet control. I'll get to that this week.

Recently, Google have been including some VERY poor performing tracking pixels but I get the sense that they've been removed or repaired. That might explain recent performance issues.

By all means use blocking tools - enough people don't to allow us to get general site analytics.

Use ad. blockers if you wish but the funds do go into a small pot that we'll hopefully be able to use to carry out some bigger site updates this year. Right now, the infrastructure software/hardware/network is covered by me - I'll pass a hat round if it ever becomes an issue :)
 
I have to admit, there are couple of bugs (and they're on my plate): http://crbug.com/16581 and http://crbug.com/74721 that make things worse when something slow like the Twitter or Facebook buttons hold things up.

I'm wondering if it's a simultaneous locking for access to the cache type problem. I see a lot of "Waiting for cache" messages, which is odd on a high end Macbook with SSD disks. But I can imaging that having 10+ pages from this site all hitting the cache loading the same small "tweet" icons over and over might cause some contention, and if one is holding the lock at the wrong point (like while waiting for something else to load) it could explain the unresponsiveness until everything is loaded problem.
 
Maybe twitter feed is just slower in general for some of us.
Even when I visit them directly, I sometimes have performance issues, like this I just saw today:
twitslow.jpg
 
No. While the Honeycomb browser is still WebKit based, the outer parts of it are something else. I'm not directly involved with Chrome on Android, but do work with some of that team.

Could you pass on that the twitter site itself runs like a dog on there please? It is unusably slow and unresponsive. It is the only website I visit that does this - no idea why.

Running 3.1 on a 32GB Galaxy Tab 10.1