back to Completed Reviews
Site Name: Evolute
Owner: Georgiana
Reviewed by: Georgina
Reviewed on: 24th November 2008
Site Name
The name Evolute is great, and I like how you’ve made it more personal by incorporating something you like.
A mathematical term is definitely original and out of the ordinary!
Coding and Validation
When I run your site through the W3C Markup Validation service you have 25 errors. Some of them are fatal (they won’t kill you but you’d better address them!):
- No doctype! We want your pages to be properly read with the correct coding!
- No character encoding!
- Your
<html>opening tag is in the wrong place!
To address these issues, let’s look at what you have first on your document:
<html dir="ltr">
<head>
<html>
<head>
The validator shows that your site is best suited to HTML 4.01, but when I look through your coding I see you’re trying to achieve XHTML. This produces a lot more errors because of a lot of tiny things you’re missing.
Firstly we’ll stick in your doctype and address these fatal issues. You have two head tags, in fact. And your HTML tag is after one of them. Let’s fix this up and include doctype and character encoding. This is what you should have at the top of every page instead of the above:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<html>
<html dir="ltr">
<head>
You’re mainly forgetting the trailing backslash in some parts of your coding, like in your favicon. In parts of your layout in images, you’re forgetting it as well. Other times, you’re putting it in, but neglecting to leave a space before it.
In other places you are using <center>, which is deprecated. You should change it through your CSS through an attribute such as <h4> or something you rarely use.
Your CSS is not validated (check here). You’re using coloured scrollbars. Eek! What for?! They only work in Internet Explorer, and as you can see, cause errors in your CSS coding. They can also cause problems in other browsers, and they’re not necessary!
For fonts such as Tw Cen MT it’s best to write “Tw Cen MT” for any font families with spaces – just quote them. You have other crazy errors in your CSS which I won’t be going through because I can see that coding isn’t your strong point, but at least fix up a few errors!
Browser Compatibility & Usability
Everything looks the same in all browsers (except Internet Explorer) – according to Browsershots.org.
The navigation is clear, which is great. I would suggest adding a link back to the homepage – maybe linking the ‘E’ to the homepage.
The text is readable and is of a good size and colour!
Layout
It’s centered in everything but Internet Explorer. It still looks alright, but instead of 0 auto for the margin, try 0 auto 0 auto.
The layout is nice. The brushes work quite well together, though on the left, it would be better if it faded out instead of just being chopped:
I like the colours used and the consistency in font. Everything looks polished and neat, but your footer doesn’t fit too well because the border doesn’t fade:
I like the big ‘E’ but it’s a little pixelated and the edges should be a little rough to complement the rough brushes. On closer inspection, the floral brushes are also chopped on the side:
There are a few glitches in your layout when I look pretty close; otherwise everything looked professional and clean. You might want to touch up those choppy bits on the layout. Your previous layout was more refined in this way; no choppy bits – so I know you can do it 
The CSS looks pretty good. I don’t really like how the links turn bold on hover, sometimes your text shifts a bit and it looks funny. No problem with the colours though.
Content
Owner
‘Evolute’ links to your old URL here.
referance should be reference
tatoos should be tattoos
earings should be earrings
in house should be in a house
definately should be definitely.
I love the photos and the little lightbox script you use! No broken images here.
Site
I huge should be a huge
introduced piczo should be introduced to Piczo
freewebs should be Freewebs
I said should be I thought
imediately should be immediately
centers should be center
urvature should be curvature
php should be PHP.
Some of your credits should be capitalised, like DeviantArt and DaFont. And you should also credit Cutenews and if any, people who have helped you. And the Lightbox Javascript you used for your photos.
Your affiliate application would be better if it wasn’t in a popup box – some people may have popups disabled. Good job on putting your affiliates in alphabetical order though!
On your ‘previous layouts’ page your CSS has gone funny and some of your links are very large. You might want to capitalise DeviantArt and also try and link to the actual DeviantArt use when you credit them. I notice you’ve specified “Mutsie” in your current layout so keep that!
You might want to capitalise font names – Script MT Bold, Maindra GD, and the rest.
Portfolio
Organised page again – well done!
everyday should be every day.
And do capitalise DeviantArt and other site names.
As all your digital art is of different size it’s best to sort them into their size categories to avoid people having to open them up to see what size they are.
These are all very lovely and very creative. I love the colours in all of them; they’re truly amazing.
The title ‘wallpapers’ should be ‘digital art’.
Wallpapers are just as wonderful; you might want to write the size of these as well so people don’t have to open up the image.
Your photography is just stunning. I really like looking through photos, and yours have always been quite amazing. I think it’s nice that you include a portfolio in your website to make it more personal.
The only little problem I have is that the Lightbox Javascript slows things down a little.
On ‘about my work’:
begining should be beginning
esthetical should be aesthetical
stubbled should be stumbled
ment should be meant
stuborn should be stubborn
aswell should be as well
titler should be title
youin should be you in.
This is a lovely page about your hobby and how you came to like photography so much. I agree, I have to take my camera everywhere! 
Remove ‘introduction to DSLR’ until you get the page up – don’t give visitors the impression that you have something unfinished.
On ‘photo tips’:
smother should be smoother
stabble should be stable
inestetic should be unaesthetic
.
This page was very well done! It’s quite impressive and definitely unique. It personally helped me a lot and I found it very interesting and original.
Visitor
HTMLs should be HTML codes
apreciate should be appreciate
learning and please should be learning so please.
Your HTML coding doesn’t come up on your affiliates page. Don’t include this code and instruction, people know how to use images like any other image.
I don’t think these affiliate images are used anymore. Affiliates deserve to be properly linked, not just with a tiny square.
A lot of your blends use celebrity images, which is actually illegal. Read this article to find out more.
Your older blends look great as well but it’s best you remove them – because, well, they’re old. I also don’t see the point of these blends, some are too big or small to be used as layouts.
Your brushes look great and well made, especially the floral ones.
Therefor should be Therefore
abr. should be .abr
You are offering downloads of programs that you don’t make, yet you’re saving them to your server, which is like redistributing them and is often not allowed. I suggest you link to the actual site or the actual site’s download. It will also save you time and space.
You’re using anchors for your HTML codes. It’s better you don’t leave such big gaps between the sections; I opened all these links in different windows/tabs and found that they’re all on the same page.
These codes aren’t really useful – HTML is more advanced now, and people generally know these simple cut-and-paste codes. A lot of the link effects are better controlled by CSS files.
Piczo add should be Piczo ad.
I love these patterns, they’re all very nice. The last dark brown one doesn’t look too good though. Most of these look like they’ll tile pretty well as backgrounds.
On your scans page:
wonderfull should be wonderful.
These are all well taken especially the second last one – this one. I think they’re really good quality as well.
These textures are really beautiful. I love the range of colours in them. You have grungy ones as well as soft pretty ones. The variety is really impressive.
On your ‘get more hits’ page:
Sign in should be Sign up
reguraly should be regularly
aproach should be approach
adress should be address
someones should be someone’s
sites affies should be site’s affies
is horribly should be it’s horribly
webb should be web.
Fairly good article here, congratulations on not following trends – I agree.
These tutorials are all pretty good and easy to follow, but I’m only skimming through the Cutenews tutorials. Cutenews is a holey script that is easily injected with malicious PHP code (quote Jem), and you wouldn’t want to encourage it’s use any further 
Form should be form
Commnet should be Comment
Redirecting should be redirecting
Installing Brushes should be Installing brushes
Improoving should be Improving
Water mark should be Watermarks
piczo should be Piczo.
On your banning ip tutorial:
yout should be your
inside should be into
Ip should be IP.
On your Custom 404 tutorial:
so that should be so what’s that
incorrect should be incorrectly
a.htaccess should be a .htaccess
nonsens should be nonsense.
On your last update tutorial:
homepagea should be homepage and you
sais should be says
pages should be page.
On your Making PHP Files tutorial:
purpouse should be purpose
actuall should be actual
depens should be depends
. Then should be Then
. How should be How.
On your Loading Time tutorial:
if should be If
then you use should be then use.
On your PHP Intro tutorial:
tools should be Tools
actuall should be actual
page you want should be pages you want
descriptioin should be description
everypage should be every page
iframe should be iFrame
reffers should be refers
ussually should be usually
aswell should be as well
world wide web should be World Wide Web
therefor should be therefore
piczo should be Piczo
freewebs should be Freewebs
how are should be who are
badwidth should be bandwidth
ads:textlink should be ads: textlink
1,5GB should be 1.5 GB
ads:banner should be ads: banner
web should be Web.
On your Uploading with Filezilla tutorial:
it’s should be it
actuall should be actual
uncomplicated should be simpler
very much should be very long
instalation should be installation
filezilla window should be Filezilla window
jpeg bmp should be jpeg, bmp.
On your Uploading Files tutorial:
folllow should be follow
hosts site adress should be host’s site address
allready should be already.
On your Basic CSS tutorial:
image,repeated should be image, repeated
freewebs should be Freewebs
degins should be design
piczo should be Piczo
hand of it should be hang of it
alot! should be a lot!
it’s own should be its own
easy! should be easily!.
On your Double Underline tutorial, ‘this’ only has one underline, not two.
piczo should be Piczo.
On your CSS Lists tutorial:
beginig should be beginning.
On your Auto-Redirections tutorial:
the url address should be the URL address.
On your Buttons/Affie Images tutorial:
adress should be address
webb adress should be web address
adress should be address
affiliate’s should be affiliates
webb adresses should be web addresses
sticked should be stuck.
The buttons here link to your old URL!
On your ‘direct linking’ tutorial:
it’s URL should be its URL
Bandwith should be Bandwidth
transfered should be transferred
desing should be design
php should be PHP
ftp should be FTP.
This tutorial sent out a good message, but should be renamed to ‘saving images to your own server’.
Some notes on your ‘displaying HTML’ tutorial:
- You don’t need the asterisks in your textarea coding, because you can simply use < and > to display coding. I can see you already know that, so at least use it in this ‘Number 1′ section.
- xmp is deprecated; you’re right. You can’t use it anymore – use <pre> instead.
- To avoid using the eeky spaces, you can type & for the & symbol!
- Usually you only need pre, no need for code at all.
On your favicon tutorial:
tha should be the
it’s very should be it’s a very.
‘Fixed backgrounds’ leads to a 404.
History links aren’t really necessary, most browsers have back/forward/refresh buttons integrated into their browser. You can keep your links, but the tutorial isn’t really useful.
Iframes – NO! Iframes are a pain. They give search engines hell, and also visitors when they want to save or bookmark just one page. They are also really, really ‘stoneage’ and hardly used. I recommend you remove this tutorial.
Aligning is better done with CSS, especially for text, so this tutorial isn’t too great.
I like the image opacity tutorial, and that you’ve included the code so it works in Firefox too!
‘Image spacing’ leads to a 404.
On your thumbnails tutorial:
piczo should be Piczo
it’s URL should be its URL
painfull should be painful
proffesional should be professional
make your should be makes your
mesurement should be measurement
beginig should be beginning
twards should be towards
got to bottom should be got to the bottom.
Your images here link to your old URL, so you might want to change that.
On your ‘page anchor’ page:
dfferent should be different
must the should be must fill in the.
On your Blending tutorial:
whereyou should be where you
losses it’s should be loses its
acuracy should be accuracy
pallette should be palette.
Credit the photos here – you shouldn’t use celebrity images!
On your Colorizing tutorial:
diferentiated should be differentiated
outline should be outline it.
Credit the photos here too.
On your Image to Sketch tutorial:
blendingmode should be blending mode.
Credit the photo.
On your Installing Brushes tutorial:
bruh should be brush
pacient should be patient
if you some should be If you get some.
On your Keyboard Shortcuts tutorial:
dissapear should be disappear.
On your Making Brushes tutorial:
how to do some people manage do make should be how some people managed to make
aswer should be answer
it really should be it doesn’t really
ussually should be usually
results a should be results in a
projects.For should be projects. For
it’s margins should be its margins.
On your Making Brush Sets tutorial:
is .abr should be is a .abr
Know should be Now
namig should be naming
Therefor should be Therefore.
On your Watermarks tutorial:
photoshop should be Photoshop
Pallette should be Palette.
On your Piczo tutorial:
piczo should be Piczo
piczo-pro should be Piczo-pro
right to should be right next to
apropriate should be appropriate
A pop up should be A popup
reconnct should be reconnect
wich should be which
O pop-up should be A popup
Oraganize should be Organize
only piczo members, only piczo friends should be only Piczo members, only Piczo friends
trick, on should be trick: on
clcik should be click
piczo toolbar should be Piczo toolbar
clcik should be click
recomend should be recommend
not to should be not too
. okay should be . Okay
top piczo should be top Piczo
twards should be towards
. under should be . Under
you’l should be you’ll
piczo site name should be Piczo site name
clcik should be click
clcik should be click
recomend should be recommend
custom piczo should be custom Piczo
proffesionalism should be professionalism
. the should be . The
the piczo toolbar should be the Piczo toolbar
piczo toolbar should be Piczo toolbar
guaranties should be guarantees
piczo page should be Piczo page
on piczo should be on Piczo
personnaly should be personally
much more should be many more
let’s should be lets
i really like should be I really like
photobucket should be Photobucket
doens’t should be doesn’t
on piczo should be on Piczo
piczo-pro should be Piczo-pro
piczo-pro should be Piczo-pro
piczo pro should be Piczo-pro
applyed should be applied
piczo pro should be Piczo pro
piczo toolbar should be Piczo toolbar
i never should be I never
proffesional should be professional.
Link ‘www.photobucket.com’ to the actual Photobucket site.
Don’t make such big gaps between the sections, and consider a ‘back to top’ link.
Note: On all your visitor pages and tutorial pages, your CSS has gone funny again and some of your links (to the pages I’ve already visited) are large, and when I hover over your links, they are HUGE.
Originality & Creativity
Your site had loads of elements of originality in it, especially in your photography. Your layouts are always very creative and so is all your art.
Some celebrity graphics have sneaked their way in through your blends, but other than that everything was very original and very creative.
Organisation & Errors
Your site was very organised, your links were even in alphabetical order. I was quite pleased.
Unfortunately you did have a few broken links and a whole bunch of errors in your grammar/spelling/punctuation.
Overall Comment
Georgiana, your site has a really great layout and your graphics and photography are definitely amazing. I did think these were your strong point.
Most of your visitor content was not very useful. Your tutorials were well written but a lot of them should be trashed, like the Cutenews and Piczo ones – which are pretty self-explanatory or aren’t really needed. A few of your other tutorials weren’t too good. Your site’s coding is quite a mess, so I don’t think you should be writing tutorials on coding.
You just have errors to fix mainly in your coding and CSS and grammar. They weren’t too overwhelming.
Your content is solid and quite good, but your coding isn’t. You should concentrate more on graphics and less on tutorials and such.
