Each dimension uses a free, publicly available tool. No account needed for most.
Work through the sites in one tier at a time — doing all 24 in one sitting takes
roughly a full day. Open this page alongside the tools below and enter scores directly
into the scores array
for each site in the JavaScript.
🔒
Dimension 1 — Security (20 pts)
Tool: SSL Labs · Time: ~3 min/site ·
🤖 Automatable
Step 1.
Go to
ssllabs.com/ssltest
and paste the site URL. Tick "Do not show the results on the boards" to keep it private.
Click Submit and wait 60–90 seconds for the full report.
Step 2.
Note the overall letter grade at the top of the results page.
Convert to a score out of 20 using this table:
| SSL Labs Grade |
Score /20 |
What it means |
| A+ | 20 | Exceptional — HSTS enforced, modern TLS only |
| A | 18 | Strong — valid cert, no major issues |
| A- | 16 | Good — minor config issues (e.g. no HSTS) |
| B | 12 | Acceptable — older TLS versions still enabled |
| C | 8 | Weak — significant configuration problems |
| F / T | 0 | Fail — expired cert, untrusted, or no HTTPS |
| Site unreachable | 0 | Record as 0 and note in verdict field |
Also note: Scroll down in the SSL Labs report and check for
"Mixed content" warnings (HTTP resources loaded on HTTPS page). If present, deduct 2 points.
Record your finding in the site's
verdict field.
🏎
Dimension 2 — Speed (20 pts)
Tool: PageSpeed Insights · Time: ~2 min/site ·
🤖 Automatable
Step 1.
Go to
pagespeed.web.dev,
paste the URL, and click
Analyse. Wait for results (30–60 seconds).
Step 2.
Switch to the
Mobile tab (not Desktop — mobile is the relevant test
given that most Indians access government sites on phones).
Step 3.
Note the
Performance score (the large number, 0–100, at the top).
Convert to a score /20 using this formula:
Speed score = round(PageSpeed Mobile score ÷ 5)
Example: PageSpeed score 72 → Speed score 72 ÷ 5 =
14 / 20
Also record the
First Contentful Paint and
Time to Interactive
values from the Diagnostics section — paste these into the verdict field.
They make the score concrete and citeable.
⚠ Run each site three times and take the middle score —
PageSpeed results vary by ±5 points between runs due to server load variation.
Do all three runs within 5 minutes of each other.
Record the median.
⚡
Dimension 3 — Availability (20 pts)
Tool: UptimeRobot (free) · Setup: 30 min, then 30-day wait ·
🤖 Automatable
One-time setup (do this first, before anything else).
Go to
uptimerobot.com
and create a free account. The free tier allows 50 monitors checking every 5 minutes —
enough for all 24 sites.
Step 1.
For each site, click
Add New Monitor.
Set Monitor Type:
HTTP(s).
Paste the URL. Set check interval:
5 minutes.
Click Save.
Step 2.
Wait
30 days. UptimeRobot will send email alerts on downtime.
Check back after 30 days and note the uptime percentage for each site.
Step 3.
Convert uptime percentage to a score /20:
| 30-day Uptime % |
Score /20 |
Notes |
| 99.9% + | 20 | Under 44 min downtime/month |
| 99.0–99.9% | 16 | Under 7.2 hrs downtime/month |
| 97.0–99.0% | 12 | Up to ~22 hrs downtime/month |
| 90.0–97.0% | 8 | Frequent or extended outages |
| Below 90% | 4 | Unreliable — more than 72 hrs down |
| Site unreachable | 0 | Did not respond during monitoring window |
Important:
Some government sites block monitoring bots. If UptimeRobot repeatedly shows
"seems down" for a site you can clearly access in a browser, the site is blocking
the monitor. In that case, manually check the site once a week for 4 weeks and
estimate availability. Note this in the verdict field.
📱
Dimension 4 — Mobile Readiness (20 pts)
Tool: PageSpeed + Manual device check · Time: ~10 min/site ·
⚡ Partial — tool + human
Mobile scoring has two parts — automated (10 pts) and manual (10 pts).
Part A — Automated (10 pts):
Use the same PageSpeed Insights run from the Speed dimension.
Under
Diagnostics → Opportunities, check for these specific failures.
Deduct points as shown:
| PageSpeed flag |
Deduct |
| "Does not have a <meta name=viewport> tag" | −4 pts |
| "Tap targets are not sized appropriately" | −3 pts |
| "Text is too small to read" | −2 pts |
| "Content wider than screen" | −1 pt |
| No flags — clean mobile diagnostics | Full 10 pts |
Part B — Manual device check (10 pts):
Open the site on a real Android phone (mid-range preferred — Redmi, Realme, or Samsung M-series).
Use Chrome. Score each item below as pass (2 pts) or fail (0 pts):
- Homepage loads without horizontal scroll
- Main navigation is tappable without zooming
- The primary form (login, search, or application) is usable without zooming in
- Site does not prompt to download an app as a prerequisite to use it
- No "Best viewed in Internet Explorer" or "Use desktop mode" warnings
Record Part A + Part B scores in the verdict. Total mobile score = Part A + Part B.
🧭
Dimension 5 — Usability (20 pts)
Method: Human task testing · Time: ~20 min/site ·
👤 Human tester required
The tester must be someone who has
never used the site before.
Brief them on the task, start a timer, and observe — do not help them.
The standard task for each site tier:
- Central portals: Find and begin the most common citizen task
(e.g. on incometax.gov.in: reach the ITR filing login page;
on passportindia.gov.in: reach the appointment booking page;
on epfindia.gov.in: reach the member passbook)
- State portals: Find where to apply for an income certificate
or caste certificate
- Municipal portals: Find where to pay property tax online
Scoring rubric (20 pts total):
| Criterion |
Points |
How to score |
| Task reachable | 0 or 8 | 8 if tester reaches the task page; 0 if they give up or reach a dead end |
| Clicks to reach task | 0–6 | 1–2 clicks = 6 pts; 3–4 clicks = 4 pts; 5–6 = 2 pts; 7+ = 0 pts |
| Time to reach task | 0–4 | Under 1 min = 4 pts; 1–3 min = 2 pts; over 3 min = 0 pts |
| No broken links encountered | 0 or 2 | 2 if no 404 or dead ends; 0 if any encountered on the path |
Record: the exact task given, number of clicks,
time taken, tester's first name and occupation (for transparency),
and any notable observations. Paste a short summary into the site's verdict field.
⚠ Tester must be a genuine first-time user. Someone who has visited
a government portal before — even briefly — has unconscious familiarity that inflates
the score. Use a friend, family member, or colleague who does not regularly interact
with government websites. Ideally test with 2–3 different people and average.
Quick reference — entering scores into the page
Once you have scores, open
digital_governance.html in a text editor and find the
SITES
array. Each site has a
scores field in this order:
scores: [availability, speed, mobile, security, usability]
// Each value: 0–20, or null if not yet tested
// Example — Security + Speed done, rest pending:
scores: [null, 14, null, 18, null]
// Example — fully scored:
scores: [16, 14, 12, 18, 10]
The grade badge, score bars, and hero statistics update automatically.
Also update the verdict field with
your key findings, and change
lastTested to the month you tested (e.g.
'May 2026').