[ParaZite]

The speed for Sinisterly is pretty good, but let's make it above outstanding. I ran a speed test with Google and they recommended just a few things that the owner could do to increase the overall page speed. Here they are, I'm going to break em' down and hope that the owner here takes a look and suggests taking the time to boost the speed for everyone here. It can always get better right?

Minify the JavaScript
The following files should be compressed.

Code:

https://www.sinister.ly/jscripts/prototype.js?ver=1603 https://www.sinister.ly/jscripts/general.js?ver=1603 https://www.sinister.ly/mobiquo/smartbanner/appbanner.js http://www.sinister.ly/images/e-red/customjs/fixedmenu.js http://www.sinister.ly/images/e-red/customjs/popup_menu.js

/prototype.js?ver=1603 could save 50.5KiB if compressed.
/general.js?ver=1603 could save 4KiB if compressed.
/appbanner.js could save 3.8KiB if compressed.
/fixedmenu.js could save 1.1KiB
/popup_menu.js could save 991B

Optimize Images
The following forum image can save 20.1KiB (a 37% reduction).

Code:

https://www.sinister.ly/images/e-red/body_bg.png

Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 13.5KiB (15% reduction).

Code:

http://www.sinister.ly/

Minify CSS
Minifying CSS could drastically speed up your forum if you have tons of CSS files that need to be compressed, fortunately this site doesn't. It won't take long to compress the CSS in the following directory routes.

Code:

https://www.sinister.ly/cache/themes/theme16/global.css https://www.sinister.ly/mobiquo/smartbanner/appbanner.css

/theme16/global.css could save 4.2KiB (19% reduction).
/smartbanner/appbanner.css could save 1.1KiB (15% reduction).

Ending Statement
These four rules come straight from Google Insights. Doing the up top requests could drastically increase the page speed to Sinisterly thus making the members have a better experience. The server load can also be reduced by removing unused plugins by deleting them in the /inc/ folder, as well as deleting any other unused folders or files in the FTP server. In my experience on my newest site I can tell you that following what Google told me to do has drastically increased the page speed of my forum and with a little work I drastically reduced the server load by removing unneeded files. Hotlinking should also be prevented in the necessary directories. One more slick trick I know is right in the Avatar function. I've denied direct avatar uploads and require a URL upload instead to limit the amount of images that have to load per page.

Let's speed up the site. It can only get better from here. It won't take that long and it's four very basic rules that every webmaster should get to know. Sinisterly is a FANTASTIC forum and I'm only here to help by giving my personal experiences and the recommendations by professionals.

You're friendly ParaZite.

[Feat]

Even though I don't really understand the technical talk, these are some really nice tips.

[ParaZite]

Even though I don't really understand the technical talk, these are some really nice tips.

Thanks man. Let me break it down for ya' a little. Think of it this way.

When you compress something it makes it smaller. The less things the server has to hold the faster the page speed/lower server load. When you compress certain files in the MyBB installation, the server doesn't have to take in as much information thus making the site quicker.

Good terminology. Hope you understand!

[Oni]

Currently working on the theme. These bits are planned already. Javascript is probably the biggest one.

[ParaZite]

Currently working on the theme. These bits are planned already. Javascript is probably the biggest one.

Glad you know about these rules and are working to get them resolved. Now that this thread has been made and you've replied that you can close me thread if you'd like.

[3SidedSquare]

I feel parazite's explanation was less than sufficient, so I'm going to try one:

If you want to load a web page really fast, make the web page (in html, javascript, images, and what have you) really small. The less data you need to send, the faster the browser will display the image.

Google, for the most part, is suggesting oni replace what's called "Absolute addressing" with "Relative addressing"

Absolute addressing:

Code:

www.sinister.ly/some-thread-name

Relative addressing:

Code:

/some-thread-name

Since your browser knows you're already on Sinister.ly, it knows there to go when you tell it
/some-thred-name
So for every link on the page that uses absolute addressing, you can save 22 characters of data you're sending over when you don't have to.

Additionally, you can use trick like taking out "new line" characters and spaces in any html or javascript you have, since the browser ignores them anyway, they just make the code a little easier to read.

I'm sure there are more tricks to reducing size that I don't know of, perhaps someone more knowledgeable could elaborate.

[ParaZite]

I feel parazite's explanation was less than sufficient, so I'm going to try one:

If you want to load a web page really fast, make the web page (in html, javascript, images, and what have you) really small. The less data you need to send, the faster the browser will display the image.

Google, for the most part, is suggesting oni replace what's called "Absolute addressing" with "Relative addressing"

Absolute addressing:

Code:

www.sinister.ly/some-thread-name

Relative addressing:

Code:

/some-thread-name

Since your browser knows you're already on Sinister.ly, it knows there to go when you tell it
/some-thred-name
So for every link on the page that uses absolute addressing, you can save 22 characters of data you're sending over when you don't have to.

Additionally, you can use trick like taking out "new line" characters and spaces in any html or javascript you have, since the browser ignores them anyway, they just make the code a little easier to read.

I'm sure there are more tricks to reducing size that I don't know of, perhaps someone more knowledgeable could elaborate.

Certainly my thread is only a basic guide to increasing the speed of the forum. There are tons of ways to reduce your server load thus making your website faster, but I have not included every single one.

I've provided just a few rules that come from Google which indeed are helpful from my own experiences. I've provided a few because I know Oni is busy with other things on the site and don't want to overwhelm him with a huge list. Thanks for your input, my friend.

If there are any other ways you can add that will benefit the page speed of this forum I'd love for you to include as many as you can in one single posting, that way Oni can work his way down and cover them all if he chooses.

[Cake]

Minifying the CSS wouldn't make a drastic improvement, just saying.

[ParaZite]

Minifying the CSS wouldn't make a drastic improvement, just saying.

But following the whole entire thread could make a drastic improvement, and really depending on how much CSS a site has depends on how much of a difference compressing it all would make.

[Lain]

Currently working on the theme. These bits are planned already. Javascript is probably the biggest one.

Google Pagespeed does all of the above and more, automatically.