Kerala Web Watch
Search

Kerala Forest Research Institute (KFRI)

https://www.kfri.res.in · audited 2 hours ago · checked 11 minutes ago

Needs work

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

Overall scoreno change

Six checks

  • Security68
  • Accessibility62
  • Content32
  • Government guidelines22
  • Performance81
  • Identity96

Screenshot

Desktop screenshot of Kerala Forest Research Institute (KFRI)Mobile screenshot of Kerala Forest Research Institute (KFRI)

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

  5. Grade 4 — Plan a fix Footer copyright year is old

    The copyright year in the footer is at least two years out of date, a small but visible sign nobody has touched this site recently.

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

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

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

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

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

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

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

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

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

  19. Grade 5 — Minor No meta description

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

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

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

  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 · 32

High

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.

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

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

20 serious violation(s)

How to fix it & reference

Fix the serious-impact violations an accessibility scanner reports.

Reference: WCAG 2.1 AA

Medium Footer copyright year is old

The copyright year in the footer is at least two years out of date, a small but visible sign nobody has touched this site recently.

copyright year 2024

How to fix it

Update the footer copyright year, ideally to update automatically each year.

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

10598.488000000001ms

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.

5.8MB

How to fix it

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

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.

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

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

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

How to fix it

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

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

Uptime — last 90 days

Technical facts

Final URL
https://www.kfri.res.in
Server
—
Content management system
Not detected
Security certificate
Valid — expires in 77 days (Feb 4 16:53:38 2027 GMT)
Domain
kfri.res.in — a government (.gov.in/.nic.in-class) domain
Platform
None — independently hosted

Actions

See all sites in Thrissur →