As you have discovered, supporting a website and continuous improvement efforts are an "ever-growing job" and in fact, never-ending. For all of the hard work, and even more for seeking suggestions for improvement from others.

Rina, Aamina, Michelle, Jeff, Bennett, and Patrick all made excellent points for consideration. To not re-hash their thoughts too much, following are some more basic "block and tackling" considerations.

1. Regularly scan for broken (or not performing links) and resolve them. Examples are:

  • In  there is a broken link
  •,  likely resulting from a certificate issue on the target domain.
  • In there is a broken link
  •, likely resulting from the absence of https://www in the URL.
  • In there is a broken link
  •, resulting from a 404 not found error.
  • There are several pages where the src or href are an empty string. Using href='' or src='' can cause unexpected effects such as traffic spikes or cookie corruption, and causes JavaScript error events to fire on Firefox).
  • An example is (line 971).

    2. Review potential browser compatibility issues, such as:
  • Internet Explorer, Chrome, and Firefox display a security warning when a secure https: web page includes http//: content.
  • In IE8 and Firefox 23 onwards, the default option is not to display the http:// content.
  • To fix this, use relative URL paths ../images/file.png, or full URL paths /images/file.png; or absolute https URLs
  • An example is (line 747). Also, consider replacing flash multimedia content with MP4 (recommended).
  • Older browsers do not support SVG images (e.g., Android 2 or earlier). An example is on (line 2509).

    3. Search Engine Requirements
  • Do not stuff alt text with keywords that users are unlikely to view. Doing so may result in search engine penalties. Example: (line 1271)
  • Google and Bing recommend avoiding broken links. Example: reference (line 771).
Working Hands
  • Bing recommends that each page should not have more than one h1 reference element, e.g., (line 773, 774).
  • Bing webmaster guidelines recommend that each page have one h1 element. An example with the h1 missing is (line 74).
  • Strongly suggest that you consider using the Yoast WordPress SEO tools, if you have not already.

    4. Standards
  • Review:  W3C HTML/XHTML Validation and  W3C CSS Validation
  • In many cases, these best practices revolve around keeping up to date with coding standards and replacing obsolete features as needed.
  • Example: The align attribute on the p element is obsolete. Use CSS instead. When using WordPress, make sure you're plug-ins are up to date and if one doesn't get the desired results, switch to a more technically up to date plug-in.

    5. Accessibility
  • Review accessibility features against the standards of WCAG 2.0 and Section 508.
  • Non-compliance can result in issues for older users, people with disabilities, or accessibility needs. Human testing, along with input from automated tools needs to be used to evaluate Accessibility.
  • People with these kinds of requirements may not need your site's services :). That said, Accessibility is a pretty big deal, especially particularly with government users and web sites.

    6. Regularly review web site performance
  • There are many complexities to evaluating performance and excellent resources out there available at little or no charge.
  • A tool that we like is
  • Some hosting providers are better than others, especially for optimized WordPress sites.