Do not use @import in your CSS files

I will let this article explain it:

 

https://varvy.com/pagespeed/avoid-css-import.html

Geeks, making the world a better place
Quote · 13 Oct 2015

how significant it will be in loading speed? if i am using cache, gzip etc..

did you try it?

 

thanks though..

Always remember that the future comes one day at a time.
Quote · 13 Oct 2015

We could still use tables for layout but that does not mean it is a good idea.  The same for @import, we need to use better coding practices.

Geeks, making the world a better place
Quote · 13 Oct 2015

you can always improve your coding..

if it making a huge improvement then ok Cool. but if it goes by the mili-seconds 

then better keep the old code.

Always remember that the future comes one day at a time.
Quote · 13 Oct 2015

The way the Dolphin template system works, is your custom template first imports a css file from the /templates/base/css directory, and then adds more css after the file is imported.  Any css that is added AFTER the css file is imported, usually replaces the imported css because it is read into the browser at a later time.  This happens for dozens of files.

The end result is, you have quite a few lines of css code that have been read into the browser, but have been negated by css that has been read in at a later time.   All these negated lines of css code can add up to a significant amount of text.

If you do not use import, and combine all the css into your custom templates css files, you can remove the css that will be negated by the css in your custom template, thereby reducing the overall file sizes.  You can't do this if you import files.  Your css files will definitely load faster if you do this, however with Today's internet speeds, you'll probably only gain a small fraction of a second in page load speed that is not enough to be noticed.  I do like the idea of eliminating redundant css though, as it's all more readable in css inspectors like Firebug.

My opinions expressed on this site, in no way represent those of Boonex or Boonex employees.
Quote · 13 Oct 2015

exactly what i mean, today the internet speed is very fast and going faster each year

the browser improving too, the servers improving also. therefore there will be no significant

improvement overall, the average user wont see different in speed.

today you can use cdn such as cloudflare, incpsua etc. to improve speed without doing anything 

Always remember that the future comes one day at a time.
Quote · 13 Oct 2015

 

exactly what i mean

 Don't get me wrong, I wasn't saying it wasn't worth doing.  The de-cluttering aspect alone, makes it worthwhile.  You may not notice a per-page loading speed improvement, but if you reduce css overall size by 10-20kb, and multiply that by the number of page loads your site gets in a month, it can easily add up to several GB of bandwidth.

My opinions expressed on this site, in no way represent those of Boonex or Boonex employees.
Quote · 13 Oct 2015

LOL. Even tho i don't really work for the company anymore, i am still part owner of a ISP that started out with dial-up.

You may find it interesting and kinda funny to know that there are still plenty of rural areas where people cannot get high-speed. My old ISP business still has quite a few dial-up customers.

Kinda sucks really. You would think by now, affordable high-speed would be everywhere, but it's not. You would think satellite would be able to be picked up anywhere, but that's not the case either due to many people being in low valleys surrounded by tree lined mountains.

Does not really matter anyway. Most modern websites no longer reliably load at speeds that low anyway.

https://www.deanbassett.com
Quote · 13 Oct 2015
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.