18 total posts
A common occurance nowadays
Sadly I see this all the time now, on nearly all professionally created web sites.
I'm fortunate in that I have a fast internet connection and so they whiz through, but for those with dial-up or slow broadband it can be a real problem.
You mention older machines. I remember the first car I brought over 40 years ago had drum brakes and cross-ply tires. Remember those? Things move on and such vehicles wouldn't be allowed on the roads here in the UK nowadays.
No such restriction on the internet of course, but 'things move on'. That's my 'real' answer, for what it is worth.
Speed isn't an issue . . .
I have a 30 Meg cable, Pentium dual core, 3 Gig of RAM, and XP pro.Pages load fast. But the added "crap" makes them slow.
I know, I just ranting.
Thanks for the feedback, Wayne.
They will be working on speeding up the pages... but these days as Mark pointed pages are loaded with scripts--they are no longer just the flat HTML pages as they once were.
Thanks . . .
I noticed a degrade in speed/stuttering on scroll with the new pages. Thus prompting my rant.
No recent changes here, but...
I disabled the Facebook, Twitter, etc scripts as soon as CNET started rolling them out some time ago. CNET is pretty fast when all those other hands aren't in the cookie jar.
I managed to disable those
Trial and error with me adding and removing filters for various components until I got it right.
But I suspect John used a custom CSS file.
CSS wouldn't cut it...
I used my HOSTS file along with AdBlock Plus, much the same as you did. Basically, I blocked nearly all third-party scripts, along with those I've deduced are used solely for advertising. They generally aren't that obtrusive, especially compared to many other sites I frequent, but now and then they just slow page loads to a crawl - especially Facebook and those surveys lately.
I HATE that facebook thing
For months I couldn't come to CNET already signed in. Finally got some advice on how to defeat it and not have to sign in again each time.
I don't understand what so many like about Facebook anyway. It seems to me a way to end up reading a lot of stuff on each person's "Wall" you'd rather not anyway.
I've never had a problem being remembered.
I'm not connected to Facebook on CNET and the system always remembers me.
I don't understand why Facebook is an issue for you when it shouldn't bother you if you don't use it or connect to it when logging in.
Facebook is there for people to use, if and when they want to. If not, just simply ignore it, no one is forcing anyone to use it.
well, relatively so anyway,
We're old. We don't understand this need to plaster ourselves all over the internet with photos and comments and "Like".
Someone recently said, Facebook is Mordor! I couldn't have described it better myself.
I solved it
I had to enable third party cookies, do the sign in, then I could disable third party cookies again and CNET continued to sign in each day I returned to site. For some reason FF sees CNET sign-in as a third party cookie I guess.
I had great success with using the hosts file to disable
and to lesser extent
No magic involved. Just looking at the "waiting for ..." and "ready with ..." messages on the status line in Firefox suffices to find the timeconsuming links. An occasional look in the html source helps also.
CBS did it
As of right now, it's impossible to remain logged in to CNET, and comments to articles will not appear, without running a script hosted on cbsistatic.com.
Minimum scripts needed:
It seems, today at least, these are four sites that need to be allowed for basic functionality in CNET.
cbsistatic.com (login seems to be dependent on it, at least since Tuesday afternoon)
com.com ('reply' links do not function without it)
cnetstatic.com (comments to articles will not appear without both of these allowed)
You also need gigya.com allowed in order to login to CNet, even if you are not using a 3rd party login.
Gigya can be blocked again after the cookie gets set (usually after navigating to an article or something).
As far as I can guess, gigya.com only needs to be allowed long enough for purs_1 to appear in the cnet.com cookies.