Critiques pour Wappalyzer
Wappalyzer par Wappalyzer
Avis de jdk17
Noté 5 sur 5
par jdk17, il y a 4 mois547 notes
- Noté 1 sur 5par FullMetalStacker, il y a un jourI 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.Réponse du développeur
mis en ligne : il y a 9 heuresThis should be fixed in the next update.
On-demand detection wouldn't work well as much of the analysis happens during page load (inspecting response headers, certificates etc.). Where possible work is already being deferred. - Noté 1 sur 5par pyx, il y a un jourI really like this extension, but I had to disable it due to a memory leak. Every time I open a page, the extension freezes my browser and jumps about 6gb memory usage.
- Noté 2 sur 5par Sam, il y a 3 joursAfter enabling Wappalyzer in Firefox 150 on Windows 11, the WebExtensions process immediately jumps from ~460 MB to 6–7 GB RAM and 100% CPU.
I verified this using about:processes and Firefox memory reports. With Wappalyzer disabled, memory usage returns to normal. With Wappalyzer enabled, the extension process spikes instantly.
This makes the browser almost unusable. Please investigate a likely memory leak or infinite loop in the background page. - Noté 2 sur 5par Ce@p2g77L#W, il y a 12 jours
- Noté 5 sur 5par Utilisateur ou utilisatrice 19652246 de Firefox, il y a 4 mois
- Noté 5 sur 5par Laurent FAVOLE, il y a 5 mois
- Noté 5 sur 5par Utilisateur ou utilisatrice 19539434 de Firefox, il y a 6 mois
- Noté 5 sur 5par Utilisateur ou utilisatrice 19184389 de Firefox, il y a 9 mois
- Noté 4 sur 5par taire, il y a 9 mois
- Noté 5 sur 5par Utilisateur ou utilisatrice 19094638 de Firefox, il y a 10 mois
- Noté 5 sur 5par 洪金宝, il y a 10 mois
- Noté 5 sur 5par Z403, il y a un an
- Noté 5 sur 5par lyz, il y a un an
- Noté 5 sur 5par 1123, il y a un an
- Noté 5 sur 5par Belco90, il y a un an
- Noté 5 sur 5par Utilisateur ou utilisatrice 18971081 de Firefox, il y a un an
- Noté 3 sur 5par Utilisateur ou utilisatrice 18978736 de Firefox, il y a un an