Kerala Web Watch
Search

Raj Bhavan Kerala · രാജ്ഭവൻ കേരളം

https://rajbhavan.kerala.gov.in · audited 13 days ago · checked 13 minutes ago

Needs work
Overall scoreno change

Six checks

  • Security28
  • Accessibility52
  • Content52
  • Government guidelines30
  • Performance86
  • Identity92

Screenshot

Desktop screenshot of Raj Bhavan KeralaMobile screenshot of Raj Bhavan Kerala

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 "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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. Grade 4 — Plan a fix Page title is missing or generic

    The browser tab/bookmark/search-result title just says something like "Home" or "Untitled" instead of naming the actual organisation or page.

  9. 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.

  10. 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.

  11. 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.

  12. Grade 4 — Plan a fix No Privacy Policy

    There is no statement telling you what personal information this site collects about you or what it does with it.

  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 No HSTS header

    The site does not tell browsers to always use the secure version, so a network attacker can sometimes still trick a browser into the insecure one.

  16. Grade 4 — Plan a fix No clickjacking protection

    Another website could embed this page invisibly and trick you into clicking something you did not mean to.

  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 Broken images

    Some images fail to load, leaving broken-image icons on the page.

  20. 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.

  21. Grade 5 — Minor No Copyright Policy

    There is no statement about who owns the content on this site and how it may be reused.

  22. Grade 5 — Minor No Disclaimer

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

  23. Grade 5 — Minor No Hyperlinking Policy

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

  24. 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.

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

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

  26. 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.

  27. Grade 5 — Minor www and non-www versions are inconsistent

    Depending on whether you type "www." or not, you might get a different result than expected instead of one consistently redirecting to the other.

  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.

  29. Grade 5 — Minor No Content-Security-Policy header

    This is a technical defence-in-depth measure most visitors will never notice missing; it makes some attacks harder for the site to be tricked into if it ever has a bug.

  30. Grade 5 — Minor No Referrer-Policy header

    Without this, the full address of the page you came from (which can include personal details in a URL) may be leaked to other sites you click through to.

  31. Grade 5 — Minor No X-Content-Type-Options header

    A minor technical hardening header is missing; on its own this rarely affects you directly.

Open issues · 33

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://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,400italic,600,600italic,700,700italic,800,800italic"

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.

jquery 1.12.4

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.

2 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 "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 No HSTS header

The site does not tell browsers to always use the secure version, so a network attacker can sometimes still trick a browser into the insecure one.

How to fix it & reference

Add a Strict-Transport-Security header once HTTPS is confirmed working sitewide.

Reference: OWASP Secure Headers

Medium No clickjacking protection

Another website could embed this page invisibly and trick you into clicking something you did not mean to.

How to fix it & reference

Add an X-Frame-Options header (or a frame-ancestors directive in CSP).

Reference: OWASP Secure Headers

Medium Serious accessibility violations

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

12 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.

2 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 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 Page title is missing or generic

The browser tab/bookmark/search-result title just says something like "Home" or "Untitled" instead of naming the actual organisation or page.

generic title "Home"

How to fix it

Give every page a specific, descriptive <title>.

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 Privacy Policy

There is no statement telling you what personal information this site collects about you or what it does with it.

How to fix it & reference

Publish a Privacy Policy page and link it from the footer of every page.

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.

13863.2275ms

How to fix it

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

Low

Low No Content-Security-Policy header

This is a technical defence-in-depth measure most visitors will never notice missing; it makes some attacks harder for the site to be tricked into if it ever has a bug.

How to fix it & reference

Add a Content-Security-Policy header, starting permissive and tightening it once nothing breaks.

Reference: OWASP Secure Headers

Low No X-Content-Type-Options header

A minor technical hardening header is missing; on its own this rarely affects you directly.

How to fix it & reference

Add "X-Content-Type-Options: nosniff".

Reference: OWASP Secure Headers

Low No Referrer-Policy header

Without this, the full address of the page you came from (which can include personal details in a URL) may be leaked to other sites you click through to.

How to fix it & reference

Add a Referrer-Policy header, e.g. "strict-origin-when-cross-origin".

Reference: OWASP Secure Headers

Low Minor accessibility issues

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

11 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>, heading levels skipped

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 Broken images

Some images fail to load, leaving broken-image icons on the page.

1 broken image(s)

How to fix it

Fix or remove the broken image references.

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.

5 console error(s): Mixed Content: The page at 'https://lokbhavan.kerala.gov.in/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,400italic,600,600italic,700,700italic,800,800italic'. This request has been blocked; the content must be served over HTTPS.

How to fix it

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

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 Copyright Policy

There is no statement about who owns the content on this site and how it may be reused.

How to fix it & reference

Publish a Copyright Policy 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 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 www and non-www versions are inconsistent

Depending on whether you type "www." or not, you might get a different result than expected instead of one consistently redirecting to the other.

How to fix it

Pick one canonical form and make the other redirect to it.

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 canonical link tag

A technical signal to search engines about which URL is the "real" one for this page is missing; it rarely affects what you see directly.

How to fix it

Add a <link rel="canonical"> to each page pointing at its preferred URL.

Info Loads third-party trackers

This page loads scripts from outside companies (analytics, social-media widgets) that can track your visit, shown here for transparency rather than as a pass/fail problem.

https://www.googletagmanager.com/gtag/js?id=G-FH946TSYK5&amp;cx=c&amp;gtm=4e6b41, https://www.googletagmanager.com/gtag/js?id=UA-103783083-7

How to fix it

Consider whether each third-party script is necessary, and disclose tracking in the Privacy Policy if kept.

47 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
  • Server discloses exact software versions
  • Links to suspicious outside websites
  • Page language is missing or wrong
  • Text contrast is too low
  • 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
  • Homepage is very large to download
  • Not set up for mobile screens
  • Buttons/links too small or close together on mobile
  • Footer copyright year is old
  • Placeholder text left on the live site
  • Uses a non-Unicode Malayalam font
  • "Best viewed in..." notice
  • Broken internal links
  • Linked PDFs are missing
  • No meta description
  • No favicon
  • No "Contact Us" page
  • No feedback mechanism
  • No Help page
  • No RTI / Public Information Officer details
  • No site search
  • No state/national emblem shown
  • Not on an official government domain
  • No robots.txt
  • Missing pages return "200 OK" instead of a proper error
  • Missing UTF-8 charset or HTML5 doctype
  • Running old, unsupported software

Uptime — last 90 days

Technical facts

Final URL
https://lokbhavan.kerala.gov.in/
Server
Apache
Content management system
Not detected
Security certificate
Valid — expires in 52 days (Jan 10 13:30:46 2027 GMT)
Domain
kerala.gov.in — a government (.gov.in/.nic.in-class) domain
Platform
None — independently hosted

Actions

See all sites in General Administration →

See all sites in Thiruvananthapuram →