Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Research & Resources 6 min read

Website health assessment worksheet

A working worksheet for reviewing availability, platform currency, access, performance, content, privacy, backups and operations, with owners and evidence.

E
EncryptTechBD · 0 comments
Scientist working with laboratory equipment
Photo: U.S. Department of Energy / Rawpixel

Website health reviews often produce a number and very little else. A tool scans the site, generates a score, and the report is filed without anyone agreeing what should change. The score also hides the questions that matter most: who can restore the site, whether the backup has ever been tested, and whether the person with administrator access still works for the company.

This worksheet is designed to be copied into a document, completed with evidence, and signed. It works for a brochure site, an online store and a custom web application. The output is not a grade. It is a short list of risks with owners and dates.

How to use this worksheet

Record the site, the date, the reviewer and the people interviewed. For every check, capture four things: the evidence seen, the owner, the review frequency and a status of Pass, At risk or Fail. Do not accept "looks fine" as evidence. A screenshot, an export, a configuration page or a test result is evidence. If a check cannot be completed, mark it At risk and say what is missing.

Use the same worksheet every quarter so that changes are comparable. A different checklist each time produces a different picture of the same site.

Section A: availability and domain

  • Uptime monitoring runs from at least two locations. Evidence: monitoring dashboard with alert history. Owner: operations. Frequency: monthly.
  • The TLS certificate is valid, covers the correct hostnames and has a named renewal owner. Evidence: certificate details and calendar reminder. Owner: technical lead. Frequency: quarterly.
  • Domain registration, DNS and registrar access are controlled by the business, not only an agency. Evidence: registrar account list and recovery contacts. Owner: director. Frequency: annually.
  • Redirects, canonical host and www/non-www behaviour are consistent. Evidence: a redirect map and test results. Owner: developer. Frequency: after any migration.

Section B: platform currency

  • The CMS, framework or application core is on a supported version. Evidence: version screen and vendor support statement. Owner: developer. Frequency: quarterly.
  • Plugins, themes and libraries have a current inventory, including last update and support status. Evidence: inventory sheet. Owner: developer. Frequency: quarterly.
  • The runtime, database and server packages are supported. Evidence: hosting panel and end-of-life reference. Owner: hosting lead. Frequency: quarterly.
  • Abandoned components have a replacement or removal decision. Evidence: decision note with a date. Owner: technical lead. Frequency: quarterly.

Section C: access and security configuration

  • Every administrator has a named account, and multi-factor authentication is enforced. Evidence: user list with MFA status. Owner: security lead. Frequency: quarterly.
  • Roles follow least privilege, with no shared logins for everyday work. Evidence: role matrix and a sample of accounts. Owner: operations. Frequency: quarterly.
  • A web application firewall or rate limiting is active and reviewed. Evidence: configuration export and blocked-request review. Owner: hosting lead. Frequency: monthly.
  • Security headers, upload handling and file permissions are configured and tested. Evidence: header report and upload test. Owner: developer. Frequency: quarterly.
  • Secrets and API keys sit outside the codebase and are rotated when staff leave. Evidence: secret store inventory and rotation log. Owner: technical lead. Frequency: on change.

Section D: performance

  • Field performance is reviewed by template, not only by homepage. Evidence: Core Web Vitals report for the last 28 days. Owner: developer. Frequency: monthly.
  • Images are correctly sized, compressed and given dimensions. Evidence: a sample of templates and image weights. Owner: content lead. Frequency: quarterly.
  • Caching and a content delivery network are configured where they help. Evidence: cache rules and a before/after test. Owner: hosting lead. Frequency: quarterly.
  • Slow queries and application errors are logged and reviewed. Evidence: error log sample and query report. Owner: developer. Frequency: monthly.

Section E: content and search

  • Broken links and unexpected 404s are checked on key journeys. Evidence: crawl export and fixes. Owner: content lead. Frequency: monthly.
  • Titles, descriptions and headings are unique on revenue or enquiry pages. Evidence: crawl report. Owner: marketing. Frequency: quarterly.
  • The sitemap and robots rules match the intended indexation. Evidence: sitemap sample and robots file. Owner: marketing. Frequency: after launch or migration.
  • Structured data is valid for the page types that use it. Evidence: validation test result. Owner: developer. Frequency: quarterly.

Section F: data and privacy

  • Forms collect only the fields the business uses, with a stated purpose. Evidence: form inventory. Owner: marketing. Frequency: annually.
  • A cookie and tracking inventory exists, and consent behaviour matches it. Evidence: script list and consent test. Owner: marketing. Frequency: quarterly.
  • Third-party scripts are limited, reviewed and removed when no longer needed. Evidence: tag manager export. Owner: marketing. Frequency: quarterly.
  • The privacy notice describes actual practice, including retention and contact routes. Evidence: published notice and retention note. Owner: director. Frequency: annually.

Section G: backup and recovery

  • Files, database, configuration and DNS records are covered by a documented backup. Evidence: backup manifest. Owner: technical lead. Frequency: quarterly.
  • At least one copy is isolated from the production account. Evidence: storage account and access path. Owner: technical lead. Frequency: quarterly.
  • A restore has been tested, timed and recorded within the last quarter. Evidence: restore log with result. Owner: operations. Frequency: quarterly.
  • An offline runbook names who declares an incident and who restores. Evidence: runbook copy and contact test. Owner: director. Frequency: annually.

Section H: operations

  • A patch and update cadence is documented and followed. Evidence: change log for the last two quarters. Owner: developer. Frequency: monthly.
  • Monitoring covers uptime, certificates, errors and backup success. Evidence: alert configuration. Owner: operations. Frequency: quarterly.
  • Access is reviewed when someone joins, changes role or leaves. Evidence: access review records. Owner: operations. Frequency: quarterly.
  • Support contacts, vendor responsibilities and escalation paths are current. Evidence: one-page support map. Owner: director. Frequency: annually.
  • Handover documentation exists for the site, hosting and integrations. Evidence: document index. Owner: technical lead. Frequency: annually.

Scoring and sign-off

Mark each item Pass, At risk or Fail. Weight the critical sections, meaning availability, access and recovery, more heavily than content polish. A site cannot be signed off as healthy while any item in those three sections is Fail. Record the reviewer, the business owner and the date, and attach the evidence pack. If an item is accepted as a known risk, write down who accepted it and when it will be reviewed.

Remediation schedule

Group failures by consequence. Exposed credentials, an expired certificate, a public administrator page or a backup that cannot be restored should be handled immediately. Issues that materially affect revenue or customer trust should have a dated plan. Cosmetic and content improvements can wait for the next publishing cycle. Each remediation needs an owner, a target date and a retest, otherwise the worksheet becomes another report that changes nothing.

Where to get help

Our team runs these reviews and the follow-on maintenance under Managed Technology & Cybersecurity. Assessment and maintenance options, with their commercial terms, are set out on the pricing page. For the cleanup side of a security incident, read the malware cleanup and prevention checklist.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes