I have 16 GB ram and AMD A10 7TH GEN A10-9600P processor if it is about display i have Big LED and a 2 cooling fans i don’t know why i bought them but then also and SATA i guess
Where the heck is problem
Sorry for bad english
My English is RIP
use mozila firefox browser. If you use chrome it will lag like hell 
3 Likes
Try using Edge browser.
There is problem with makeroid when you spend time on it its going lagly
1 Like
I am using CHROME and makeroid is working good and fast too 
1 Like
Makeroid Is Working Very Slow On My PC
i have same problem here, but i can handle it by:
1.try to restart the browser often, if you working with large and many blocks it will slow down time to time
2. try not to often clean up your block
3. use as little block and screen as you can
With chrome it’s smoother, but the page freezes at least 5 seconds every two clicks. Very VERY annoying. With Firefox, it’s not very smooth, but no freeze, so i use Firefox
I currently have 8 GB of RAM and its lagging after 5 minutes in my project. In two days, I’ll have 12GB of RAM, I’ll see if there’s any changes!
1 Like
It also talks about it here: https://community.makeroid.io/t/the-lag-about-the-blocks-editor/1648/13
Works great if you have a really good connection and PC.
/Boban
2 Likes
yea Boban is right.Its all about good connection and PC
No joke man I have postpaid data plan man
But then also i am facing issues
It’s now better with Opera
Use browser in incoming mode
16 GB RAM / Intel i5 / MacBook Pro 2012
Lag is still there.
Aren’t these specs enough for Makeroid to work properly?
First, it’s a laptop
Intel i5, Could it be this one? there is a difference between desktop and mobile processors
Your speed test is for your nearest test server and the Makeroid server is not even in your vicinity where you are.
However, I don’t know how reliable these tests are through the speed test but here are my tests anyway.
Other tests you can perform for connection, Ping and Traceroute.
e.x Windows
ping google.com
tracert google.com
C:\Users\Boban>ping google.com
Pinging google.com [172.217.22.174] with 32 bytes of data:
Reply from 172.217.22.174: bytes=32 time=1ms TTL=55
Reply from 172.217.22.174: bytes=32 time=1ms TTL=55
Reply from 172.217.22.174: bytes=32 time=1ms TTL=55
Reply from 172.217.22.174: bytes=32 time=1ms TTL=55
Ping statistics for 172.217.22.174:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
C:\Users\Boban>tracert google.com
Tracing route to google.com [172.217.22.174]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 1 ms 1 ms 1 ms gw2-no516.tbcn.telia.com [81.232.129.1]
3 1 ms 1 ms 1 ms fre-peer4-link.se.telia.net [81.228.86.25]
4 1 ms 1 ms 1 ms s-b5-link.telia.net [62.115.123.166]
5 1 ms 1 ms 1 ms google-ic-319323-s-b5.c.telia.net [213.248.103.67]
6 3 ms 2 ms 2 ms 108.170.253.177
7 2 ms 1 ms 1 ms 216.239.58.153
8 1 ms 1 ms 1 ms arn09s11-in-f14.1e100.net [172.217.22.174]
Trace complete.
C:\Users\Boban>
/Boban
1 Like