Skip to main content

Simple trick to speed up your Yahoo! Store pages

If your store uses images or other files stored in the "Files" library, there is an easy trick to improve the response time of those files - and make your pages load faster.

Typically you reference files from the library using this relative URL:

/lib/yourstoreid/filename

where you replace yourstoreid with the Yahoo account ID of your store. This is generally fine, because the Store is smart enough to expand this to the actual location of the file, which is at

http://lib.store.yahoo.net/lib/yourstoreid/filename

What I often see in stores is that the store operator enters things like this:

http://www.yourdomainname.com/lib/yourstoreid/filename

or

http://lib.store.yahoo.com/lib/yourstoreid/filename

What's wrong with that? Well, Yahoo! Store is still smart enough to find the correct file for you, but it doesn't come cheap. What happens is that the Yahoo! Store server does a redirect on these URLs so that they reference the file correctly from the lib.store.yahoo.net server. In a test I've done, these redirects generally took a little over 1,000 milliseconds - or one second. Now imagine if you had 10 or 20 such references in a page? Or inside a css file. It would slow your pages down and completely unnecessarily.

This can be even more pronounced on your checkout pages, where everything is served over an already slower SSL connection (yes, SSL is always slower than regular, unsecure HTTP://), and if you have relative URLs such as /lib/yourstoreid/... in your checkout pages, those will always be redirected. The fix is to use the absolute URL https://lib.store.yahoo.net/lib/yourstoreid/... in your checkout pages, and http://lib.store.yahoo.net/lib/yourstoreid/... on the regular store editor pages. Be sure to do this not only in your HTML source but in all JavaScript and CSS files you use as well.

Comments

Post a Comment

Popular posts from this blog

CPR for a Yahoo Store on Google's Supplemental Index

Recently a client of mine came to me and said that most of his store pages disappeared from Google, and he did not do anything to make this happen. I was a bit skeptical, so I went to Google, did a search on his store, and sure enough, there were only two pages indexed, his home page and his site map (ind.html) page. The rest were in the supplemental results, which means that Google thought the rest of the pages were not much different than these two pages. When I looked at the supplemental results, the little excerpts under each link were exactly the same, and I also noticed that what Google showed under each result was actually text from the ALT tags of the header image. I looked at some of these pages in my client's store, and they were actually different. This was a bit puzzling, but then I thought perhaps Google saw that the header and left navigation was the same throughout the site (which is pretty normal), but that the text that made each page different was too far down ins
Post a Comment
Read more

How to create clean and efficient CSS

In a typical workday, I deal with dozens of yahoo stores and very often I have to tweak, fix, or change CSS used by these stores. While some stores have very clean and easy to follow style sheets or CSS definitions, the vast majority of stores I've seen seem to include complete hack jobs, style sheets put together completely haphazardly, or as an afterthought. While working in such a store, the idea came to me to turn my gripes into a post. So the following is my list of dos and don'ts of good CSS or style design. 1. Externalize your style sheets. This means to save your style sheets into one or more css files, and link to them using the <link rel="stylesheet" type="text/css" href="/lib/yourstoreid/yourstyle.css"> notation, or in Editor V3.0, you can use the LINK operator. 2. Combine your style sheets into as few files as possible. Nothing worse than trying to wade through 6, 8, 10 or more different style sheets to find the color of a l
6 comments
Read more

Smaller is Better

You often hear the phrase "bigger is better". Sometimes it's true but not when it comes to JavaScript or CSS code in your Yahoo! Store pages. If you include JavaScript code or CSS either as linked files (the preferred method) or embedded inside your pages (obviously not preferred), making these files as small as possible should be your goal. Why? This is no rocket science: smaller files mean faster page loads = happy customers. Ok, so what bloats JavaScript code? In general, white space (tabs, carriage returns, non-used spaces), comments, and the actual code, such as variable and function names. You have control over all of these, however, if you don't use white spaces, carriage returns or comments, it will be immensely difficult to understand and modify your code. And not just for others, you too. There are many commercial JavaScript compression tools around, but I've been using this handy and free utility: http://www.andrewkesper.com/jscrush/ This little utilit
1 comment
Read more