Clustered index would not be null at all in my case. However, one point in my mind is that at the intermediate level due to page splits on clustered index (I read that the intermediate level would be a clustered Key rather then the case of heap), would it lead to a page split on non-clustered index even its a sequential one.

I can see the NextPageID of DBCC IND is far way from the CurrentPageID.However, its sequential.Can we take this scenario as a page split? Once I defragment, all Pages are getting closer and sequential.

Also I can see a small percentage of fragmentation in this case. Is this fragmentation due to any kind of Page split?If I could add a FILLFACTOR for the non-clustered index would it be beneficial to reduce the fragmentation?