Safari can't load specific websites

1. Empty Caches

Safari > Preference > Advanced

Checkmark the box for "Show Develop menu in menu bar".

Develop menu will appear in the Safari menu bar.

Click Develop and select "Empty Caches" from the dropdown.

2. Reset Safari.

Click Safari in the menu bar.

From the drop down select "Reset Safari".

Click "Reset".

3. Safari > Preferences > Privacy > Cookies and all other website data:

Press “Remove All Website Data” button

4. Turn off Extensions if any, and launch Safari.

Safari > Preferences > Extensions

That post was for a computer version of Safari.

Double click the Home button and swipe Safari upwards. Go to Settings/Safari and clear History and Website Data. Open Safari and test.

Safari - Clear the history and cookies on your iPhone, iPad, or iPod touch

Safari website data on your iPhone or iPad - How to clear

I'm having the same issues... took me awhile to get into this post, because (ironically) Apple.com is one of the sites that Safari just will not load for me. Again, I can open these same pages in Chrome or Firefox with zero issues, THEN - after refreshing - I can get it open in Safari.

All of the above suggestions have been tried, as well as others from the various threads I've found in the Communities and elsewhere online.

What's even more interesting is that this exact same problem exists on my iOS devices... Safari won't load the same specific pages on my iPhone 5 or iPad Air (iOS 7), but Chrome or other 3rd party browsers will.

None of what you just said makes any sense to me if I open up settings nothing of what you said is there, if I try to open up that app by itself it surely is not there. I am talking about my Iphone 6 plus here I do not have preferences/ extensions and do not know where to find all the stuff you are talking about. Maybe you could be more clear on this matter

Safari 5.0.1 or later: Slow or partial webpage loading, or webpage cannot be found

I am having the same problem and have tried everything except the instructions in Linc Davis' post -- next on my list, but honestly, shouldn't be necessary. I've noticed that as soon as I load the page in Chrome, Safari is also able to load it. I'm not sure what they changed in the last Safari update or two, but clearly something broke.

Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.

Feedback

I experience the same thing also. I hope Apple will fix this soon...

dominic23's steps worked for me. Until completing those steps two sites that would refuse to load (among others) were Facebook and Wikipedia. Opening on chrome presented no issues.

HI all,

seems I meet this problem after I upgrade to YOSEMITE, for example some website (www.codeporject.com) can't load completely and some can't load , and I try to solve it by add the auto detect proxy,

you can set the it bye safari->preference->advance->proxy->auto detect proxy.

although, it is still a bit slow I think , but now, it can load the pages completely. my version of sarfari is 8.0 .

cdlike74

thank you

Your advice solved my problem

But in my mac the navigation was following

safari->preference->advance->proxy->auto proxy discovery

My dad had this problem on his 2007 MacBook Pro(I know. I'm embarrassed for him...) and I was able to fix it by reseting the browser(Safari>Reset and than select all the check boxes) and then clearing the cache(Develop>Clear Cache).

Hi there

Exactly the same issue after upgrading to Yosemite. rightmove.co.uk will not load in Safari or Firefox and I don't really want to remove all my website history etc. as I will have to set up all those passwords again.

Tried the "proxy" fix but that didn't work for me unfortunately.

Installed Chrome and now that website loads fine.

Bit of a work around - so hopefully the issue will be resolved by Apple.

this link no longer exists...Linc.

I am also facing same problem. However, Google chrome opens same URL without any issue on MAC book pro.

I appreciate responses having possible solutions.

However, I do not expect this type of critical issue from apple.

Shame on Apple.