back to Completed Reviews

Site Name: RReliant
Owner: Michael
Reviewed by: Georgina
Reviewed on: 2nd January 2010

Previous reviews:

Rettro

Site Name

It’s alright and easy to remember. It’s better than your old site name, because your old site name had “retro” – which was just too common.

Coding and Validation

I’m having problems checking your HTML validation with the validator but upon checking it manually your coding is fine.

Your CSS has 1 error and 8 warnings in CSS3. There’s a lot of styling being embedded as most of it comes from your plugins. On the calendar.css stylesheet, color: 4060ff should be color: #4060ff.

Browser Compatibility & Usability

Your site is navigable and functions in Firefox, Safari, Opera and Internet Explorer, however there is a problem with your titles. The WordPress plugin you are using does not work in Opera (the font does not appear) and Internet Explorer (all titles appear as “XXX” and there is a Javascript error). I suggest using the TTF Titles plugin.

The navigation is clear but I think you could make the text a bit bigger so it isn’t knocked off by the bold header image. The text is fairly easy to read but I think the main text could do without the shadow.

Layout

I see you’ve changed the header and footer and replaced them with newer images. These look a lot better than the text and what you had before. I’m not really liking the image in the footer being the same as the header image though. It should be simple and less bold – maybe reduced in opacity or as a light grey. Something more subtle.

The tagline isn’t really my thing… “The free download and tutorial site” applies to quite a lot of sites out there; it’s not hugely special.

I like your use of bright colours in this layout. You use bright colours a lot but I don’t think you have used dark greys as part of the background before. They look much better on a darker background than the white backgrounds you have previously used.

Overall it’s not a bad layout and you’ve done well with the choice of hues and background. I think the bold white lines under the navigation and above the footer could go, though.

Content

In the sidebar there are some mistakes:
RReliant.com; should be RReliant.com,
weeks should be week’s
of only should be for only.

About

On the main page there are some mistakes:
you’re hearts should be your heart’s
please do read should be please read
contact the site should be contact the owner.

I don’t think it’s necessary to use “our” when you are the only owner of the site; you should use “my”.

Additionally, in the “History” section of the sidebar:

The site was first purchased as a web-hosting site, however I decided to change it to a resource and tutorial site, however there is still hosting available to purchase.

You’ve used “however” twice in this sentence. It would more correct to say:

The site was first purchased as a web-hosting site and I decided to change it to a resource and tutorial site. However there is still hosting available to purchase.

“Affie application” should really be “Affiliate application”. Affie is not a word.
Dont should be Don’t.

I’m not sure if it was intended but your contact form page does not have a sidebar. Also, under “your choose” (which should be “your choice” or “you choose”), the options don’t make sense.

It might be useful to include an email address in case people prefer to send an email or if the contact form is not functioning.

On your credits page don’t forget to credit sites like your host or any programs you have used.

There’s only one link button – it would save some space if you perhaps put it on the main “about” page.

On the owner page you have a few mistakes:
white half Irish and half British should be white, half-Irish and half-British
i’m not should be I’m not
school, next should be school; next
collage should be college
phycology should be psychology
Shows and should be My favourite shows and
dont should be don’t.

There’s not much on the Skype page; why not put this on the main page or the owner page? I don’t think it looks good to have so many pages when a lot of them just have a few lines of text on them.

Visitor

I see you are attempting to use semicolons in your writing, but you’re using them incorrectly:

Welcome to RReliant’s visitor section, here we provide a large amount of free resources and downloads for you to use; all located to the right.

A semicolon can be used between two independent clauses. This means that you should use a semicolon when you can split the sentence into two separate sentences. Therefore this is correct:

Welcome to RReliant’s visitor section; here we provide a large amount of free resources and downloads for you to use, all located to the right.

You use both “our” and “my” on this page – stick with one! You’re the only owner; there’s nothing to be ashamed of.

On the visitor pages, “Right-Click” is for a right-handed mouse. It would be left-click on a left-handed mouse, so it would be nice to make note of this. These instructions should also be at the top of the page, not at the bottom after all the content.

The brushes page is under construction. You should not have displayed it until it was up!

I think I mentioned this in your other review, but the button bases aren’t really useful – people usually make their own.

Nothing much to say about the layout templates, but the last one definitely needs more padding on the edges because the text is squished.

The emoticons are good!

The icon bases are okay. Just Framless should be Just Frameless.

The icon textures and the polaroids are okay – do make sure that if you make any more of these, you credit the right person at their exact URL (ie. the user on DeviantArt, not just “DeviantArt”).

On the premade layouts page, themes, are should be themes are and version, if should be version; if.

I mentioned this in your last review; the pink on the final layout is much too bright. The layout with the swirls is quite interesting but the links are much too small.

This pink and grey theme is rather interesting in structure. I think the site name and navigation text could be made bigger though. It’s also hard to see the text on the blue layout because of the stripes. You seem to be a fan of tiny navigation – that’s not the way to go.

On the textures page, site, I should be site; I, and full-screen view should be full view.

The user bars are okay.

On your article you have a number of mistakes:
then knew should be the new
its good should be it’s good

Actually, Juno doesn’t discuss the advantages of being a teenage mother. It documents the girl’s pain and the relationships she develops with her friends and family throughout her pregnancy. If you haven’t seen the movie I suggest you don’t make claims about it.

I knew it should be I know it
venerable should be vulnerable
girls story’s should be girl stories
true life story’s should be true life stories
her self should be herself
there own should be their own
there latest should be their latest
there smashing should be their smashing
there children should be their children.
This is a pretty good article but you need to fix up the spelling and grammatical errors.

Tutorials

On the main page:
Tutorial Categories should be tutorial categories
individual requests just should be individual requests; just
free to use, if should be free to use; if.

I’d personally prefer if the tutorials weren’t categorised so I could see them all at a glance on the one page, but it works with your site so I guess that’s okay.

On the cPanel tutorial for creating subdomains:
you’re FTP should be your FTP
you’re new sub-domain should be your new sub-domain
create you’re FTP should be create your FTP.

5000MB is actually a lot of quota; some websites don’t even offer more than 200MB of quota for one website.

On the blockquote tutorial, CSS, you should be CSS; you and instead of saying “Contact the site”, say “contact me”.

On the textarea tutorial, CSS, feel should be CSS; feel.

On the external stylesheet tutorial, you have a few mistakes:
When i should be When I
stylesheet’s; meaning should be stylesheets, meaning
Its a single should be It’s a single
main dictionary should be main directory.
And no, an external stylesheet is not a “single link code”. It is a stylesheet that is not embedded into the HTML of a page but rather as a separate document. You shouldn’t be writing this tutorial with the wrong definition.

On the bubble texture tutorial:
This tutorial going should be This tutorial will
800×800 should be 800×800 pixels
laer should be layer
your done should be you’re done.

On the scratch texture tutorial:
photo shop should be Photoshop
there really useful should be they’re really useful
paint shop pro should be Paint Shop Pro
800 x 800 document should be document, 800×800 pixels in size.

On the main WordPress tutorial page, Installing-plugins should be Installing plugins.

On the Akismet tutorial:
plugin, is should be plugin is
by click the activate should be by clicking “Activate”
key, should be key.
were it should be where it.

The tutorial for “custom number of posts” is not very useful. It’s something as simple as changing a setting; you don’t need a tutorial for it.

On the calendar tutorial:
sidebars, it displays should be sidebars; they display
on what days should be on the days
blog enter should be blog entry
i recommend should be I recommend
stlye.css should be style.css
your done should be you’re done.

On the installing plugins tutorial:
quiet easy should be quite easy
want download should be want, download
firefox should be Firefox
done, you should be done; you.

On the “installing WordPress” tutorial:
wordpress can be quiet should be WordPress can be quite
realy should be really
First Go should be First, go
root dictionary should be root directory
in the second option should be using the second option
strait should be straight
belive should be believe
your done should be you’re done.

On the BellaBuzz tutorial:
intergrate should be integrate
yourbellabuzz should be your Bellabuzz
replace it with should be paste it in place of
code i should be code I
the bellabuzz should be the BellaBuzz
what you want i named mine should be what you want. I named mine
ask-me should be “ask-me”
main dictionary should be main directory
your done should be you’re done.

I honestly don’t know why you are writing “main dictionary”. I think you actually need a dictionary seeing as you don’t seem to understand the meaning of “dictionary” or even use the correct word in this context.

On the tutorial on “making PHP pages work with WordPress”:
long-run should be long run
main dictionary should be main directory
screen this is should be screen. This is
pathh should be path.
This tutorial is looking a little janky… why does the “code” read “YOUR Page content here”?

On the Exporting tutorial:
wordpress should be WordPress
your going should be you’re going.

On the second part, importing:
wordpress should be WordPress
Your should be your
cimpleted should be completed.

On the permalinks tutorial:
Permalinks, are should be Permalinks are
somthing should be something
don that should be done that
Ttype should be Type.

On the “removing ‘comments are closed’” tutorial, what exactly do you mean by “making a website”? Of course you’re making a website… why else would you be using WordPress?
quiet should be quite.

On your top commenters tutorial, you say “commenter” then “commentator”… stick with one. Preferably “commentator”.
your done should be you’re done.

On the “WordPress on your index” tutorial, you should mention that this happens when you install WordPress in a folder, and you should also explain which index.php file you are dealing with.
dont should be don’t
intergrate WordPress to should be integrate WordPress with.

On the PHP tutorial:
Main HTML should be Basic HTML
header.php in it should be header.php. In it
have not got should be do not have
site so everything should be site – so everything
individual page so should be individual page – so
like this yours should be like this. Yours
style.css insert should be style.css. Insert
your normally CSS strait should be your original CSS straight
strait into should be straight into
You maybe used to should be You may be used to
i’m going should be I’m going
new file name it should be new file. Name it
it its going should be it, it’s going
i’m just should be I’m just
page.Where should be page. Where
main root should be main directory
page but should be page.

More

There’s nothing much here – you should credit where you got the colour picker from, unless you actually made it yourself.

Hosting

On the main page:
Welcome to hosting @ RReliant, as should be Welcome to hosting at RReliant. As
which really means can host should be which means that I can host
try’s should be tries
RReliant isn’t a huge site should be RReliant is a small site
improving, we should be improving; we.

I’m not sure if you really have a team here of if you are simply the one hosting. If you don’t have a team, your hostees aren’t going to like it if you make this up.

On the value packages page promo, after should be promo; after.

The order page shouldn’t have comments enabled at the bottom. It’s confusing.

On the terms of service page more happier should be happier.

On the addons page USD $ should be just USD. Also, one of the prices is in pounds, not USD.

Ask

There’s no sidebar on this page; I don’t know if it was intended. Also, you haven’t credited Jem for the script.

Contact

You don’t really need this in your main navigation as it’s in the “about” section.

Originality & Creativity

I think this has improved since your last review in terms of content. Your layout uses some unique colours, as I know you like using bright colours, but I think you could spice it up a bit and be more unique. Things like the woodgrain background – that’s quite common. It’s a neat layout but I guess it could be a bit more interesting.

You’ve removed a bulk of your graphics, it seems, and I believe you’ve cut down the amount. Your site looks a lot cleaner and you’ve kept the content that is best.

Organisation & Errors

Quite organised!

You had a lot of mistakes in your writing though; these need to be fixed. I think your article was pretty well written, but because you had so many mistakes in your tutorials it looked like these were really rushed. I suggest you go over those.

Overall Comment

I see you have removed the bulk of your tutorials that were useless, such as the completely basic and simple Photoshop ones. This is a move you made which I’m quite happy about.

I can’t recall if you have added anything new, but the tutorials you have are quite useful. I can’t really pick a strong point because you don’t have many graphics, but I suggest writing more tutorials and sharing things when you learn something new, perhaps adding a few more layouts, or adding articles.

I think you did a great job on the article you wrote. If you write more and make sure you proofread what you write, you’ll have some better and more original content on your website.

Rating

(out of 5)