Such test case we call a GUI tests or GUI Test cases and those have GUI in their name indicators.
One test, multiple objects in it
Usually, we put all GUI checks on one screen into one test. This is according to multiple test methodologies.
Multiple tests one for each object
If one of the persons, who are checking the automated test log is not skilled enough, you would need to get human readable test reports. Then you can use the test suite name as the name of the page and to have one test per object. But consider a lot of
it(...) around each test. data-drivenen approach is then recommended, so for example in JSON object could be the object name, object xpath or class name and the
it(...) should be inside of the foreach cycle. The it name could be calculated as
"checking if the element "+elementName+" is present". Transfering the objects to array will be necessary for usage in foreach.
Then you can get test results for one-page TestSuite and for each object. This approach is a bit antipattern. In reality, you will not do thousands of test cases, but just a few of them, so it can break your statistics if you monitor such numbers/KPI's.
Decision is up to you. I personally would choose the methodical approach. One test, multiple objects. in the test suite for the page is then not only the GUI check but also other tests of the functionality, for example, multiple variants of the functional test, etc.