"NordPass is slow" describes four different problems that happen to share a symptom: the app taking a long time to open, autofill suggestions arriving late, sync staying incomplete, and the interface stuttering while scrolling a large list. They live in different parts of the system and have different causes. Anyone who starts by clearing data or reinstalling is treating a guess as a diagnosis.
Establish first whether the delay is in the vault or around it. If unlocking takes several seconds while other websites load instantly, the bottleneck is probably network or account handling rather than the vault itself. Our nordpass login account overview describes what normally happens during that sequence.
Measure before you change anything
Write down three observations: which device is affected, which operation is slow, and roughly how long it takes. Then compare against another device with the same account. A delay on one machine only points at that machine. A delay on every device points at the account, the network, or the size of the vault.
Time the operations separately. Note how long the app takes to launch, how long it takes to open after unlocking, how long the first autofill suggestion takes on a page you visit often, and whether a manual sync ever completes. These four numbers separate the problem far more effectively than a general impression.
Check the network path first
Filtered corporate and school networks, hotel Wi-Fi with a captive portal, mobile hotspots, and any connection using a filtering proxy can delay or block the sync endpoint. A vault that opens locally but refuses to finish syncing is a strong hint that the network path is the problem, not the vault.
Test the same account on a trusted personal connection. If it becomes fast immediately, the original network is delaying you. Do not solve this by disabling a security product or accepting a certificate warning on a managed network; report the blocked connection to whoever administers it instead.
Weak signal strength causes the same symptom in a different way. A weak mobile connection with poor latency can make every request feel stalled even when throughput looks adequate.
Reduce what the vault has to process
Vault size affects performance more than people expect, particularly on mobile. Several thousand entries with large attachments, long notes, and stored card details mean the client has more to decrypt and index on each open. This is not a flaw in the design, but it responds well to maintenance.
Archive entries for services you no longer use and delete obviously dead items. Large attachments are the most expensive kind of content to keep, so move rarely opened documents out of the vault if they are stored securely elsewhere. Trim notes that have grown into essays when a single line carries the useful part.
Run a duplicate cleanup at the same time. Removing duplicate entries reduces indexing work and fixes autofill picking the wrong password, which is a performance and a correctness improvement in one pass.
Look for competing tools
Two password managers, or a password manager plus an aggressive browser extension, compete for the same form fields and the same keystrokes. The result is a visible delay before suggestions appear and occasionally two overlapping suggestion panels.
Decide which manager you use, then disable or uninstall the others. If you keep a second manager for a specific legacy reason, restrict it to the domains that genuinely need it rather than leaving it active everywhere.
Aggressive ad blockers and privacy filters sit in the same category. Many have blanket rules that interfere with legitimate requests, and a blocked sync endpoint looks exactly like a slow one. Test with one filter disabled before concluding that your vault is at fault.
Account for mobile power and background limits
Mobile operating systems deliberately restrict background work to protect battery life. A vault that syncs instantly at home may only sync when you open it on a cellular connection with battery saver active, and the delay can look like a fault rather than a policy.
Check the battery saver setting and the app's background permission on your platform. Allow background refresh or background data for the app if you rely on syncing while it is closed. Expect an open operation to take longer the first time after the app has been fully terminated, since the client must rebuild its local state.
Low storage on the device causes its own delays, as the client writes temporary decrypted data while working. Freeing space often improves vault behaviour noticeably on older phones.
Adjust sync settings with intent
On-demand syncing, automatic sync on launch, and background sync intervals are all reasonable options, and choosing between them is a trade-off between immediacy and resource use. If you mostly use one device, longer intervals cost you nothing and reduce background activity. If you rely on sharing changes quickly, shorter intervals are worth the overhead.
Change one setting at a time and re-measure after each. Adjusting four options at once produces a result you cannot attribute, and you will not know which change helped.
Know when to stop optimising
If you have measured launch time, unlock time, autofill delay, and sync completion, and each is within a range you find acceptable, stop. Perfectionism here produces settings you do not understand and cannot maintain.
If performance degrades sharply after an app update, on one device only, or alongside a sudden change in vault size, note the date and the version and report it through the vendor's official channel with those measurements attached. We are an independent fan site and cannot diagnose your install, but a report containing four timings converts a vague complaint into something a support team can act on.