When you install applications during the time you use your Mac some of them may add themselves in Startup Items. Connect back each device one at a time and you will soon find out what caused the problem. If the slowness disappeared when you did this.
Sometimes a peripheral connected to your computer can cause slow mac issues without it being apparent. Disconnect dongles, extra hard drives, extra displays, docking stations, networking dongles. Disconnect devicesĭisconnect every external thing connected to your mac.
If you are lucky, maybe this is the only thing you have to do! If not, go back to that bookmark when you have restarted and read on. If none of these suggestions help you just have to hold the power button down on your Mac for about 5 seconds to force it to shut down. In the window that pops up, try to quit the application from there. Try the key-combination pictured below to force quit stubborn apps. If your Mac won’t shut down it could be applications that prevents it from doing so. Choose Shut Down from the Apple () menu.TIP: Bookmark this page, press CMD + D to add a bookmark in your browser. If you are lucky, maybe this is the only thing you have to do! I promise this guide will be here when you come back online again. So if you haven’t already: please start this guide with a shutdown of your computer (not restart, shutdown). It is often hanging applications and similar that in the end can make the computer feel slow and sluggish. Have you tried turning it off and on again? Ever heard this? Its actually not a joke… Your Mac can be turned on for weeks or months without any serious problems, but every now and then a shut down is recommended.
Is your Mac running slow showing you that spinning wheel? Starts to feel sluggish, slow and unresponsive? This article should help you out! 1. By employing the redirect that TidBITS describes, you cause the lookup to fail instantly and you’re good to go.14 Easy Ways To Speed Up a Painfully Slow Mac If it had simply denied requests, all would have been fine: your Mac would’ve ignored the attempt and swiftly moved onward. Yesterday’s problem was that Apple’s server was slow in answering. It involves simply(?) editing your Mac’s /etc/hosts file and making requests to fail outright. In the event this is not remedied, however, Adam Engst and the team over at TidBITS have a workaround. Whatever the reason, it’s clear that OCSP lookups should be isolated from any other issues Apple (or its providers) may have, and I’m sure that’s being (or been) remedied. Based on temporal coincidence, one could assume that this was triggered by the high demand for Big Sur. I have no doubt that Apple engineers spent many hours last night post-morteming this event and likely coming up with a plan for some redundancy in this department. Thankfully, Apple resolved the OCSP/Certificate Server issue pretty quickly in the grand scheme of things, but it begs the question: why did Apple let this happen in the first place? Having that sort of Achilles Heel baked into such a critical and common part of the macOS experience seems like an oversight.
Meanwhile, no one could download macOS Big Sur, either. And matter it did! For about an hour yesterday, Mac apps wouldn’t launch (or would launch slowly), rebooting was super-slow (for the same reason), and even Zoom connections took minutes to connect.