Thanks for reporting this. We have now changd the way Whisp Map uses the Whisp API and that provoked the issue.
When using points the Whisp API retruns now an “Area” of 0. This was done to align with systems (such as TRACES), and because you could argue reasonably that points don't really have an area; previously it showed the underlying pixel area: https://github.com/forestdatapartnership/whisp/issues/106
We have added a quick fix in Earth Map / Whisp Map to instead assign points an approximate area of 100 m² for readability (the Whisp analysis is done at 10 m pixel resolution) as the areas returned for the different layers will have always and area of 0 or 100 square meters when doing point analysis.