What's the point of having 1G on WAN and 2.5G on LAN? Traffic won't hit the LAN port until it's routed to the Internet, yet the WAN port is the bottleneck.
Edit: Seems like I switch up the port speed but my point still holds as the bittleneck still exist.
The LAN and WAN ports aren't labelled as such on the device and can be configured to do anything. The 2.5Gb port can also be used to take in PoE so for a lot of people - myself included - this will be the only port that's actually used, or at least the port that will be used the heaviest. The reason, I think, that it's configured as WAN by default is so that the LAN port can be used to plug a laptop in directly without disconnecting the whole network.
It doesn't matter. Port configuration can switch around and the bottleneck is still there. Traffic with in the broadcast domain (i.e. subnet) will handled by the switch alone.
There is WiFi onboard so it can have some actual benefits, depending on design and how user access resources, but how likely you're going to saturate that 1/2.5G link? Not even you stream some 4K movies from Plex to iPhone will does that.
I think you might have missed the point: with a managed switch that 2.5Gb port can be used to handle multiple WAN and LAN connections simultaenously. My home network includes two WANs and six LANs split purely by VLAN tagging and that 2.5Gb connection should handle all of them just fine.
Local NAS, local security cameras, in-house streaming, LAN multiplayer, local torrent-like data sharing (FYI, Windows Update and more uses the local network to share update between computers by default, so it gets downloaded once and then shared internally)
Does it have enough power to handle routing (not just switching) 2.5Gb + 2.5Gb + whatever the WiFi can support? My guess is it cannot and it would have pushed the price up signifcantly to do so.
Does seem counter intuitive to me as this is squarely aimed at enthusiasts who would like to min max their home network.