Kerala Web Watch
Search

Irrigation Department

https://irrigation.kerala.gov.in · audited yesterday · checked 11 minutes ago

Needs work
Overall score▲ 4 vs last week

Six checks

  • Security60
  • Accessibility22
  • Content62
  • Government guidelines36
  • Performance71
  • Identity96

Screenshot

Desktop screenshot of Irrigation DepartmentMobile screenshot of Irrigation Department

What to fix first

  1. Grade 3 — Fix soon Critical accessibility violations

    Automated testing found serious accessibility problems that are very likely to block some visitors, such as screen-reader users, from using this page at all.

  2. Grade 3 — Fix soon Page language is missing or wrong

    A screen reader needs to know what language the page is in to pronounce it correctly -- without this, a Malayalam page read aloud in an English voice is unintelligible.

  3. Grade 3 — Fix soon "Last updated" date is missing or very old

    There's no visible sign of when this page was last reviewed, or the date shown is over a year old -- you can't tell whether the information is still current.

  4. Grade 3 — Fix soon Secure page loads insecure content

    The page is served securely but pulls in some scripts, styles or images over an insecure connection, weakening the protection the padlock is supposed to mean.

  5. Grade 3 — Fix soon Uses a JavaScript library with a known vulnerability

    The page loads a script library with a publicly known security flaw, which could let an attacker interfere with the page in your browser.

  6. Grade 4 — Plan a fix Images missing alt text

    Someone using a screen reader hears nothing useful where an image is -- if it conveys information, that information is simply lost to them.

  7. Grade 4 — Plan a fix Serious accessibility violations

    Automated testing found accessibility problems likely to make parts of this page difficult to use for some visitors.

  8. Grade 4 — Plan a fix Text contrast is too low

    Some text is hard to read against its background, especially for visitors with low vision or in bright sunlight on a phone.

  9. Grade 4 — Plan a fix Uses obsolete web technology

    This page uses old technology (Flash, Java applets, <marquee>/<blink>, frames) that modern browsers no longer support at all, so part of the page may simply not work.

  10. Grade 4 — Plan a fix No Accessibility Statement

    There is no page explaining the site's accessibility commitments or how to report an accessibility problem.

  11. Grade 4 — Plan a fix No last-updated date shown

    There is no visible date telling you when the site (not just one page) was last updated.

  12. Grade 4 — Plan a fix No content-ownership statement

    There is no footer statement saying which department owns this content and who built/hosts the site, making it harder to tell an official site from an impersonation.

  13. Grade 4 — Plan a fix No sitemap page

    There is no page listing everything the site contains, making it harder to find something that isn't in the main menu.

  14. Grade 4 — Plan a fix Main content is slow to appear

    The largest visible element on the page (usually a heading or image) takes a long time to show up, which feels like the page is stuck.

  15. Grade 4 — Plan a fix Buttons/links too small or close together on mobile

    On a phone, some links or buttons are small or crowded enough that it is easy to tap the wrong one.

  16. Grade 5 — Minor Homepage is very large to download

    The homepage transfers an unusually large amount of data, which is slow and can be expensive on a limited mobile data plan.

  17. Grade 5 — Minor Minor accessibility issues

    Smaller accessibility issues were found; each on its own is unlikely to block anyone, but they add up.

  18. Grade 5 — Minor Heading structure is missing or broken

    Screen-reader users often jump between sections by heading level; a missing top-level heading or skipped levels make the page harder to navigate that way.

  19. Grade 5 — Minor JavaScript errors on load

    The page's own code fails partway through loading, which can silently break some feature on the page without any visible error message.

  20. Grade 5 — Minor No meta description

    Search engines have nothing useful to show as a summary of this page in search results.

  21. Grade 5 — Minor No Disclaimer

    There is no disclaimer covering the accuracy or official status of the information on this site.

  22. Grade 5 — Minor No feedback mechanism

    There is no way to send feedback about the site itself.

  23. Grade 5 — Minor No Help page

    There is no page explaining how to use the site itself (navigation, search, common tasks).

  24. Grade 5 — Minor No Hyperlinking Policy

    There is no statement about how this site handles links to and from other websites.

  25. Grade 5 — Minor No Screen Reader Access page

    There is no page pointing screen-reader users to compatible software or usage tips for this site.

  26. Grade 5 — Minor No Terms & Conditions / Terms of Use

    There is no page setting out the terms for using this site.

  27. Grade 5 — Minor No sitemap.xml

    This helps search engines find every page on the site; without it, some pages may be harder to discover via search.

  28. Grade 5 — Minor Images are uncompressed or oversized

    Some images are far larger than they need to be for how they are displayed, slowing the page down for no visible benefit.

Open issues · 29

High

High Secure page loads insecure content

The page is served securely but pulls in some scripts, styles or images over an insecure connection, weakening the protection the padlock is supposed to mean.

href="http://cprcs.kerala.gov.in/"

How to fix it

Change every http:// resource reference on the page to https://.

High Uses a JavaScript library with a known vulnerability

The page loads a script library with a publicly known security flaw, which could let an attacker interfere with the page in your browser.

underscore.js 1.13.7

How to fix it & reference

Update the affected library to a version without the known vulnerability.

Reference: OWASP A06:2021 Vulnerable and Outdated Components

High Critical accessibility violations

Automated testing found serious accessibility problems that are very likely to block some visitors, such as screen-reader users, from using this page at all.

13 critical violation(s)

How to fix it & reference

Run an accessibility scanner (e.g. axe) and fix every critical-impact violation it reports first.

Reference: WCAG 2.1 AA

High Page language is missing or wrong

A screen reader needs to know what language the page is in to pronounce it correctly -- without this, a Malayalam page read aloud in an English voice is unintelligible.

<html lang="en"> vs. 51% Malayalam content

How to fix it & reference

Set <html lang="ml"> (or the correct language) so it matches what the page actually contains.

Reference: WCAG 2.1 SC 3.1.1

High "Last updated" date is missing or very old

There's no visible sign of when this page was last reviewed, or the date shown is over a year old -- you can't tell whether the information is still current.

no "last updated" date found

How to fix it & reference

Show a genuine last-reviewed/updated date on every content page, and actually keep it current.

Reference: GIGW 3.0

Medium

Medium Serious accessibility violations

Automated testing found accessibility problems likely to make parts of this page difficult to use for some visitors.

17 serious violation(s)

How to fix it & reference

Fix the serious-impact violations an accessibility scanner reports.

Reference: WCAG 2.1 AA

Medium Images missing alt text

Someone using a screen reader hears nothing useful where an image is -- if it conveys information, that information is simply lost to them.

12 image(s) missing alt text

How to fix it & reference

Add descriptive alt text to every meaningful image; use alt="" only for purely decorative ones.

Reference: WCAG 2.1 SC 1.1.1

Medium Text contrast is too low

Some text is hard to read against its background, especially for visitors with low vision or in bright sunlight on a phone.

2 low-contrast element(s)

How to fix it & reference

Darken text or lighten backgrounds until the contrast ratio meets WCAG AA (4.5:1 for normal text).

Reference: WCAG 2.1 SC 1.4.3

Medium Uses obsolete web technology

This page uses old technology (Flash, Java applets, <marquee>/<blink>, frames) that modern browsers no longer support at all, so part of the page may simply not work.

<marquee

How to fix it

Replace Flash/Java-applet content and framesets with modern HTML/CSS/JS equivalents.

Medium No sitemap page

There is no page listing everything the site contains, making it harder to find something that isn't in the main menu.

How to fix it & reference

Add a human-readable sitemap page linking every major section.

Reference: GIGW 3.0

Medium No Accessibility Statement

There is no page explaining the site's accessibility commitments or how to report an accessibility problem.

How to fix it & reference

Publish an Accessibility Statement with a way to report barriers.

Reference: GIGW 3.0

Medium No content-ownership statement

There is no footer statement saying which department owns this content and who built/hosts the site, making it harder to tell an official site from an impersonation.

How to fix it & reference

Add a footer statement: "Content owned by <department> — Designed, developed & hosted by <agency>".

Reference: GIGW 3.0

Medium No last-updated date shown

There is no visible date telling you when the site (not just one page) was last updated.

How to fix it & reference

Show a site-wide last-updated date, typically in the footer.

Reference: GIGW 3.0

Medium Main content is slow to appear

The largest visible element on the page (usually a heading or image) takes a long time to show up, which feels like the page is stuck.

21015.661500000002ms

How to fix it

Optimise the largest above-the-fold image/element: compress it, size it correctly, and load it early.

Medium Homepage is very large to download

The homepage transfers an unusually large amount of data, which is slow and can be expensive on a limited mobile data plan.

6.0MB

How to fix it

Compress images, remove unused scripts/styles, and enable gzip/br compression on the server.

Medium Buttons/links too small or close together on mobile

On a phone, some links or buttons are small or crowded enough that it is easy to tap the wrong one.

How to fix it

Increase the tap-target size and spacing for interactive elements on small screens.

Low

Low Minor accessibility issues

Smaller accessibility issues were found; each on its own is unlikely to block anyone, but they add up.

3 moderate/minor violation(s)

How to fix it & reference

Work through the moderate/minor findings from an accessibility scanner as time allows.

Reference: WCAG 2.1 AA

Low Heading structure is missing or broken

Screen-reader users often jump between sections by heading level; a missing top-level heading or skipped levels make the page harder to navigate that way.

no <h1>

How to fix it & reference

Add one <h1> per page and use heading levels in order without skipping.

Reference: WCAG 2.1 SC 1.3.1

Low No meta description

Search engines have nothing useful to show as a summary of this page in search results.

How to fix it

Add a concise <meta name="description"> summarising each page.

Low JavaScript errors on load

The page's own code fails partway through loading, which can silently break some feature on the page without any visible error message.

4 console error(s): Connecting to 'https://spreadsheets.google.com/feeds/cells/1AC1uazMT9dyPgbzg9l-w-Eg_OGBIpBuv22LHy98VFIs/1/public/full?alt=json' violates the following Content Security Policy directive: "connect-src 'self' https://docs.google.com". The action has been blocked.

How to fix it

Open the browser's developer console on this page and fix the reported script errors.

Low No feedback mechanism

There is no way to send feedback about the site itself.

How to fix it & reference

Add a feedback form or a dedicated feedback email address.

Reference: GIGW 3.0

Low No Terms & Conditions / Terms of Use

There is no page setting out the terms for using this site.

How to fix it & reference

Publish a Terms of Use page.

Reference: GIGW 3.0

Low No Disclaimer

There is no disclaimer covering the accuracy or official status of the information on this site.

How to fix it & reference

Publish a Disclaimer page.

Reference: GIGW 3.0

Low No Screen Reader Access page

There is no page pointing screen-reader users to compatible software or usage tips for this site.

How to fix it & reference

Publish a Screen Reader Access page (GIGW's traditional term for this).

Reference: GIGW 3.0

Low No Help page

There is no page explaining how to use the site itself (navigation, search, common tasks).

How to fix it & reference

Publish a Help page.

Reference: GIGW 3.0

Low Images are uncompressed or oversized

Some images are far larger than they need to be for how they are displayed, slowing the page down for no visible benefit.

How to fix it

Resize images to their display dimensions and compress them (WebP/AVIF where possible).

Low No sitemap.xml

This helps search engines find every page on the site; without it, some pages may be harder to discover via search.

sitemap.xml returned 404

How to fix it

Generate and serve a sitemap.xml, and reference it from robots.txt.

Info

Info No state/national emblem shown

The site does not display the state or national emblem that citizens usually look for to help recognise an official government site.

How to fix it & reference

Display the appropriate emblem, used correctly per government branding guidelines.

Reference: GIGW 3.0

50 checks passed
  • Hostname does not resolve
  • Server did not respond
  • Page does not load successfully
  • Site redirects to an unrelated domain
  • Domain shows a "for sale" / parking page
  • Server's default page is showing, not the site
  • Page is effectively empty
  • "Under construction" page only
  • Server is slow to start responding
  • Blocked from where we check from
  • Not served over HTTPS at all
  • Plain http:// does not redirect to https://
  • HTTPS certificate is invalid or expired
  • Certificate is about to expire
  • Only an old, insecure TLS version is supported
  • No HSTS header
  • No Content-Security-Policy header
  • No clickjacking protection
  • No X-Content-Type-Options header
  • No Referrer-Policy header
  • Server discloses exact software versions
  • Links to suspicious outside websites
  • Form fields without labels
  • No "skip to content" link
  • Possible keyboard-navigation trap
  • Lighthouse accessibility score
  • Lighthouse performance score
  • Page layout jumps around while loading
  • Not set up for mobile screens
  • Placeholder text left on the live site
  • Uses a non-Unicode Malayalam font
  • "Best viewed in..." notice
  • Broken internal links
  • Linked PDFs are missing
  • Broken images
  • No Malayalam version available
  • Page title is missing or generic
  • No favicon
  • No "Contact Us" page
  • No Privacy Policy
  • No Copyright Policy
  • No RTI / Public Information Officer details
  • No site search
  • Not on an official government domain
  • No robots.txt
  • Missing pages return "200 OK" instead of a proper error
  • No canonical link tag
  • Missing UTF-8 charset or HTML5 doctype
  • Running old, unsupported software
  • Loads third-party trackers

Uptime — last 90 days

Technical facts

Final URL
https://irrigation.kerala.gov.in
Server
nginx
Content management system
Not detected
Security certificate
Valid — expires in 176 days (May 13 23:59:59 2027 GMT)
Domain
kerala.gov.in — a government (.gov.in/.nic.in-class) domain
Platform
None — independently hosted

Actions

See all sites in Thiruvananthapuram →