Problems conecting & loading...and bounced back e-mails
- goodhealthgourmet Dec 3, 2011 06:54 AM
Hoping this actually posts. I was having such problems with the site that I tried to send an e-mail instead to let you all know, and it came back to me FOUR times (I tested my e-mail several times to be sure it wasn't my account. It wasn't).
Here's a copy, addressed to email@example.com...
Sorry to do it this way but I got so frustrated waiting for the pages to load on the site that I gave up. Ever since about 10 pm Eastern time last night, connecting to CH has been excruciatingly slow. I started watching the script that runs along the bottom of my Google window after I navigated to a page, and in addition to the usual "waiting for chowhound.chow.com" and Google analytics-related stuff, there were a couple of messages about connecting to/loading Facebook, something having to do with a "secure-us" connection, and finally "optimizely?"
Whatever is going on over there, not only does it make browsing CH practically impossible for me, it also slowed down Firefox so much that I had to quit and re-launch my browser to connect to anything else. Once I did, performance returned to normal with no lags at all on any other sites...until I tried navigating to CH again. Once I landed on CH, whammo, everything else came to a screeching halt when I went back to the other open tabs.
I hope I explained this all clearly enough for Engineering to figure out the problem. Ironically it began last night very soon after I said how much faster things were moving since they fixed the problem with long hang times on posting!
P.S. here's hoping you actually receive this because my first attempting at sending it resulted in *three* "Mailer-Daemon notifications that it was undeliverable.
"P.S. here's hoping you actually receive this because my first attempting at sending it resulted in *three* "Mailer-Daemon notifications that it was undeliverable."
I just wonder if the problem isn't with your ISP? I say that only because getting back emails as undeliverable normally means that the problem is either a "bad address" or there is some other issue at the senders end. I don't really have any posting or loading issues (maybe a little slow to load some long threads but that particular problem is a long standing issue).