Review: Cassie @ RetroRawr

back to Completed Reviews

screenshot

Site Name: RetroRawr
Owner: Cassie
Reviewed by: Georgina
Reviewed on: 12th August 2009

Site Name

“Retro” is a far too common prefix in website names. I like the name, but “retro” is just overused.

Coding and Validation

Your coding has 4 errors on the homepage.

You’re missing a </div> in your coding. Most of the other pages are valid which is good. Your coding looks clean and flawless and I can’t spot any things that need to be improved or fixed.

Your CSS has 8 errors and 26 warnings.

To fix several warnings, you need to quote fonts with whitespace like so:

Also, your CSS can be shortened further. You have values such as font: normal 9pt arial; and you can do this with a few more values.

Many of the errors are associated with Lightbox. This isn’t such a huge issue; it’s quite common and it doesn’t affect the performance of your website.

Browser Compatibility & Usability

Your site looks the same in most browsers, and it is navigable and functions in Internet Explorer, Mozilla Firefox, Safari, and Opera.

The text is fine and I have no problems reading it.

The navigation is quite unique and I like how it stands out on the yellow background. The way it stays at the top of the page is very unique and also useful for viewers as they navigate.

Layout

My first impression isn’t a good one. What really stands out to me is the busy background. It looks busy because of the colours used – you have used about five colours to design the background. The shapes used are also very random and don’t work well at all. The lines for the shapes are not smooth – the hearts, clouds, lightning bolts and bird shapes – all clash together and make the background very busy. The blue is also very bright and overall, the background is very distracting.

I have seen your previous layouts and they were so much better than this one.

The styling of the content section is okay. However the yellow colour really stands out and is much too bright.

The colour choices are not bad – but its the brightness of the colours that are having a bad effect. Softer and pastel colours would have suited this layout better, and a less busy background as well. The shapes could do without the faces, at least.

The container and content section could do with some padding. The text is a bit too close to the edge.

I like that you have opted for a busy background with very simple CSS, but the background you have chosen simply doesn’t work. The layout is fine, but the main things you need to fix are the background and the brightness of the colours.

Content

Content

This section would be better named as “visitor”. “Content” refers to all content on your website.

The reviews and “ask me” pages are pretty self explanatory.

The simple layouts are more like CSS templates, seeing as they really don’t have a navigation and the look of a “layout”. Also, when displaying code, use code and not textarea. You should convert the code into its entities and place it between <code> and </code>. Textarea is intended for user input only.

The pixels are okay. They could be made a bit more interesting and the edges smoother but otherwise it’s a good job.

I personally don’t like the fact that you’re using Lightbox for the textures. It actually takes a long time to load. Also, the lightbox itself has some problems – the “image x of x” appears far off at the left, and the “previous” button tiles in an array. You might want to look into this; perhaps there are a few errors in the files.

The icon textures are good. I believe they are to some extent better than the actual icons you have made. Your icons look a bit bland and the colours are dull. The text should also have some effects on these icons.

You’ve used a nice photo for the mini header but the whole header needs improvement. Some blending done on the image and further effects would make it look more appealing. The text also looks like it’s just been “slapped on”. It has no effect, not even a simple dropshadow. The pixelated text in the corner with your site name is also unsightly.

You have one layout/theme, and it’s quite nice. Simple and a good use of colour – just a simple purple in different shades. It would help to get this validated as well – there is just one error in the HTML but many errors and warnings in the CSS. The “site title” should have a bit of padding from the right; it looks squashed over there, and really, it should be centered like the rest of the layout to keep things consistent.

The seamless backgrounds are nice in that they are seamless, but the designs themselves are not really very interesting. They are unique as they are drawn by you, but the colours should be more interesting, and probably simpler as well. Adding some textures would again make these a lot better.

Tutorials

On the main page you have some mistakes:
programm should be program
brouser should be browser
Mangement should be management.

The tutorials would look more organised if they were in alphabetical order.

Looking through the CSS tutorials, they are easy to understand. Generally you seem to be opting for the “template” method, in which the viewer will understand with an example of the code. Often this isn’t desirable because the reader doesn’t really pick up anything or learn anything – regardless, your tutorials are well set out and give good examples.

On the “Learning CSS” tutorial, italuc should be italic.

The “using CSS” tutorial can be improved by explaining embedding styling and an external stylesheet to be more concise.

On the container tutorial, nessecery should be necessary.
This tutorial needs to be fixed because not everyone uses PHP includes. People following this tutorial may be puzzled by the mention of “header.php” and “footer.php”.

In your classes and IDs tutorial, you should make it more clear that an ID can only be used once.

The Pt to Percent conversion table is a nice reference point.

An example of the fixed navigation would be a nice addition to your tutorial.

On the installing FanUpdate tutorial, unfortunatly should be unfortunately. You can download FanUpdate from FanUpdate.co.uk.

On the meta tags tutorial brouser should be browser.
You have the slashes at the ends of these codes for XHTML; to avoid confusion you should remove them.

On the paragraphing tutorial:
Paragrah should be Paragraph
brouser should be browser
paragraphy may should be paragraph may
basic paragraphy should be basic paragraphing.

On the displaying HTML/CSS/PHP tutorial you have some mistakes:
unfortunatly should be unfortunately
thier should be their.
This isn’t the correct way to display code. The correct way to display code is outlined at JemJaBella.

On the tables tutorial, show’s should be shows.

On the special characters tutorial:
Charcters should be Characters
different should be different.

The Javascript tutorials are very unique. I suggest making a note that Javascript will not work on all platforms and browsers.

The PHP tutorials are also unique. The display date/time one should be modified; it doesn’t show the correct time for myself; it shows the time on your server.

On the retouching tutorial, brousing should be browsing.
It isn’t noticeable on the final result, but on the steps in between, the result of the “healing brush” looks quite patchy and blotchy on the girl’s face.

On the vintage effect tutorial, display the images on the page to avoid clicking to open an image.

On the understanding webhosts tutorial:
completly should be completely
Host’s should be Hosts.

On the WordPress themes tutorial, you have some question marks for some symbols.

Articles

On this page programms should be programs.

On the Hannah Montana article:
amoung should be among
programm should be program
Whats should be What’s
orginal should be original
SOme should be Some
thier should be their
stuff.I should be stuff. I
repetative should be repetitive
Threre should be There
similar,and should be similar, and.

On the Facebook article, its not easy should be it’s not easy.

On the “different way of getting hits” article:
thier should be their
toher should be other
yoursite should be your site
back an forth should be back and forth
Twitter ad ask should be Twitter and ask
dollers should be dollars.

On the illegal content article:
elses should be else’s
programms should be programs
searchs should be searches
leagal should be legal
necesseraly should be necessarily
tisdale should be Tisdale
thoses should be those
poulartity should be popularity
thier should be their
thats should be that’s.

“Article: Proffesional website” should be Professional website… if you really are trying to be professional yourself.

- Use good grammer. Make sure all your sentances make sense.

Incorrect. This is how the above point should be written.

- Use good grammar. Make sure all your sentences make sense.

And spelling, for that matter.
termanoligy should be terminology
puntuation should be punctuation
thier should be their
proffesinal should be professional (and the numerous other times you have spelled this wrong).

Spell “BROWSING” correctly on the essential programs articles; thanks.
programms should be programs
brousing should be browsing
lets face it should be let’s face it
Internet explor is slow, it crashes alot should be Internet Explorer is slow; it crashes a lot
absolutly should be absolutely
advertisment should be advertisement
programms should be programs
quiker should be quicker
DOwnload should be Download
profram should be program
unfortuantly should be unfortunately
Iff should be If.

On the stranger danger article:
DON’t should be DON’T
adress should be address
hav should be have
thier should be their
situtaions should be situations
definatly should be definitely.

On the beauty article:
appearence should be appearance
moisteriser regualry should be moisturiser regularly
blotchs should be blotches
blemishs should be blemishes
glamourous should be glamorous
disasterous should be disastrous
alot should be a lot
tweazers should be tweezers
your in a permanant should be you’re in a permanent
feauture should be feature
appearence should be appearance
trys should be tries
straigten should be straighten
your not Elly is bad grammar. It should be “you’re not Elly”, short for “you are”.

On the hair care article:
be be careful should be be careful
thouroughly should be thoroughly
over do should be overdo
to to protect should be to protect
its really should be it’s really
be come like should be become like.

On the revision tips article:
aswell should be as well
relavent should be relevant
programm should be program
nyour should be you’re
somthing should be something.

On the classes/subjects article:
your shouldn’t should be you shouldn’t
do bad should be do badly
If your teach. doesn’t should be If your teacher doesn’t
thier should be their
boreing should be boring
suprised should be surprised
teach’s should be teachers
acedemic should be academic
yourslef should be yourself
remeber should be remember.

Fun

I can’t really review contests and things. I found your blue smiley and completed the murder mystery though.

About

The site history would be a lot easier to read in paragraphs; not just as one huge chunk of information.
abit should be a bit
alot should be a lot
everyday should be every day
unfortunatly should be unfortunately.

Try making some inanimate buttons for your link buttons. Animated ones can be distracting.

Owner

I am greeted with many text effects on this page, making things hard to read. Reduce the amount of text effects on this page.
passionatly should be passionately
belive should be believe.

Originality & Creativity

You’ve got some very original articles and tutorials, and content in general. Your layout could be more creative and your graphics could do with some touching up. If you are not comfortable with graphics, I suggest trying something simple instead.

Organisation & Errors

Organisation was fairly good.

There were far too many mistakes on your pages. These need to be fixed as soon as possible. It’s unprofessional and makes your website look messy and as if it was rushed.

Overall Comment

The layout needs a bit of work. Your graphic skill needs a bit of improvement. However, you do not need to have exceptional graphic skill to create a nice layout. Work with shapes and colours as you have done with this layout, but make them more subtle.

You have some very good tutorials but these need a few improvements. Some are well explained, but others need to account for things like errors, correct coding, and so on.

You also really need to make use of a spellchecker to correct your many mistakes. Some of these mistakes are so careless (otherwise you’re telling me you can’t spell a simple word like “their”). Please fix these mistakes. Particularly with your article on professionalism, it is rather ironic that you have such mistakes.

With a simpler layout that hides your flaws, your website would look more impressive. You have great tutorials, though these could also be improved in some way. You’re well on your way to a great website but there are just many things you need to address first.

Rating
cookiecookiecookiehalfcookie

(out of 5)

2 Comments so far — leave one?

Cassie says:

Thanks so much :)
I am getting straight on fixing the errors.
I always spell thier wrong. At school, at home, on the computer. I just never spell it right.
As for the displaying HTML thing, I learnt that off Smileyhelper, and I have seen it on other websites, so I assumed it was right.
I am also going to do a simpler layout too :D

Reply to this comment »

Georgie replied:

You’re welcome!

Haha I hope you break that habit. :)

Ah, well, code is the correct way; just making sure you’re aware. More people are learning about that too nowadays so don’t worry. :D

Reply to this comment »

Leave a Comment

Super-cool smilies (click to use; don't abuse)

XD O_O D: @_@ ;) :love: :X :P :O :D :) :( /zzz /x3 /wave /wah /um /type /sweat /sus /snort /rose /puke /pow /poo /pirate /peace /oh /mwah /love /look /kiss /huh /ho /hmph /hehe /heart /finger /faw /ehh /ehe /eee /drool /cry /cool /clap /brow /bounce /bomb /blush /bash /asdfgh /argh /angry (Y) (H)
Comments may be held for moderation by me until they are approved. Comments related to the blog post are appreciated, rather than messages simply commenting on the website. Comments are responded to (as a reply here or as a response at your website) at my own discretion.