Front Page › Forums › Development › Optimising the client side code output
This topic contains 3 replies, has 2 voices, and was last updated by JSE Admin 6 months, 1 week ago.
Compressing https://load.jsecoin.com/server/load/<user_id>/<website_url>/ could save 9.4KiB (64% reduction).
Anyway we can get that JS code compressed and then delivered over Gzip?
Unsure how it may affect the client side code under compression.
Yeah we should definitely be minifying that to save network load. I don’t know why that wasn’t implemented from the start #facepalm
Not sure how much benefit there will be to gzipping it after that in regards to transfer and load times. Will need to test that part out.
Thanks for your help Peter!
I see it as one of the very minor things on a large list of things required to do when creating a new token, mining platform and setting up a new business.
but thanks for the reply and having it on your list, it does effect us webmasters 🙂
It’ll be rolled out on Sunday 🙂
Mail (will not be published) (required):
Trust is essential and will be proportional to our operating transparency. We take pride in operating an open ethical business.
Read about our privacy efforts
The page above also contains an opt-out link to turn off browser based JSE cryptocurrency mining across the entire network
A Cryptocurrency Company
© All rights reserved
Enter the destination URL
Or link to existing content