Kerala Web Watch
Search

Kerala Police

https://keralapolice.gov.in · audited 3 hours ago · checked 12 minutes ago

Needs work
Overall score▲ 2 vs last week

Six checks

  • Security50
  • Accessibility60
  • Content46
  • Government guidelines26
  • Performance66
  • Identity96

Screenshot

Desktop screenshot of Kerala PoliceMobile screenshot of Kerala Police

What to fix first

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

  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 Uses a non-Unicode Malayalam font

    This page uses an old-style Malayalam font (like ML-TTKarthika or ISM/Matweb) that only displays correctly if you happen to have that exact font installed -- for everyone else, the text is unreadable garbled characters.

  4. Grade 3 — Fix soon No "Contact Us" page

    There is no clear way to find out how to contact this office by phone, email or post.

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

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

  7. Grade 4 — Plan a fix Broken internal links

    Some links on this site lead to pages that no longer exist or time out, which is frustrating and can hide information you were looking for.

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

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

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

  14. Grade 4 — Plan a fix 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.

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

  16. Grade 5 — Minor Minor accessibility issues

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

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

  18. Grade 5 — Minor Possible keyboard-navigation trap

    Some interactive elements may be unreachable or invisible to someone who navigates by keyboard alone rather than a mouse.

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

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

  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 Help page

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

  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 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://ptc.keralapolice.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.

swiper 11.2.10, jquery-validation 1.19.1

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

High Uses a non-Unicode Malayalam font

This page uses an old-style Malayalam font (like ML-TTKarthika or ISM/Matweb) that only displays correctly if you happen to have that exact font installed -- for everyone else, the text is unreadable garbled characters.

ml-

How to fix it

Switch to a Unicode Malayalam font (e.g. Manjari, Noto Sans Malayalam) so the text reads correctly for everyone, with no font install required.

High No "Contact Us" page

There is no clear way to find out how to contact this office by phone, email or post.

How to fix it & reference

Add a Contact Us page with a real phone number, email and postal address.

Reference: GIGW 3.0

Medium

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.

14 serious violation(s)

How to fix it & reference

Fix the serious-impact violations an accessibility scanner reports.

Reference: WCAG 2.1 AA

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.

36312.308000000005ms

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.

9.4MB

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.

31 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 Possible keyboard-navigation trap

Some interactive elements may be unreachable or invisible to someone who navigates by keyboard alone rather than a mouse.

tabindex="-1" alongside outline:none

How to fix it & reference

Make sure every interactive element can be reached and clearly seen with the keyboard's Tab key alone.

Reference: WCAG 2.1 SC 2.1.1

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.

20 console error(s): Failed to load resource: the server responded with a status of 400 ()

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 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 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-FXT3GHQP8K&amp;cx=c&amp;gtm=4e6bh1, https://www.googletagmanager.com/gtag/js?id=G-EHGEHQFVXZ&amp;cx=c&amp;gtm=4e6bh1, https://www.googletagmanager.com/gtm.js?id=GTM-5XH2XTV, https://www.googletagmanager.com/gtag/js?id=G-FXT3GHQP8K

How to fix it

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

51 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 X-Content-Type-Options header
  • No Referrer-Policy header
  • Server discloses exact software versions
  • Links to suspicious outside websites
  • Critical accessibility violations
  • Images missing alt text
  • Text contrast is too low
  • Form fields without labels
  • No "skip to content" link
  • Lighthouse accessibility score
  • Lighthouse performance score
  • Page layout jumps around while loading
  • Not set up for mobile screens
  • News/announcements section is stale
  • Placeholder text left on the live site
  • Uses obsolete web technology
  • "Best viewed in..." notice
  • Linked PDFs are missing
  • Broken images
  • No Malayalam version available
  • Page title is missing or generic
  • No meta description
  • No favicon
  • No feedback mechanism
  • No sitemap page
  • No Privacy Policy
  • 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://keralapolice.gov.in
Server
—
Content management system
Not detected
Security certificate
Valid — expires in 51 days (Jan 8 23:59:59 2027 GMT)
Domain
keralapolice.gov.in — a government (.gov.in/.nic.in-class) domain
Platform
None — independently hosted

Actions

See all sites in Thiruvananthapuram →