Q: safari iOS 8.1 freeze and slow

STill very very unhappy with NOmfix from Apple...notice how the stupid capital letters still type i. safari on this post.  I am so sick of trying everything to get a better wifi connection with this **** ipad...forgetting networks...rebooting modems, etc etc.  Apple *****.

I have had the same disappointing experiences with my iPad3 and have tried everything I can think of to get it fixed.... .to no avail. Apple doesn't seem to care any more whether we are happy with our Apple products. I miss the Apple that Steve created and has since gone away.

Hopefully iOS 8.2 will make my iPad self destruct - then I'll be able to move on!

Any improvements with 8.2.

NOt that i can tell notice that the NO is still capitalizing on safari wit this response.  8.2 also doe not work with the facebook app.  When on your newsfeed, if you click on any one of the options at the top, friends, comments...you can only click one time otherwise it doesn't do anything next time you click.  You have to close out the app, restart.  Thrn clck on the option at the top...then in the next screen that pulls up, continue to click the next comment to keep going...or you have to close out each time.

APple is too proud of their watch to fix anything else. Poor Steve Job's would be so ashamed..

I'm having this same issue on my iPhone 5.  I just got the 8.2 software update yesterday and after I loaded it, Safari hasn't been working right since.  I thought it was just me at first, but apparently, I'm not alone.  I hope that something can be fixed about this soon because it's really annoying.

i loaded a 64 GB iPad 3 with 53 GB free with 8.1.3, as a new machine when it didn't work with any of the other fixes. Resetting would buy about 3 or 4 minutes of  marginal Safari performance, then degrade again. The new machine worked for less than 24 hours , then it degraded to unacceptable speed.  Finally after months, converted to Chrome. Not as good as Safari on iOS 7, but at least Chrome is usable

An iPad without a decently fast browser - what's the point?

I Just updated to ios 8.3.  Pleased to report...for the time being...and keeping my fingers crossed...that the blue load line on Safari is moving lickety split!

Dear Momolorient, dear Safari / Webkit developers,

I still use my 8 GB iPad 2 with iOS 9.3.4 on a daily basis...!

For most simple tasks and webbrowsing it is still quite useable,  but it is definatelly reaching its end of life.

The one thing that it really cannot handle anymore is web sites with a lot of javascript running in the background for tracking and advertisement purposes. E.g. articles on nytimes.com.

My usual approach is to switch to Safari Reader mode, or to send the page to the separate Readability app. It helps a bit, and offers at least a superior reading experience.

Today, I tried another approach: disabling Javascript. And to my surprise, the nytimes.com articles opened quite fast...!

The downside of diabling javascript is that it is an all-or-nothing approach on iOS.

Many websites won't work at all without Javascript...

On the one hand, I can blame such website developers for abusing javascript too much.

On the other hand, I can blame Apple for the limited control iOS users have on javascript.

Suggestion:

What I would like in to have in the Safari interface, is an option to enable/disable Javascript only for the current site.

Of course, this setting is then applied any time the user visits the website in the future. :-)

You are not talking to Apple here.

This is a user to user community technical support forum.

We are all users here, like yourself.

If you want Apple to read your ideas for iOS or iPad improvements, post multiple suggestions/feedback here.

http://www.apple.com/feedback/ipad.html

OH thanks, MichelPM.

This was my first contribution to Apple communities ever. I expected Apple to scan these communities, and hoped for some constructive feedback of other users on my suggestion...

Again, thanks for the advise. I will forward my suggestion to Apple then. All my hopes for any feedback will then be lost though. ;-)