# Mobile app bad performance Vs WebApp **URL:** https://community.thunkable.com/t/mobile-app-bad-performance-vs-webapp/2762731 **Category:** Questions about Thunkable X **Created:** [December 28, 2023, 3:56pm UTC](https://community.thunkable.com/t/mobile-app-bad-performance-vs-webapp/2762731 "2023-12-28T15:56:50Z") **Posts on this page:** 1 **Showing post:** 8
### Author: ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy) #### Post date: [January 19, 2024, 4:05pm UTC](https://community.thunkable.com/t/mobile-app-bad-performance-vs-webapp/2762731/8 "2024-01-19T16:05:19Z")
Can you share the blocks and/or project with us? It is impossible for us to know why this issue could be happening based on just seeing the app running in production. I would also take a peek at this post, which talks a lot about performance and how to use different blocks and variables to speed things up. > [@Accelerate your Thunkable application](https://community.thunkable.com/t/accelerate-your-thunkable-application/2716433): > > Since I encountered a performance problem with a complex application I programmed in Thunkable (especially on older phones), I decided to explore ways to speed up the application by optimizing the code for speed (sometimes at the cost of degrading its readability). Here is the first part of my research, how to speed up Thunkable apps and optimize code for speed. PART 1. I use the blocks shown below for my tests. The content under test is inserted in the middle, between Timer1\_Start and Timer1\_… --- _[View the full topic](https://community.thunkable.com/t/mobile-app-bad-performance-vs-webapp/2762731)._