Welcome to the Q&A Forum

That was my first instinct as well - but I wanted to check if there was a better move? Thanks for your help!

I am in the US (North Carolina), my name is Dutch though... Always good discussion, and I don't think either one is right or wrong here.

Haven't used it myself but there are definite benefit - http://googlecode.blogspot.com.au/2010/11/make-your-websites-run-faster.html

Well I think it's correct what both SirMax and Jose Garcia Jr say, web 2.0 was an incredible change in the that way eaverybody could use the web and interact in it. Actually everybody can open a new blog for free, can write on the other blogs, can interact with friends in the social network thanks to web 2.0 social view. Before this, websites were only static paper-like advertising posters with no interaction possibilities. I can't say if this change drove to a new graphic style or if a new graphic style helped us to change, now the web 2.0 style, made by gradients, glossy buttons, and icons as J.G Jr said is a standard. Obviously web 2.0 style doesn't mean automatically web 2.0 intercatcion, it could be good for some tasks, less for others, it depends on what your website's made for.

Yes, there are plenty of sites like that. Here are some that I recommend: https://www.awwwards.com is a great one. You can also get lots of great inspiration on there for your own designs. http://www.cssdesignawards.com/ is another good one.

Page content is a same as old index.html. How about those 70 links to inner pages?

Hi Naghirniac, This is a very general question.  As far as a limit the answer would have to be no, there is no limit.  However, what is going on here?  Are you rebuilding a very large website and attempting to consolidate pages?  Be sure you are pointing old URLs to pages that are very relevant to the old content or you will surely see rankings fall for those pages.  Also, do the old URLs have lots of backlinks?  You may consider contacting the webmasters of the websites that link to your old pages and told of the change so they can update their links to point to the new pages, at least for the more important links – the 301’s will pass most of the juice, but not all. Hope this helps, Vizergy

W3C feedback - Validation Output: 7 Errors [image: error.png] Line 12, Column 125: Attribute xmlns:fb not allowed here.``` <code class="input">….facebook.com/2008/fbml" xmlns:addthis="http://www.addthis.com/help/api-spec" ></code> [✉](http://validator.w3.org/feedback.html?uri=http%3A%2F%2Fwww.homecinemauk.com%2F;errmsg_id=html5#errormsg "Suggest improvements on this error message through our feedback channels") [image: warning.png] Line 12, Column 125: Attribute with the local name xmlns:fb is not serializable as XML 1.0.``` <code class="input">….facebook.com/2008/fbml" xmlns:addthis="http://www.addthis.com/help/api-spec" ></code> [✉](http://validator.w3.org/feedback.html?uri=http%3A%2F%2Fwww.homecinemauk.com%2F;errmsg_id=html5#errormsg "Suggest improvements on this error message through our feedback channels") [image: error.png] Line 12, Column 125: Attribute xmlns:addthis not allowed here.``` <code class="input">….facebook.com/2008/fbml" xmlns:addthis="http://www.addthis.com/help/api-spec" ></code> [✉](http://validator.w3.org/feedback.html?uri=http%3A%2F%2Fwww.homecinemauk.com%2F;errmsg_id=html5#errormsg "Suggest improvements on this error message through our feedback channels") [image: warning.png] Line 12, Column 125: Attribute with the local name xmlns:addthis is not serializable as XML 1.0.``` <code class="input">….facebook.com/2008/fbml" xmlns:addthis="http://www.addthis.com/help/api-spec" ></code> [✉](http://validator.w3.org/feedback.html?uri=http%3A%2F%2Fwww.homecinemauk.com%2F;errmsg_id=html5#errormsg "Suggest improvements on this error message through our feedback channels") [image: warning.png] Line 109, Column 382: Attribute addthis:url is not serializable as XML 1.0.``` <code class="input">…homecinemauk.com/' addthis:title=' ' ><a class="addthis_button_facebook_like" …<="" code=""></a></code> <a class="addthis_button_facebook_like" …<="" code=""></a>[✉](http://validator.w3.org/feedback.html?uri=http%3A%2F%2Fwww.homecinemauk.com%2F;errmsg_id=html5#errormsg "Suggest improvements on this error message through our feedback channels")` `* [image: warning.png] Line 109, Column 382: Attribute addthis:title is not serializable as XML 1.0.``` <code class="input">…homecinemauk.com/' addthis:title=' ' ><a class="addthis_button_facebook_like" …<="" code=""></a></code> ````<a class="addthis_button_facebook_like" …<="" code=""></a> <a class="addthis_button_facebook_like" …<="" code=""></a>[✉](http://validator.w3.org/feedback.html?uri=http%3A%2F%2Fwww.homecinemauk.com%2F;errmsg_id=html5#errormsg "Suggest improvements on this error message through our feedback channels")` `*  _Line 109, Column 382_: Attribute addthis:url not allowed on element div at this point.``` <code class="input">…homecinemauk.com/' addthis:title=' ' **>**<a class="addthis_button_facebook_like" …<="" code=""></a></code> ````<a class="addthis_button_facebook_like" …<="" code=""></a><a class="addthis_button_facebook_like" …<="" code=""></a> <dl><a class="addthis_button_facebook_like" …<="" code=""></a> <dt><a class="addthis_button_facebook_like" …<="" code="">Attributes for element </a>[`div`](http://dev.w3.org/html5/spec-author-view/#the-div-element):</dt> <dd>[Global attributes](http://dev.w3.org/html5/spec-author-view/#global-attributes)</dd> </dl>` `*  _Line 109, Column 382_: Attribute addthis:title not allowed on element div at this point.``` <code class="input">…homecinemauk.com/' addthis:title=' ' **>**<a class="addthis_button_facebook_like" …<="" code=""></a></code> ````<a class="addthis_button_facebook_like" …<="" code=""></a><a class="addthis_button_facebook_like" …<="" code=""></a> <dl><a class="addthis_button_facebook_like" …<="" code=""></a> <dt><a class="addthis_button_facebook_like" …<="" code="">Attributes for element </a>[`div`](http://dev.w3.org/html5/spec-author-view/#the-div-element):</dt> <dd>[Global attributes](http://dev.w3.org/html5/spec-author-view/#global-attributes)</dd> </dl>` `*  _Line 109, Column 452_: Attribute fb:like:layout is not serializable as XML 1.0.``` <code class="input">…ok_like" fb:like:layout="button_count"**>**<a class="addthis_button_tweet"></a></code> ````<a class="addthis_button_tweet"></a> <a class="addthis_button_tweet"></a>[✉](http://validator.w3.org/feedback.html?uri=http%3A%2F%2Fwww.homecinemauk.com%2F;errmsg_id=html5#errormsg "Suggest improvements on this error message through our feedback channels")` `*  _Line 109, Column 452_: Attribute fb:like:layout not allowed on element a at this point.``` <code class="input">…ok_like" fb:like:layout="button_count"**>**<a class="addthis_button_tweet"></a></code> ````<a class="addthis_button_tweet"></a><a class="addthis_button_tweet"></a> <dl><a class="addthis_button_tweet"></a> <dt><a class="addthis_button_tweet">Attributes for element </a>[`a`](http://dev.w3.org/html5/spec-author-view/#the-a-element):</dt> <dd>[Global attributes](http://dev.w3.org/html5/spec-author-view/#global-attributes)</dd> <dd>`[href](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-href)`</dd> <dd>`[target](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-target)`</dd> <dd>`[rel](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-rel)`</dd> <dd>`[media](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-media)`</dd> <dd>`[hreflang](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-hreflang)`</dd> <dd>`[type](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-type)`</dd> </dl>` `*  _Line 109, Column 557_: Attribute g:plusone:size is not serializable as XML 1.0.``` <code class="input">…oogle_plusone" g:plusone:size="medium"**>**<a class="addthis_counter addthis_p…</code></pre> <p class=" helpwanted"=""></a>[✉](http://validator.w3.org/feedback.html?uri=http%3A%2F%2Fwww.homecinemauk.com%2F;errmsg_id=html5#errormsg "Suggest improvements on this error message through our feedback channels")</code> ````*  _Line 109, Column 557_: Attribute g:plusone:size not allowed on element a at this point.``` <code class="input">…oogle_plusone" g:plusone:size="medium"**>**<a class="addthis_counter addthis_p…</code></pre> <div class=" ve="" html5"=""></a> <dl><a class="addthis_counter addthis_p…</code></pre> <div class=" ve="" html5"=""></a> <dt><a class="addthis_counter addthis_p…</code>Attributes for element </pre> <div class=" ve="" html5"=""></a>[`a`](http://dev.w3.org/html5/spec-author-view/#the-a-element):</dt> <dd>[Global attributes](http://dev.w3.org/html5/spec-author-view/#global-attributes)</dd> <dd>`[href](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-href)`</dd> <dd>`[target](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-target)`</dd> <dd>`[rel](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-rel)`</dd> <dd>`[media](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-media)`</dd> <dd>`[hreflang](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-hreflang)`</dd> <dd>`[type](http://dev.w3.org/html5/spec-author-view/#attr-hyperlink-type)`</dd> </dl></code> `````````` ## Analysis and Recommendations * TOTAL_HTML - Congratulations, the total number of HTML files on this page (including the main HTML file) is 1 which most browsers can multithread. Minimizing HTTP requests is key for web site optimization. Y * TOTAL_OBJECTS - Caution. You have 20 total objects on this page. From 12 to 20 objects per page, the latency due to object overhead makes up from 75% to 80% of the delay of the average web page. See Figure II-3: [Relative distribution of latency components showing that object overhead dominates web page latency](http://www.websiteoptimization.com/secrets/performance/II-3-object-overhead.html) in [Website Optimization Secrets](http://www.websiteoptimization.com/secrets/) for more details. Consider reducing, eliminating, and combining external objects (graphics, CSS, JavaScript, iFrames and XHTML) to reduce the total number of objects, and thus separate HTTP requests. Consider using [CSS sprites](http://www.websiteoptimization.com/speed/tweak/css-sprites/) to help consolidate decorative images. * TOTAL_IMAGES - Caution. You have a moderate amount of images on this page (14 ). Consider using fewer images on the site or try reusing the same image in multiple pages to take advantage of caching. Using CSS techniques such as colored backgrounds, borders, or spacing instead of graphic techniques can help reduce HTTP requests. * TOTAL_SIZE - Warning! The total size of this page is 315393 bytes, which will load in 66.86 seconds on a 56Kbps modem. Consider reducing total page size to less than 100K to achieve sub 20 second response times on 56K connections. Pages over 100K exceed most attention thresholds at 56Kbps, even with feedback. Consider optimizing your site with [Website Optimization Secrets](http://www.websiteoptimization.com/secrets/), [_Speed Up Your Site_](http://www.websiteoptimization.com/speed/) or [contacting us](http://www.websiteoptimization.com/contact/) about our optimization services. * TOTAL_SCRIPT - Caution. The total number of external script files on this page is 5 , consider reducing this to one or two. Combine, refactor, and minify to [optimize your JavaScript](http://www.websiteoptimization.com/speed/tweak/javascript-optimization/) files. Ideally you should have one (or even embed scripts for high-traffic pages) on your pages. Consider [suturing JavaScript files together](http://www.websiteoptimization.com/speed/tweak/suture/) at the server to minimize HTTP requests. Placing external JavaScript files at the bottom of your BODY, and CSS files in the HEAD enables progressive display in XHTML web pages. * HTML_SIZE - Congratulations, the total size of this HTML file is 12545 bytes, which less than 50K. Assuming that you specify the HEIGHT and WIDTH of your images, this size allows your HTML to display content in under 10 seconds, the average time users are willing to wait for a page to display without feedback. * IMAGES_SIZE - Warning! The total size of your images is 207700 bytes, which is over 100K. Consider [switch graphic formats](http://www.websiteoptimization.com/speed/tweak/graphic-optimization/%3Eoptimizing%20images%3C/a%3E%20for%20size,%20combining%20them,%20and%20replacing%20graphic%20rollovers%20with%20CSS.%20You%20can%20often%20%3Ca%20href=) to achive smaller file sizes (from JPEG to PNG for example). Finally, substitute CSS techniques for graphics techniques to create colored borders, backgrounds, and spacing. * SCRIPT_SIZE - Warning! The total size of external your scripts is 95148 bytes, which is over 20K. Consider [optimizing your JavaScript](http://www.websiteoptimization.com/speed/tweak/javascript-optimization/) for size, combining them, and using [HTTP compression](http://www.websiteoptimization.com/speed/tweak/compress/) where appropriate for any scripts placed in the HEAD of your documents. You can substitute [CSS menus](http://www.websiteoptimization.com/speed/tweak/cssmenus/) for JavaScript-based menus to minimize or even eliminate the use of JavaScript. * MULTIM_SIZE - Congratulations, the total size of all your external multimedia files is 0 bytes, which is less than 10K. Firebug on Firefox Yahoo: See attached image Google: See attached Image [OdPjx.png](http://i.imgur.com/OdPjx.png) [VRW71.png](http://i.imgur.com/VRW71.png)```

Did you tried at http://codecanyon.net/. There you will found tousands of good codes with several types of sliders. I hope it can help you...

I have looked at Firstserv but there are no prices. 1 and 1 has been recommended to me Keri, but the trouble with 1 & 1 is, a lot of joomla people do not seem to like them although the tech guy does, but when i researched them, they got a lot of negative feedback. On a cost point of view there dedicated servers are a good price but because i am not technical when it comes to sorting out databases it would cost me more in the long run. I have also looked at 123 reg, Tsohost, go daddy, and united offer less memory etc for much more than i am paying at the moment. The sites have been put there for the time being so they can be worked on in the near future, none of the sites will be similar, they are just there at the moment, waiting to be worked on. I am seriously thinking because i cannot find a suitable hosting company to spend a few thousand pounds on having my own server at our office and then employ someone so many hours a week as this seems the better option.

Thank you Robert..more clear now

Hi John, I have taken a look at your site and believe that you are doing the structure right. Many people will say that you should not have a parent page however I tend to disagree. In WordPress "Siloing" works very well. So to answer your question, do not mix up your pages and articles (posts), your pages must be siloed (eg www.greensidelawncare.com/lawn-tips/turf-weed-help) however your POSTS (blog) do not have to silo (eg: www.greensidelawncare.com/name-of-article-1) Structure: Lawn Care (links to www.greensidelawncare.com/lawn-care) (page) Grass Diseases (links to www.greensidelawncare.com/lawn-tips/grass-dieases) (page) Turf Weeds Help (links to www.greensidelawncare.com/lawn-tips/turf-weed-help) (page) Selecting Grass Types (links to www.greensidelawncare.com/lawn-tips/selecting-grass-types) (page) Lawn Tips (links to www.greensidelawncare.com/lawn-tips) (main blog page) Article 1 (links to www.greensidelawncare.com/name-of-article-1) (blog article) Article 2 (links to www.greensidelawncare.com/name-of-article-1) (blog article) -  Article 3 (links to www.greensidelawncare.com/name-of-article-1) (blog article) Landscaping (links to www.greensidelawncare.com/landscaping/) (page) idea (links to www.greensidelawncare.com/landscaping/child-1) (page) idea (links to www.greensidelawncare.com/landscaping/child-2) (page) idea. (links to www.greensidelawncare.com/landscaping/child-3) (page) Side note: I suggest that on your blog page greensidelawncare.com/lawn-tips/ that you do not show the full post for each article, make sure that it only shows the excerpt (just a small summary linking through to the full article) in the main blog feed or you may have duplicate content issues.

When the big update came through a little over two years ago about page speed, I was working on a site with load time issues. I did see quite the drop in organic referrals from Google after that update was pushed, while organic referrals from Bing and Yahoo continued to increase. I was working in-house at the time, so I don't have a lot of other sites to judge at that time, but I did see distinct change in that one site. I also agree with you that load time affects users and their browsing and conversion behavior. And even though "everybody has broadband" there are a lot of people on poor public (or conference) wifi connections or on their phones, and pagespeed is quite important to them.

I will give a try...thanks

Wow Perfect Marcin, thank you.

(2) is a calculated risk. Yes, you'll knock the deeper pages out of contention for ranking, but they're low-value pages (in Google's eyes) and near-duplicates. So, you should boost the rnaking ability of the main Armani brand page. Net-net, I think you'll gain branded searches. Truthfully, though, 15 brands X 8 pages isn't a ton. You may be having ranking issues beyond this. It is common for these pages to do poorly, as they're search results and tend to use copy that's used across the web (since many people sell the same brands). There's a lot of competition.