Skip to main content

Top 7 ways to speed up download of your page.

Why is download speed so important?
As we all know nobody wants to wait everybody in this word wants to get everything in flash…so tell me Do you like to wait for pages to download? i do not think so,and if is it so…just go through following zombie steps…..

1. Design your pages with Stylesheet(CSS), not tables


CSS downloads faster than tables because:
Browsers read through tables twice before displaying their contents, once to work out their structure and once to determine their content
Tables appear on the screen all in one go - no part of the table will appear until the entire table is downloaded.
CSS generally requires less code than tables
All code to do with the layout can be placed in an external CSS document, which will be called up just once and then cached (stored) on the user's computer; table layout, stored in each HTML document, must be loaded up each time a new page downloads
With CSS you can control the order items download on to the screen - make the content appear before slow-loading images and your site users will definitely appreciate it …(I dnt abt about others..but I really do.)

2. Don't use images where you only wants to display text


This is where CSS comes into the picture.There is no need to use image where u want only text just use CSS and feel the power. Have a look at this code:

3. Use shorthand CSS properties


Font
Use:
Font: 1em/1.5e, bold italic serif
...instead of
font-size:1em;
line-height:1.5em
font-weight:bold;…etc.
Border
Use:
Border:1px solid #000000;
...instead of
border-width:1px;
border-color:#000;
border-style:solid;
Same things can be applied for background, margin, padding…..

4. Minimise white space and comment tags


Every single letter or space in your HTML code takes up one byte(oh my goshhhhhhhh). It doesn't matter but when considered along with all the spaces it may go higher than expected.

5. Use relative calls rather than absolutes


Try to avoid absolute call ups as they take up more space. An example of an absolute call up is: . Much better would be . But what if some files are in different folders to other ones? Use these shorthand properties:
- Calls up http://www.URL.com
- Calls up http://www.URL.com/filename.html
- Calls up http://www.URL.com/directory/filename.html
- Calls up index.html within that directory
- Calls up index.html one directory above
- Calls up filename.html one directory above
- Calls up index.html two directories above

6. Put CSS and JavaScript into external documents


To place CSS in an external document use:

To place JavaScript in an external document use:

Any external file is called up just once and then cached (stored) on the user's computer. Instead of repeating JavaScript or CSS over and over again in HTML files, just write it out once in an external document.

7. Use / at the end of all links to directory


Don't do this:
http://www.myBlog.com/zombie
Do this instead:
http://www.myBlog.com/zombie
Why? If there's no slash at the end of the URL the server doesn't know if the link is pointing to a file or to a directory. By including the slash the server instantly knows that the URL is pointing to a directory and doesn't need to spend any time trying to work it out…isn’t it amazing…....
I hope this will help u people…as it helped me also…so happy CSSingggggggggg….

Comments

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!