EDIT: He has a review of a one-page website
here.
I just want to address some of the comments in the review for the benefit of others. For background, part of my role is to research what makes for effective websites - and I mean 'effective', not pretty. The site itself is for a local theatre company.
Something for people generally to bear in mind when looking to review a site is that they are not the only user. It's fine to look at things from a personal point of view but there may be contexts and audiences to consider that aren't obvious. In this case the reviewer does try to take accessibility into account.
The site is described as 'ugly' which I'd agree with, although that's a subjective personal opinion and probably does impact effectiveness, but that could be tested.
The statement is made "The most important piece of information, the details of the next production, are right there on the home page. No hunting around."
I would argue that many visitors to the site will first want to know the location of the theatre. There are mentions at the top of the page of 'Lighthorne' and 'isle of man' (sic) which could lead people to think that's where the plays are - it appears they are in Stratford-upon-Avon (yes, Lighthorne isn't far).
"Everything else I wanted to know is on a link to the 'about' page".
I struggled to find this link. The resulting 'about' page has tiny text with lines too long to read comfortably. On mobile you have to pinch zoom to read it, and then scroll side to side.
"Because the site is so simple it works perfectly on mobile without anyone having to do extra work." True it renders on mobile but it's not all usable.
"It is accessible (for the blind as far as I can tell. The image correctly has an empty alt tag (as the information in it is repeated as text). Most websites get this wrong."
The lack of alt text or a description for the image means a screen reader will hear "Welcome to theatre company" and miss the name of it. The second image could include a description of a lady in a period gown looking at a stately home, which some blind users would enjoy. It also includes a phone number which is not on the page.
The varying font styles and colour and the patterned background make some of the text effectively invisible to readers with poor sight and colour blindness. It's suggested that "The readability issue is easily fixed by deleting the background image (I tried blocking it and the site looked much better)." Quite aside from the fact that this shouldn't be necessary in the first place, how many prospective theatre goers know how to do that?
The review says the site 'has some faults' but doesn't consider these fatal. These include "some broken links and 'under construction' pages". Research has demonstrated that this type of issues impacts the trust that users have for a site. If broken links are allowed to persist it calls into question the trustworthiness of the operator. Right or wrong.
I note that the 'html title', which is the text in the tab and which goes into bookmarks is 'index'. So if someone finds the page useful and bookmarks it, they'll see a few months later 'index' which isn't helpful.
If you want to book at ticket you have to use your phone to read a QR code. At least the Theatre's Facebook page does have a direct link to the booking site. There should be one here. Why a QR code? It's certainly not going to be easy for the blind.
The conclusion of the review is "In short, if the PR aspect of a nice design is important, then you need to prioritise it. If you want to put your users first, then stuff it." I'd agree. But in this case the 'nice design' isn't about PR, it's about usability.
My takeaway is that if you are really confident that you know what elements of 'nice design' matter to effectiveness and you want to code your own site then fine. Otherwise you need the help of someone who does know, or use a templated site which you can still make a mess of but stand a better chance.