<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.websitemagazine.com/content/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>'Net Features : sem, servers, search engines</title><link>http://www.websitemagazine.com/content/blogs/posts/archive/tags/sem/servers/search+engines/default.aspx</link><description>Tags: sem, servers, search engines</description><dc:language>en</dc:language><generator>CommunityServer 2008 SP2 (Build: 31104.93)</generator><item><title>SE Ranking Problem - Slow Server</title><link>http://www.websitemagazine.com/content/blogs/posts/archive/2008/02/13/SE-Ranking-Problem-Slow-Server.aspx</link><pubDate>Wed, 13 Feb 2008 16:49:00 GMT</pubDate><guid isPermaLink="false">1e469e21-c924-44fa-a132-47b5d0a8ad47:4440</guid><dc:creator>Administrator</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.websitemagazine.com/content/blogs/posts/rsscomments.aspx?PostID=4440</wfw:commentRss><comments>http://www.websitemagazine.com/content/blogs/posts/archive/2008/02/13/SE-Ranking-Problem-Slow-Server.aspx#comments</comments><description>&lt;p&gt;I received a note from a reader yesterday afternoon inquiring about why her 
site was not ranking. As you can imagine we receive many emails like this each 
day and periodically I like to look under the hood an see what&amp;#39;s going on. As 
you can imagine, not ranking (at least anywhere notable) is a common problem so 
several posts this week will address the issue of why your site may not be 
ranking well. &lt;/p&gt;
&lt;p&gt;The result for this website? All in all it was a complete disaster. The code 
was chock full of third party javascript (&lt;i&gt;thanks widget trend&lt;/i&gt;) and 
iframes, there was little proprietary content on the site itself, the meta 
information was a mess, and it had no inbound links.&amp;nbsp; We&amp;#39;ll discuss those 
issues later but what stood out the most for this site (at least to me) was that 
the site loaded too slow. Is that a problem? You bet. Here&amp;#39;s why. &lt;/p&gt;
&lt;p&gt;While search engines are not going to penalize sites that are on a slow 
server, there are indirect consequences. When search engine spiders notice that 
a site is unable to handle their request for information, they will simply leave 
and go elsewhere. The indirect consequence is that the slow loading site will 
not be completely crawled and will have fewer pages in the search engine 
indices.&lt;/p&gt;
&lt;p&gt;I encourage all WM readers to test the performance of their websites (and web 
pages), mainly in terms of load times. InternetSupervision.com (a Website 
Magazine advertiser) has a helpful resource to &lt;b&gt;
&lt;a href="http://internetsupervision.com/"&gt;check the performance and load time of 
websites&lt;/a&gt;&lt;/b&gt;. &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://www.websitemagazine.com/content/aggbug.aspx?PostID=4440" width="1" height="1"&gt;</description><category domain="http://www.websitemagazine.com/content/blogs/posts/archive/tags/seo/default.aspx">seo</category><category domain="http://www.websitemagazine.com/content/blogs/posts/archive/tags/sem/default.aspx">sem</category><category domain="http://www.websitemagazine.com/content/blogs/posts/archive/tags/search+engines/default.aspx">search engines</category><category domain="http://www.websitemagazine.com/content/blogs/posts/archive/tags/servers/default.aspx">servers</category></item></channel></rss>