I don’t have any more tips really. The loading time is better on subsequent attempts to load because Glide has cached the images. On your first try, the device has to load all images presented on the first screen, so it takes more time.
Maybe one tip is to move another tab that has fewer images to the first position on the left.
2 Likes
hmmm… I’ll test this idea!
I didn’t realize the initial screen impacted the time. Thought the app tried to load everything at one.
2 Likes
Having a lot of unused CSS in a file can slow down your application by increasing page load time, file size, rendering time, and memory usage.
1 Like
Right. I make sure to keep it clean 
I added a light front page and it works on mobile but on pc, the heavy page still opens first. Is there away to change this?
*Nevermind, I was using an old link 
**The new front page shaved off 3-5 seconds so that’s progress 
Can i hide the nav bar for this page only?
Yeah, I think you can do that. But does it still load that as the first page? I haven’t tried it.
1 Like
How do I remove this part but still have it visible on the other screens?
You need to have class names given to components that only exist on your Home Screen.
ok. I have all the components within a container. The current class is full-container:
.full-container {
height: 100%;
background-color: #000000;
}
You need CSS to hide the bottom tab bar
If I add:
/* Hide bottom tab bar */
.tab-bar {
display: none;
}
Will this work? So far I’ve had no luck.
how are two classes written in here?

full-container, tab-bar
?
you guys are being cryptic today 
#page-root:has(.full-container) .has-tab-bar > div:last-child {
display: none;
}
1 Like
this worked! Thanks @Himaladin 
one sec…what would cause it to work in the editor but not on the installed mobile device?
1 Like
It’s actually working on my test app but not on my published app… strange.
There may be a time delay problem for publication. Close your builder and reopen, usually works.
I’ll wait a while to see if it kicks in…
When I click “Preview CSS” , it appears to be working but with compiled CSS it is no longer enabled. Is that normal?
Keep the compiled CSS button always in the off position, or you will lose your CSS functionality.
1 Like
ooohhh ok!!
Maybe this is why I had trouble getting some CSS to work in the past 
Strangely, most of our tinkering worked while it was in the “on” position.