The graphical issue is something we just haven't prioritized. I made a fix in our development environment for this particular page now. The issue probably exists in many other places as well though.
Regarding the counties with empty names. These are the geocaches in Florida with an empty county name:
+---------+----------+---------+-----------+------------+
| gccode | archived | region | latitude | longitude |
+---------+----------+---------+-----------+------------+
| GC1449 | 1 | Florida | 27.000000 | -82.883333 |
| GC5285 | 1 | Florida | 0.000000 | 0.000000 |
| GC52D3 | 1 | Florida | 0.000000 | 0.000000 |
| GC85D0 | 1 | Florida | 1.000000 | -83.016667 |
| GCG89Z | 1 | Florida | 29.999983 | -81.000000 |
| GCGVHP | 1 | Florida | 30.000000 | -81.000000 |
| GC5808D | 0 | Florida | 29.652683 | -84.500133 |
+---------+----------+---------+-----------+------------+
As you can see all but one is archived (second column). If we then focus on GC5808D which actually isn't archived.
The geocache is to far out in the sea to match any county polygons. The geocache itself has the region Florida to it, entered by the cache owner. Project-GC can however not match any state or county to it by itself, because it simply isn't in any. The region from the cache owner is used though, but as you probably are aware, there are no county data in the geocache-metadata.
When a geocache isn't inside any polygon (county) we do use the nearest one, up to a certain distance. This seems to be further away than that configured max distance.