Hi Guys, this is a site we have completed for a bathroom showroom. The client wanted a simple site with shopping cart. The shopping cart part of the site is not ready to go online yet as it is quite extensive but the client wanted the site online as soon as possible, hence the missing shopping components. The site was created in adobe muse, the shopping cart will be ecwid.

http://www.mobilecountrybathrooms.co.uk/

It's a nice looking site. Good Job!

Something odd is happening as I reduce the browser window width. The login icon goes big and black then the nav menu disappears. Is there meant to be a hamburger menu ? I don't get one.

 

I would love to hear how you get on with ecwid

 

TW

Thank you for spotting that TW, I'll get right on to it, can't believe I didn't spot that and the hamburger menu is indeed to appear there. Thank's for the comments.

 

 

Something odd is happening as I reduce the browser window width. The login icon goes big and black then the nav menu disappears. Is there meant to be a hamburger menu ? I don't get one.

 

Ok, that's fixed now, it was a rogue element. Thanks again TW for pointing that out.

Why the huuuuge image on the homepage?

 

Why the invitation to shop online?

 

The homepage should be the shop.

 

Other pages serve little purpose. For example: http://www.mobilecountrybathrooms.co.uk/bathroom-gallery.html. There are no captions, no prices, no links to the product pages. and you have an 'exclusive' page that has a totally different gallery set up. Most confusing.

 

The current CTA on the homepage (arrange a homevisit) is way down the page and just takes me to a contact page and all I see is a map.

 

So while the site looks OK, it doesn't really do anything. If the shop is some way off I'd remove all references to it from the site.

 

The site sort of looks like the layout was developed before any thought was given to the content. Which is always the wrong way round to do things.

 

And why 'mobilecountrybathrooms'? What's 'mobile' about the business?

Edited March 21, 201610 yr by fisicx

Fisicx, all valid points but as I said the site is going to be about the shop but just not now, the client wanted the site online straight away while they go about adding the products, not an ideal but the client has the right to do what they want. The gallery will be before and after pictures, again this is being updated by the client. its mobile because they can bring the showroom (or at least a part of it) to their customers.

 

 

You also seem to be including //netdna.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.min.css 6 times in your head

 

A limitation of adobe muse unfortunately, one of it's weaknesses is the code it generates.

Its mobile because they can bring the showroom (or at least a part of it) to their customers.

That's not at all clear on the website. The only thing it appears to be is a shop for bathroom products. And there is no shop.

 

 

 

A limitation of adobe muse unfortunately, one of it's weaknesses is the code it generates.

So why use adobe muse? The code is horrible.

 

As I said, this is a design led website which means it looks pretty but delivers nothing. Neither gallery add any value. There are no details of this mobile showroom, there is no obvious way to arrange a home visit other than fill in a form. Which doesn't even make it clear it's a local service. Can they come an see me in Hampshire?

 

This isn't moaning at you. It's pointing the finger at the client who is going to end up with a site that doesn't convert. Which isn't your fault but you may well get the blame.

There are no details of this mobile showroom,

 

They would be here

 

http://www.mobilecountrybathrooms.co.uk/bathrooms-bradford.html

 

However it isn't clear as it is reached from the About button in the menu.

That's why I couldn't find it. And even on that page it's hidden way down below the fold. All I see on the page is a huuuuuge image and the words: Premier Bathroom Supplies in Bradford.

 

And I've just spotted all sorts of SEO issues. One of which is 8 H1s on the page

Overall the design is really quite nice. Uncluttered, modern look.

 

Take on board some of the points made here and it should be OK. The one point I would make is to learn to code these things for yourself as the code generated by Muse is poor. It shouldn't require 400KB of CSS to render each page.

Overall the design is really quite nice. Uncluttered, modern look.

I agree, it does look nice. But looking nice doesn't convert. What converts is the right content on the right pages in the right order. BUt it seems that the client has focussed on the layour rather than what they want the site to acheive.

 

If their USP is the mobile showroom then that's what should be on the homepage along with their contact details. Put the phone number in the header, in the footer and on in the content. Instead of the 'Arrange a home visit' button put the contact form on the page. And test putting the navigation on the left below the logo - tests show this generates far more clicks than putting it on the right.

It won't convert if it looks like a pile of dog **** either.

No, but a simple layout can convert really well. The choice of font and good use of whitespace can have a bigger influence on conversions than all sorts of fancy features.

 

On the site under review for example there is a huge image on the homepage. It's doesn't add any value other than looking pretty. Someone landing on the site will scan the area on the screen and wonder what they are supposed to do next. But if you made the image smaller you could get some useful content above the fold to guide the visitor as to what to do next.

No, but a simple layout can convert really well. The choice of font and good use of whitespace can have a bigger influence on conversions than all sorts of fancy features.

 

On the site under review for example there is a huge image on the homepage. It's doesn't add any value other than looking pretty. Someone landing on the site will scan the area on the screen and wonder what they are supposed to do next. But if you made the image smaller you could get some useful content above the fold to guide the visitor as to what to do next.

 

Which is why I also posted

 

Take on board some of the points made here ...

 

There seemed little point reiterating them.

 

Do you read the last line of posts?

 

Filler line to ensure the last line is read.

Do you read the last line of posts?

Yes I do. Apologies if you thought I was just posting the same stuff again. The more I look at the site the more issues I'm discovering.

And I've just spotted all sorts of SEO issues. One of which is 8 H1s on the page

 

Multiple H1s is not a problem in HTML5 (if they are nested corectly) They are actually recomended for groups of content on a page.

H1 elements nested one "level" down will be interpreted as H2 elements. However the nesting should probably be in article or section elements rather than divs.

http://webdesign.tutsplus.com/articles/the-truth-about-multiple-h1-tags-in-the-html5-era--webdesign-16824

Interesting article. But the page isn't structured or nested, they are just repeating the same two phrases in different blocks. It's the same on most pages. They don't need to be an H1 on any of them as they are just being used as a tagline. What they should have is all the ducks lined up so Google can tick all the boxes. Because their is no connection between the key indexing elements on the page Google is left wondering what's going on.

All points made here will be taken on board, but do remember that the site has gone live unfinished (as I said in the op), I am aware of the problems as is the client but it was important for the client to have the site live as soon as possible (for their own reasons). At the end of the day if the client is happy for it to go live then there is nothing a designer can do, no matter what one's personal views. I didn't realise that there were more than one h1 tag in a page and that will certainly be fixed soon.

 

Rallport, I have not implemented any feature, if you had used muse you would know that the site is designed and the code is output by muse, short of going in and changing the code everytime a change is made to the site, either by myself or the client, there is nothing that can be done, the code is republished in it's entirety by muse every single time. The same applies to any widgets used (in this case a fontawsome one).