Skip to main content

Quick way to give your Yahoo! Store a speed boost

If you have a customized Yahoo! Store, chances are you are at least somewhat familiar with the “files library” in the store editor. The “files library” (“lib” for short) is an area where you can store files; all kinds of files such as images, css files, JavaScript files, videos, etc. You can access this area from your editor by clicking the “Files” button in your editor toolbar.

Storing files in the “lib” has many advantages over storing files elsewhere (for example on your web hosting server.) The “lib” is measurably faster than web hosting (any file that comes from is hosted on your web hosting account and not in the “files library”.) In addition, all files stored in the “lib” are automatically “gzipped”, meaning they are compressed before sending across the web and decompressed by the browser resulting in a smaller payload – and therefore, faster delivery. But did you know that you can also have your “lib” hosted on a Content Delivery Network (CDN?)

What is a CDN?

A CDN is a network of distributed servers that serve web pages and files based on the geographical location of the user. The idea is that if a visitor lives in New York, for example, and brings up a web page, then if that web page is stored on a server closer to New York then it will “pop up” on the visitor's screen faster than if the same web page was stored on a server in, say, California. Not to mention, that Google can detect if your web site uses a CDN or not, and will assign a different (better) SEO score to your site if it is using a CDN then if it is not.

How can you tell if your “lib” is on a CDN or not?

That's relatively easy. Log into your store editor and in the store manager, look in the far left column of links, under “Edit”. If you see a link there that says “Store Files” (with a “New” icon after it), then your store is already on the CDN. You can stop reading right here :)

How can you have the CDN enabled?

Easy, you just have to ask :) Well, almost. Basically, you have to call Yahoo! Small Business tech support and ask them to switch your file library over to the CDN-based version. The only catch is this: if your store uses any CSS files (and which web site does not?), then you will have to make sure BEFORE the switch-over that none of those CSS files include relative URLs pointing to files in the lib. So the CSS files should have nothing like this:


All such relative URLs should be changed to absolute URLs like


How much speed boost can I expect from this?

That's hard to tell, but probably nothing very dramatic. Unless you have an extremely poorly optimized and/or built store whose pages come up noticeably slowly, then using a CDN to serve up your layout images and external files will most likely not be noticeable for a human. However, it will be noticed by Google... And who doesn't like to make Google feel happy, right?

So go ahead and if you feel up to it, review your CSS files and give your store a quick speed boost. Or, if you'd rather have a professional take care of the whole thing for you, let us know and for a nominal fee we can do this for you. More info here:


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

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

What to expect when your redesign goes live

At Y-Times we roll out new designs, redesigns and other major upgrades to Yahoo stores on a fairly regular basis. Some of the main questions our clients ask are how to prepare for a roll-out and what to expect in terms of SEO and conversions when the changes go live? For any functional Yahoo store how well the site ranks and how well it converts are probably the two most important metrics. Since pretty much ANY change you make to any page can potentially alter either or both of these metrics, merchants may understandably feel nervous about far reaching alterations to their sites. However, when those functionality and design changes and additions are done right, there is really very little to fear. First off, what does it mean for a design or redesign to be "done right?" From the technical stand point, search engines look at the underlying structure of your site (the HTML, and increasingly also the CSS and JavaScript code) to try to extract information and meaning from i