Reviews of Wappalyzer

By: Wappalyzer

List of user reviews and ratings for Wappalyzer

Total ratings

4.40 (Rating count: 545)

Receive review notifications

Get notified when new reviews are posted so you can respond quickly.

See reviews on Firefox Add-ons Store

View and respond to reviews directly on the store page.

Visit

Review summary

Overall, reviews are mostly positive: users say the add-on works, is easy to use, and is highly regarded for recon tools. The most consistently reported downside is installation issues, with several users seeing 'Installation aborted because the add-on appears to be corrupt,' including on Linux Flatpak. There are no widely repeated functional complaints beyond installation errors. A few reviewers warn about misuse or malware claims, but those are not common across reviews. The tool is generally seen as useful but with platform-specific installation problems.

Pros

Works as expected for recon tasks
Easy to use / user-friendly
Strongly regarded for recon tools and websites
Generally considered a good/best extension by users

Cons

Installation aborts due to the add-on appearing corrupt (repeated across multiple reviews)
Compatibility/installation issues on Linux Flatpak (non-working or problematic installation)

Upgrade to see all 296 reviews

User Reviews

Recent rating average: 1.40

All time rating average: 4.40

Upgrade to see all 296 reviews

13% (39)

Date	Author	Comment
2026-07-05	xi*****

2026-05-08	Va*****	Memory Leak -- extremely high CPU usage Deleted as for now
Memory Leak -- extremely high CPU usage Deleted as for now
2026-05-06	ne*****	I spent two days to catch reason of huge lags of my laptop. Huge disrespect and uninstalled forever.
I spent two days to catch reason of huge lags of my laptop. Huge disrespect and uninstalled forever.
2026-05-06	xe*****

2026-05-05	Sh*****	Hello Devs, Thumb Rule: Changes pushed to production must not degrade user experience. If a release impacts multiple users, immediately assess severity and deploy a hotfix faster and if you can't there is always an option to roll back the changes so that devs get time to fix and user experience remains intact. It's been a while and feel you guys need time to fix, So why don't you revert changes from previous release 6.12.1 that are causing leaks? This will help us use the extension without worrying. I was about to completely uninstall firefox because of the problems wappalyzer created.
Hello Devs, Thumb Rule: Changes pushed to production must not degrade user experience. If a release impacts multiple users, immediately assess severity and deploy a hotfix faster and if you can't there is always an option to roll back the changes so that devs get time to fix and user experience remains intact. It's been a while and feel you guys need time to fix, So why don't you revert changes from previous release 6.12.1 that are causing leaks? This will help us use the extension without worrying. I was about to completely uninstall firefox because of the problems wappalyzer created.
2026-05-04	An*****	Extremely high memory usage. Disabled
Extremely high memory usage. Disabled
2026-05-01	Mi*****	Extremely high memory usage recently/В последнее время наблюдается крайне высокое потребление памяти.
Extremely high memory usage recently/В последнее время наблюдается крайне высокое потребление памяти.
2026-04-28	Fi*****	Extremely high memory usage recently, stalling my laptop to a halt. Unacceptable
Extremely high memory usage recently, stalling my laptop to a halt. Unacceptable
2026-04-28	Fi*****	memory leak after update
memory leak after update
2026-04-27	Fu*****	I really love this add-on and it belongs to my core set of Firefox add-ons since many years. However, since the last update two days ago, it has made Firefox almost unusable due to extreme lagging. Firefox even started showing warnings that the browser was no longer responding. Judging from the other recent reviews, this is clearly a bug. That alone would not have made me rate it one star. But after disabling Wappalyzer, I realized how much faster my browsing became compared to the previous months. So this is not only about the recent bug; the add-on seems to have become a serious performance drag over time. This made me think that the core issue may not only be the current bug, but also the way the add-on performs its analysis in general. From a user perspective, the ideal solution would be an optional on-demand mode, where Wappalyzer analyzes a website only when I click the extension button. At the same time, I understand that fully on-demand analysis may not fit Wappalyzer’s model, because the extension probably wants to collect technology statistics from visited websites. A good compromise could therefore be time-shifted automatic analysis: instead of doing the full detection immediately when a new page is opened, Wappalyzer could wait until the page has loaded, the browser is idle, or a short delay has passed. Another good compromise could be a two-stage approach: perform only a lightweight initial scan during page load, then defer the heavier technology detection until later. That would still allow automatic detection while reducing the impact on page loading and general browsing performance. For now, I will keep it disabled even after the current bug is fixed, and only enable it when I really need it for a specific task. I hope the Wappalyzer team takes a serious look at performance and improves it significantly. If that happens, I will gladly increase my rating back to 5 stars.
I really love this add-on and it belongs to my core set of Firefox add-ons since many years. However, since the last update two days ago, it has made Firefox almost unusable due to extreme lagging. Firefox even started showing warnings that the browser was no longer responding. Judging from the other recent reviews, this is clearly a bug. That alone would not have made me rate it one star. But after disabling Wappalyzer, I realized how much faster my browsing became compared to the previous months. So this is not only about the recent bug; the add-on seems to have become a serious performance drag over time. This made me think that the core issue may not only be the current bug, but also the way the add-on performs its analysis in general. From a user perspective, the ideal solution would be an optional on-demand mode, where Wappalyzer analyzes a website only when I click the extension button. At the same time, I understand that fully on-demand analysis may not fit Wappalyzer’s model, because the extension probably wants to collect technology statistics from visited websites. A good compromise could therefore be time-shifted automatic analysis: instead of doing the full detection immediately when a new page is opened, Wappalyzer could wait until the page has loaded, the browser is idle, or a short delay has passed. Another good compromise could be a two-stage approach: perform only a lightweight initial scan during page load, then defer the heavier technology detection until later. That would still allow automatic detection while reducing the impact on page loading and general browsing performance. For now, I will keep it disabled even after the current bug is fixed, and only enable it when I really need it for a specific task. I hope the Wappalyzer team takes a serious look at performance and improves it significantly. If that happens, I will gladly increase my rating back to 5 stars.