
05-07-2008, 04:04 PM
|
 |
WebProWorld 1,000+ Club
|
|
Join Date: Nov 2006
Location: Steinbach, Manitoba, Canada
Posts: 1,085
|
|
Re: A new site: www.brixhousewine.com
You've obviously worked hard on the site, however there are a few issues which are likely to have a negative effect on your rankings.
- Too much embedded javascript (slows down page loading and increases server load).
- Your meta keywords repeat the word "wine" six times. (That's five times too many.)
- Your meta description well written but too long (Try to keep it under 160 characters).
- Poor use of title text (You're passing up on a great opportunity to use keywords). The words "Home Page" and "Shopping Cart" do nothing for you in terms of rankings in the SERPs. At best, your site name should be at the end of the title if at all.
- The layout is almost entirely graphic based. (Not enough white space, the pages look cluttered).
- Your lacking content and text links (There's very little SE's can index other than alt attributes).
- User account required to check out (lots of users don't like being forced to create an account).
- Your enourmous "featured wines" graphic takes up the entire "above the fold" area of the page.
- Error text which appears after validating form submissions should be a different colour than regular paragraph text.
Quote:
Password length minimum: 5.
Non-alphanumeric characters required: 0.
|
- After form validation, some fields containing errors are marked with red asterisks, others aren't
- Runtime error on submission of shipping details on the following page results in lost cart contents:
https://www.brixhousewine.com/cartshipping.aspx
Quote:
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
|
.02
|