11–20 of 54 posts
Is there a good reason Facebook's JavaScript file for websites is 400K? Is it unoptimised? Is this just what happens in large companies? Does it do more than you'd think? I would have thought they'd have an incentive to make it fast and lean so people could comment and like faster.
I just use open graph tags on websites, which are more useful, lightweight and makes the link presentable and customisable when shared around Facebook. There's no downside to open graph tags. Website 'Like' buttons on the other hand, are useless, tacky, cheap and chunky. Nobody cares how many likes your webpage has. The number means nothing because your website might be one month old with '2k likes', or two years old…
I don't like them either but you'd be crazy by not integrating it on a website that you're trying to funnel organic, social traffic to.
I just use open graph tags on websites, which are more useful, lightweight and makes the link presentable and customisable when shared around Facebook. There's no downside to open graph tags. Website 'Like' buttons on the other hand, are useless, tacky, cheap and chunky. Nobody cares how many likes your webpage has. The number means nothing because your website might be one month old with '2k likes', or two years old…
Google have said Facebook likes aren't treated as a ranking signal but your page showing up on newsfeeds will bring in more likes and more backlinks.
> Makes zero difference to any visitor what that number is. It's not any measure of performance or anything.
You don't think a large number of likes makes a page look more newsworthy than a page with zero likes?
That title is misleading, the article clearly says "The SDK code is so big that it represents about 16% of the total size of all Javascript on the average web page." which is clearly not 16% the total site.
I just use open graph tags on websites, which are more useful, lightweight and makes the link presentable and customisable when shared around Facebook. There's no downside to open graph tags. Website 'Like' buttons on the other hand, are useless, tacky, cheap and chunky. Nobody cares how many likes your webpage has. The number means nothing because your website might be one month old with '2k likes', or two years old…
> Website 'Like' buttons on the other hand, are useless, tacky, cheap and chunky. Nobody cares how many likes your webpage has. Google have said Facebook likes aren't treated as a ranking signal but your page showing up on newsfeeds will bring in more likes and more backlinks. > Makes zero difference to any visitor what that number is. It's not any measure of performance or anything. You don't think a large number of…
I just use open graph tags on websites, which are more useful, lightweight and makes the link presentable and customisable when shared around Facebook. There's no downside to open graph tags. Website 'Like' buttons on the other hand, are useless, tacky, cheap and chunky. Nobody cares how many likes your webpage has. The number means nothing because your website might be one month old with '2k likes', or two years old…
The overall number may have no value (although social capital theory would suggest otherwise), but when a user looks at a Facebook page and sees "5 of your friends Liked this page" with a list of who they are, that has a huge impact on how they think. It's like having a personal recommendation. That's worth a lot. Likes do have value.
So I just wanna know if ublock origin blocks all this or not.
That title is misleading, the article clearly says "The SDK code is so big that it represents about 16% of the total size of all Javascript on the average web page." which is clearly not 16% the total site.
Was the title changed? As it is, it clearly says '16% of the code', and to me that does imply only the javascript.
Earlier quoted context omitted.
Was the title changed? As it is, it clearly says '16% of the code', and to me that does imply only the javascript.
I think most people would consider HTML and CSS "code", too. Why would you not count HTML if it's in its own file, but assuming you would count it if it was JSX returned from a React component?