The Context
After identifying the website’s goals, it was essential to also define the stakeholders to guide our primary research, usability testing, and inform design decisions in later stages.
The stakeholders are:
1. local businesses of Kingston
2. Kingston City Council
3. government and local agencies.
Tourism plays a crucial role in a city’s economy by increasing revenue, supporting the local manufacturing industry, and creating essential service jobs. With this in mind, the goal was to make the website's navigation predictable, reliable, and consistent to enhance the user experience.
Content Audit
A content audit of BeautifulKingston.CA using Content Auditor and Screaming Frog SEO Spider revealed a structure primarily composed of images and text. The site contains 224 images (65.50%), 114 HTML files (33.33%), and minimal CSS and JavaScript (0.58% each). GIFs are used for decoration and headlines, adding unnecessary load, accessibility issues, and increasing page load times.
On the text content part, according to the crawling result on On Point Content Auditor for this site, the reading grade score was only 14.6, indicating that the content on the site may not be easy to understand.
In addition, the average content age is 3084 days, which means the content on this website is around 8 years old. Outdated content may frustrate the purpose of providing up-to-date tourist information to users.
Navigation System
In addition to the content audit, a brief analysis of the navigation systems was conducted to better understand how users locate the information they need.
2 main problems are found:
1. Flat Information Hierarchy in Navigation Menu
The website features a scrollable global navigation bar with over 30 links to various pages. The lack of categorization and hierarchical grouping makes navigation difficult and leads to information overload.
2. Duplication in Footer
The website includes a global footer with over 30 links, many of which are duplicates of those found in the global navigation bar. As a result, the footer fails to serve its intended purpose of providing secondary navigation to less critical pages, such as the Privacy Policy and Legal Notice.