My website has just been finished! Please leave some comments and feedback and even constructive criticism to make it better! www.thecannonmc.com
Banned forever. Reason: Community harassment
Website Feedback
- Thread starter FytikMC
- Start date
- Status
PebbleHost
High performance, consistent uptime and fast support. Minecraft hosting that just works.
Your "captainbg.png" is 7.1 megabytes.
Total is 7.8 megabytes.
According to Net Index (http://www.netindex.com/) the average global download speed is 24.3 Mbps (3.04 MB/s).
This means, on average, your page will take at least 2.57 seconds to fully load.
There is absolutely no need to have a 7.1 MB image (3546x2500). Reduce that down to 1920 pixels width, and save it as .JPG with about 80% compression (won't even be noticeable since there is no text on the image) and boom its 768 KB (that's 10.6% the amount of bandwidth you were using before - AKA an 89.4% reduction!)
Before:
After:
In my opinion it looks a lot better because the image isn't being scaled down (which causes it to be blurry)
And at 768 KB, with a download speed of 24.3 Mbps, the image will fully download in 0.247 seconds.
Now you may be saying, "Well the image only loads the very first time someone goes to the site, and will be cached every time after that"
Well then let's also look at something else:
It appears you're using mcapi.us to retrieve some sort of playercount (although it doesn't look like you're using it anywhere).
However, mcapi.us is offline.
You could reduce your loadtime by another 500 ms just by pinging the server yourself and caching the data, rather than requesting mcapi.us to do it every time.
If not, at least cache the data from mcapi.us if you're not going to do it yourself, since requesting mcapi.us will add a few hundred milliseconds either way.
Last edited:
Is there a website or application I can use to scale it down without affecting the artwork?
Your "captainbg.png" is 7.1 megabytes.
Total is 7.8 megabytes.
According to Net Index (http://www.netindex.com/) the average global download speed is 24.3 Mbps (3.04 MB/s).
This means, on average, your page will take at least 2.57 seconds to fully load.
There is absolutely no need to have a 7.1 MB image (3546x2500). Reduce that down to 1920 pixels width, and save it as .JPG with about 80% compression (won't even be noticeable since there is no text on the image) and boom its 768 KB (that's 10.6% the amount of bandwidth you were using before - AKA an 89.4% reduction!)
Before:
After:
In my opinion it looks a lot better because the image isn't being scaled down (which causes it to be blurry)
And at 768 KB, with a download speed of 24.3 Mbps, the image will fully download in 0.247 seconds.
Now you may be saying, "Well the image only loads the very first time someone goes to the site, and will be cached every time after that"
Well then let's also look at something else:
It appears you're using mcapi.us to retrieve some sort of playercount (although it doesn't look like you're using it anywhere).
However, mcapi.us is offline.
You could reduce your loadtime by another half a second just by pinging the server yourself and caching the data, rather than requesting mcapi.us to do it every time.
If not, at least cache the data from mcapi.us if you're not going to do it yourself, since requesting mcapi.us will add a few hundred milliseconds either way.
Banned forever. Reason: Community harassment
I use Photoshop, which will allow you to set your compression level.
Paint does around about 80% compression on .JPG so it can be used just fine as well.
Or you can just use the one I made:
https://i.js.ai/captainbg.jpg
Jack,
I developed this site. I agree with the image compression, I had that on my mind but I forgot about it since the caching.
Fytik's host does't allow for fsock, and I will be moving to a new API. There is already caching mechanism's in place for other API services. MCApi uses caching already so I thought I'd hold out on that for a little bit, thanks for the advice I will implement all this now.
Don't use xPaw's, it hardly works anyways.
FunnyItsElmo's has always worked for me, doesn't use fsock, but you may need to experiment with the version depending on the server (1.6 or 1.7/1.8)
And just a word about caching.
I know that most API services will cache data, but for thecannonmc.com to actually send a request (via JS) to mcapi.us, it's actually like loading a whole other website. So if it takes 500 ms for mcapi.us to load and respond, that's an addition 500 ms that your site will take to load, only because their site is being slow.
Look at it like this:
Every single person visiting your site will be requesting mcapi.us which will increase load and bandwidth. Imagine 1000 people on your site - that's a lot of load and bandwidth being used just sending requests to mcapi.us
If you make it so the response from mcapi.us is cached for 1 minute, that means 1 person will request mcapi.us and the other 999 people (for the next 60 seconds) will be instantly loading your cache - from your server - in only a few milliseconds (rather than 500 ms)
Hm, Okay i'll take a look at this.
Yea I understand about asynchronous calls and loading times, the load times was smaller before but they changed something on their end and I can't make cross-origin calls anymore. I will update it.
- Status
