Best practice question - state attr

I just wondering what’s the best practice here
I’ve got a sensor which collects website pages and visitors like this:

it’s a top 10 of pages and visitors which I receive from a rest sensor.

I would like to display this top 10 in a card eventually.

Is it best practice to create seperate sensors for each “page” and one for each belonging “visitors” stats?
but then I get like 20 sensors.

Or can I display the result another (easier) and more nicer view?
when I execute this template:

{{ state_attr('sensor.api_breakdown', 'results') }}

I get a “ugly” view with characters like ( in { … This clearly needs to go

Attributes seem fine, but take care not to exceed 16KB per update since these get stored in database.