Kerala Web Watch
Search

Forest and Wild Life Department

https://forest.kerala.gov.in · audited 3 hours ago · checked 8 minutes ago

The server responded, but with an error instead of the page, or a chain of redirects that never arrives anywhere.

Down

The most recent attempt to fully audit this site didn't finish (3 hours ago) — the scores and issues below, if any, are from the last audit that did complete.

Overall score▲ 1 vs last week

Six checks

Not scored.

Screenshot

Desktop screenshot of Forest and Wild Life DepartmentMobile screenshot of Forest and Wild Life Department

What to fix first

  1. Grade 2 — Act now: citizens cannot use the site Page does not load successfully

    The server responded, but with an error instead of the page, or a chain of redirects that never arrives anywhere.

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

  3. Grade 3 — Fix soon 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.

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

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

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

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

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

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

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

  11. Grade 4 — Plan a fix Form fields without labels

    A screen reader cannot tell you what a form field is for if it has no associated label, making forms hard or impossible to fill in.

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

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

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

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

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

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

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

  19. Grade 5 — Minor Minor accessibility issues

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

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

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

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

  23. Grade 5 — Minor No favicon

    The site has no small icon shown in browser tabs and bookmarks, a minor but very visible polish gap.

  24. Grade 5 — Minor No meta description

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

  25. Grade 5 — Minor No feedback mechanism

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

  26. Grade 5 — Minor No site search

    There is no way to search this site directly; you have to browse the menu to find anything.

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

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

  28. Grade 5 — Minor No robots.txt

    This is a minor technical hygiene item about how search engines crawl the site; it rarely affects what you see directly.

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

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

Open issues · 30

Critical

Critical Page does not load successfully

The server responded, but with an error instead of the page, or a chain of redirects that never arrives anywhere.

final response was 503

How to fix it

Check the server logs for the error status this request returned, and fix or shorten any redirect chain.

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.

src="http://localhost/kf/wp-content/uploads/2023/11/videobg.mp4"

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.

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

8 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

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

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.

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

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

1 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 Form fields without labels

A screen reader cannot tell you what a form field is for if it has no associated label, making forms hard or impossible to fill in.

1 form control(s) without a label

How to fix it & reference

Give every form control a <label> (or aria-label) that describes what to enter.

Reference: WCAG 2.1 SC 4.1.2

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

36995.83625000001ms

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

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 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 Minor accessibility issues

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

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

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 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 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 No favicon

The site has no small icon shown in browser tabs and bookmarks, a minor but very visible polish gap.

How to fix it

Add a favicon.ico (or modern equivalent) to the site.

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.

17 console error(s): Failed to load resource: the server responded with a status of 503 (Service Temporarily Unavailable)

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 site search

There is no way to search this site directly; you have to browse the menu to find anything.

How to fix it & reference

Add a site search facility.

Reference: GIGW 3.0

Low No robots.txt

This is a minor technical hygiene item about how search engines crawl the site; it rarely affects what you see directly.

robots.txt returned 503

How to fix it

Add a robots.txt that at least allows normal crawling.

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 503

How to fix it

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

Uptime — last 90 days

Technical facts

Final URL
—
Server
—
Content management system
Not detected
Security certificate
—
Domain
—
Platform
None — independently hosted

Actions

See all sites in Thiruvananthapuram →