Why does FPS drop when switching between game wiki pages? Any fixes?

FPS dips like that indicate something being rendered by the GPU or processed by the CPU. Are you hanging on to previous images or animations while you load new ones? Garbage collection may spike. Use smooth transitions rather than fully reloading assets. You might be loading too many resources up front; defer loading things like video. If you’re using WebGL or Unity, remember to dispose anything you’re not using anymore. Consider the structure of your DOM, since large complex trees can also cause problems. Profile your code with Chrome DevTools or similar to find the choke points. Render only what the user can see. If all else fails, perhaps you could publish a minimal reproducible example. All the best with this wiki thing.

FPS dips are usually the result of excessive asset unloading/loading or memory leaks. Are you preloading assets on every page? If so, try to add some simple caching functionality. In addition, make sure that unused assets are unloaded at the end of each page. Finally, if you’re experiencing FPS hiccups, chances are there’s something wrong with your page transition animations; they are likely too complicated. Streamline your transitions, simplify your textures, unload any unnecessary assets, and optimize your assets. You might also want to use async-loading techniques.

FPS dips on page change? Probably due to large asset sizes. Are you unloading old game assets, or do they accumulate? Consider using lazy loading of assets, and loading the next page’s asset set in the background. Avoid major scene changes between pages. Profile your game for memory leaks. Dispose of any unused objects. Fixing these areas should leave you with relatively stable FPS as you navigate through the wiki.