The Felt Source Peer Review - Needs Quality Control

Keeping a website polished isn’t just about the graphics; the smallest details - like the year listed in a byline - can create a ripple of confusion for visitors. On The Felt Source, the front page proudly declares “Selling quality felts to Schools, Libraries, Parents, and Churches for over 15 years.” Yet a glance at a product page shows “13 years,” and a deeper dive lands at “11 years.” This inconsistency can make the brand feel unreliable. A practical fix is to centralize that information. Use a server‑side include or a template variable that pulls the same string into every page. When the years change, update the single source and the whole site updates automatically. This approach keeps the message fresh, saves editing time, and signals a professional attention to detail. Additionally, place that consistent line in the footer. Visitors naturally scroll to the bottom for contact info, and a unified footer becomes a subtle but powerful reminder of the brand’s longevity.

Testing for Dead Links: Avoiding Broken Paths

Broken internal links do more than frustrate users - they break the trust you’ve built. A quick audit of The Felt Source revealed a pattern: the nurseryrhymes page had two links that both pointed to “.htmll” instead of “.html.” The extra “l” turned them into dead ends. Another example was a dead link on the international currency converter page, which led nowhere. These mistakes often slip through because manual checks are slow and error‑prone. The solution is twofold: automated link checking and regular manual reviews. Tools like Screaming Frog or Sitebulb crawl the site, flagging broken internal and external links. Running a crawl after every major change catches errors before they reach visitors. Pair this with a quick manual test on the most visited pages, ensuring that the critical pathways stay intact.

Link errors also highlight a lack of testing before publication. Whenever a new page is added or an existing page is updated, create a temporary staging URL and walk through every link. A simple “click test” from the home page to every major category can reveal hidden problems. If you’re using a CMS, configure a test environment that mimics the live site. Once the content passes the link test, move it to production. By making link checking a mandatory step, you prevent frustration and protect your site’s reputation.

Streamlining Product Page Design for Better Scanning

Product pages should feel like a well‑ordered shop. On The Felt Source, products appear left, right, center, and even above the text, creating a visual mess. This lack of consistency makes it hard for visitors to locate what they need. The first rule is to pick a single layout style and apply it sitewide. Choose a structure that places the product image, title, and key details in predictable positions. A common pattern is a two‑column layout: the image on the left, the description on the right. When you add more information - price, size, color - append it below the description. Stick to this pattern across all product categories.

Visual hierarchy matters. Use heading tags for titles, larger fonts for prices, and subtle borders to separate sections. Keep the background light so that text stands out. Avoid placing product titles above the image; that disrupts the scanning flow. Consistency also extends to the placement of call‑to‑action buttons. Whether it’s “Add to Cart” or “Learn More,” keep the button in the same spot on every page. This predictability speeds up decision‑making and reduces cognitive load.

Another tip is to limit the amount of text on each product page. If the description is too long, break it into bullet points. Bullets scan faster than paragraphs and allow visitors to pick out key benefits quickly. Add a small “Read More” link for those who want deeper details. Finally, test the layout on multiple devices. A desktop may handle a wide two‑column design, but on a phone you’ll need a stacked layout. Use responsive CSS to adjust automatically, ensuring the same clean look no matter the screen size.

Implementing a Robust Change‑Management Workflow

Quality control isn’t a one‑time fix; it’s an ongoing practice. Before any content goes live, create a copy of the page in a sandbox environment. Edit the copy, then run a full test suite: check for broken links, verify that all images load, and confirm that the CSS styles render correctly. Once the page passes all tests, merge the changes into the live site. Use version control - Git, for example - so that you can track changes and revert if needed. A pull request system forces a second pair of eyes on every update, catching mistakes before they become public.

Automate repetitive checks with scripts. Set up a cron job that runs a link checker nightly, or integrate a continuous‑integration pipeline that runs tests whenever new content is pushed. If any test fails, the pipeline stops the deployment and notifies the team. This early detection saves time and prevents broken links from reaching users. Document the workflow in a simple step‑by‑step guide and train all team members to follow it. Consistency in process is the backbone of consistency in output.

Finally, don’t forget user feedback. Add a small “Report a problem” link on each page. When a visitor notices an issue - whether a dead link, a typo, or a misplaced product image - they can report it quickly. Review these reports regularly and incorporate them into the next maintenance cycle. By treating quality control as a collaborative effort between the team and its audience, the site stays reliable and trustworthy.

- Peter Langford, IT & C Manager, Marston & Langinger

Peer reviewers volunteer their time to help web owners refine their sites. Take a moment to visit this reviewer’s own site and acknowledge the value of their contribution to the web community. If you’d like a review, email