Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Lorenzo Pieri
19,772 PointsPage rendering at 60FPS or less
Let us take in consideration the fact that pages (just like games) might load at a lower FPS rate, dropping lower and lower (LoL much?)
If Im not mistaken, our naked eye can only see differences in framerate when the latter drops below 25FPS. If that is true, why would I care about the FPS rate dropping from 60+ to 30?
Thanks!
1 Answer
Gleb Vorobjev
13,704 PointsThe issue with a video game dropping to 30 FPS is that the rate of player's input may not quite correlate to the visuals, at least in terms of smoothness, depending on how the game is programmed. Some gamers claim that they can notice a difference between 30 and 60 FPS.
All that aside, dropping from 60 to 30 FPS should not be an issue for most web pages/apps. But if a certain effect causes a large drop in FPS, this should be a candidate for optimization from the developer's point of view. If the user is running a low-end machine with other processes competing for system resources, that 30 FPS might dip below ~25 FPS and cause noticeable visual lag.
I think the take away message is to use the Timeline panel to double check if your web page has any effects that are unusually resource intensive.