Find out which kind of slow you have
A delayed network response, a busy web app and memory pressure can all feel like “Safari is slow,” but call for different checks. Compare a few unrelated pages and note whether typing, scrolling, loading or switching apps is the actual problem.
| Pattern | Start here |
|---|---|
| One website loads or scrolls badly | Reload, check that site's work, then extensions and site data. |
| All sites load slowly, but the Mac responds | Network path, service issues and relevant Safari settings. |
| Safari and other apps hesitate | Activity Monitor, memory pressure and available storage. |
| Safari stops responding completely | Save what you can, quit normally, then force quit only if needed. |
There is no fixed healthy tab count. A few active web applications can do more work than many quiet reference pages. Keep the task and symptom in view rather than blaming the number beside the tab group.
Reload, then reopen Safari if needed
Apple's Safari troubleshooting guide starts with View › Reload Page or Command-R. Save work in an editor, form or web app first if reloading could discard it.
If that doesn't help, quit Safari normally and reopen it. If it cannot quit, Option-Command-Escape opens Force Quit; that abrupt action can lose unsaved page work. To avoid reopening the same unwanted pages, Apple documents holding Shift while opening Safari.
After reopening, test the original action with a small number of necessary pages. Closing optional video streams or unused active web apps reduces work directly; it is more targeted than clearing every browser setting at once.
Test optional extensions
On macOS 15 Sequoia, 26 Tahoe and 27 Golden Gate, open Safari › Settings › Extensions. Turn an optional extension off and repeat the problem action. If you changed several at once to find whether extensions matter at all, re-enable them one at a time to identify the dependency.
An extension may alter page content, filter requests or add features. A site working differently without it is evidence to investigate that extension's version and settings, not proof that all extensions are harmful.
Update the extension through its genuine developer or App Store route. On a work Mac, keep required security or organizational extensions under IT's control. Record the site, extension version and reproducible action if you contact the developer.
Test site data before removing it
Open File › New Private Window and try the affected site. Apple recommends this to test whether stored cookies, caches or other website data could matter. A private session may also differ in sign-in state and permitted extensions, so treat it as a clue rather than a complete isolation of one variable.
If that test helps and you decide to remove the site's data, first confirm that needed work has synced and you know how to sign in again. Then use Safari › Settings › Privacy › Manage Website Data, select the affected website, choose Remove, then Done.
Return to an ordinary window and test again. Removing data can sign you out and remove local site state. The cache guide explains the consequences; don't clear every site's data when one site is the problem.
Check the Mac's workload
Open Finder › Applications › Utilities › Activity Monitor. In CPU, look for sustained activity during the symptom, then use Memory to inspect pressure. A briefly busy process while a page opens isn't the same as one that remains busy after the page should be quiet.
Safari web work can appear in separate WebKit processes. Don't assume Safari's main process alone accounts for every page's cost, and don't terminate a process merely because it has a technical name.
On our M2 Max documentation Mac, macOS 27.0.1, a read-only check on 23 October 2026 found WebKit web-content executables in the logged-in account at:
/System/Library/Frameworks/WebKit.framework/Versions/A/XPCServices/com.apple.WebKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContentThis framework service can serve web content; its name alone doesn't identify a Safari tab or prove that Safari is the client. EnhancedSecurity variants were also present. The check established path and ownership, not a CPU measurement or performance comparison.
For the wider list, see processes you'll see in Activity Monitor. If pressure remains high across apps, use the memory guide; if the whole Mac is slow, use the broader diagnosis.
Check the network path and site compatibility
If every page loads slowly while the Mac itself responds normally, compare another device on the same network and check whether other internet tasks are affected. That distinguishes a browser-only problem from a wider connection problem without changing system settings.
Apple's Safari guide also covers Private Relay, VPNs and other security software, and settings a particular site may not support. Review the specific feature implicated by the symptom. Don't disable every privacy or security control as a general speed recipe.
On a managed Mac or network, ask IT about required VPN or filtering software. For one malfunctioning site, give its operator the URL, Safari version and action that fails. Don't send private page contents or account information merely to describe a loading problem.
Update Safari and retest
Safari is supplied with macOS. Check System Settings › General › Software Update for the supported Safari and macOS updates, save work and complete a required restart. The Safari update guide explains the available routes.
A claim about one early OS build may not apply after later fixes. Record the exact installed macOS and Safari version before applying a workaround. If only one website still fails after the smaller checks, contact its developer rather than reinstalling the entire operating system first.
How Tend shows Safari and WebKit
Tend's free app list groups helpers by the outermost .app in their executable path. Helpers inside Safari's app bundle can join Safari, but the framework-based WebKit path above is outside it and remains a separate own-user entry. Tend therefore doesn't promise one complete Safari-with-all-tabs total or identify a web-content process's exact tab.
Free CPU, memory and estimated app watts can add workload context, with 24 hours of energy totals and longer views in Pro. For a suspected browser task, combine that context with Safari's actual pages and Activity Monitor rather than attributing all WebKit work to Safari.
Questions
Why is only one website slow in Safari?
The page itself, an extension, stored website data or a site-specific compatibility issue may be involved. Reload after saving work, test optional extensions and try a private window before deleting data.
Will clearing Safari's cache always make it faster?
No. It can help a particular stored-data problem, but does not fix every network or CPU issue. Removing website data can also sign you out and remove local site state.
Does WebKit WebContent always mean a Safari tab?
No. A WebKit framework process can serve web content for a client, and the displayed process name does not by itself identify the browser or exact tab.
Does Tend combine all Safari web processes into Safari?
No. Its grouping uses executable paths. Helpers inside Safari’s app bundle can join Safari, but framework-based WebKit services outside the bundle remain separate own-user entries.
Related guides
Diagnose the whole Mac
Separate a browser issue from a system bottleneck.
Update Safari
Use the supported macOS update route.
Clear cache carefully
Understand website-data consequences.
Chrome helpers
Compare a different browser’s process layout.
Sources
- Apple, If Safari does not work as expected
- Apple, View and group process activity
- Apple, Read Memory Pressure
- Apple, Update macOS and included Safari software
Inspect the workload behind the slow page
Tend is free to download. Pro is $1.99 a month, $12.99 a year with a 7-day free trial, or $29.99 once.