Critical Page is effectively empty
The page loads but has almost no visible text -- there is nothing here for you to read or use.
0 visible characters
How to fix it
Check the CMS/build for a rendering error and restore the page's real content.
https://revenue.kerala.gov.in · audited last month · checked 18 minutes ago
The page loads but has almost no visible text -- there is nothing here for you to read or use.
Not scored.


The page loads but has almost no visible text -- there is nothing here for you to read or use.
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.
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.
There is no clear way to find out how to contact this office by phone, email or post.
You cannot find who to contact to file a Right to Information request with this office, which is a legal right, not a courtesy.
Someone using a screen reader hears nothing useful where an image is -- if it conveys information, that information is simply lost to them.
Automated testing found accessibility problems likely to make parts of this page difficult to use for some visitors.
This citizen-facing site has no Malayalam version or toggle, which shuts out anyone more comfortable reading Malayalam than English.
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.
There is no page explaining the site's accessibility commitments or how to report an accessibility problem.
There is no visible date telling you when the site (not just one page) was last updated.
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.
There is no statement telling you what personal information this site collects about you or what it does with it.
There is no page listing everything the site contains, making it harder to find something that isn't in the main menu.
On a phone, some links or buttons are small or crowded enough that it is easy to tap the wrong one.
The page takes an unusually long time to even start loading, before you see anything at all.
The homepage transfers an unusually large amount of data, which is slow and can be expensive on a limited mobile data plan.
Smaller accessibility issues were found; each on its own is unlikely to block anyone, but they add up.
The page's own code fails partway through loading, which can silently break some feature on the page without any visible error message.
There is no statement about who owns the content on this site and how it may be reused.
There is no disclaimer covering the accuracy or official status of the information on this site.
There is no way to send feedback about the site itself.
There is no page explaining how to use the site itself (navigation, search, common tasks).
There is no statement about how this site handles links to and from other websites.
There is no page pointing screen-reader users to compatible software or usage tips for this site.
There is no way to search this site directly; you have to browse the menu to find anything.
There is no page setting out the terms for using this site.
Without a declared UTF-8 charset, Malayalam and other non-English text can sometimes render as garbled characters in some browsers.
This is a minor technical hygiene item about how search engines crawl the site; it rarely affects what you see directly.
This helps search engines find every page on the site; without it, some pages may be harder to discover via search.
Depending on whether you type "www." or not, you might get a different result than expected instead of one consistently redirecting to the other.
Text and buttons shift position as the page finishes loading, which can make you tap the wrong thing.
Some images are far larger than they need to be for how they are displayed, slowing the page down for no visible benefit.
The page loads but has almost no visible text -- there is nothing here for you to read or use.
0 visible characters
Check the CMS/build for a rendering error and restore the page's real content.
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)
Run an accessibility scanner (e.g. axe) and fix every critical-impact violation it reports first.
Reference: WCAG 2.1 AA
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
Show a genuine last-reviewed/updated date on every content page, and actually keep it current.
Reference: GIGW 3.0
There is no clear way to find out how to contact this office by phone, email or post.
Add a Contact Us page with a real phone number, email and postal address.
Reference: GIGW 3.0
You cannot find who to contact to file a Right to Information request with this office, which is a legal right, not a courtesy.
Publish the designated Public Information Officer's name, address and contact details, and how to file an RTI request.
Reference: RTI Act 2005 s.4
The page takes an unusually long time to even start loading, before you see anything at all.
3533ms
Investigate server/hosting performance (database queries, PHP-FPM/worker limits, an undersized shared-hosting plan) and add caching if the content changes rarely.
Automated testing found accessibility problems likely to make parts of this page difficult to use for some visitors.
14 serious violation(s)
Fix the serious-impact violations an accessibility scanner reports.
Reference: WCAG 2.1 AA
Someone using a screen reader hears nothing useful where an image is -- if it conveys information, that information is simply lost to them.
6 image(s) missing alt text
Add descriptive alt text to every meaningful image; use alt="" only for purely decorative ones.
Reference: WCAG 2.1 SC 1.1.1
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.
<frameset
Replace Flash/Java-applet content and framesets with modern HTML/CSS/JS equivalents.
This citizen-facing site has no Malayalam version or toggle, which shuts out anyone more comfortable reading Malayalam than English.
Malayalam ratio 0.00, no language toggle found
Add a Malayalam translation (or at minimum the key citizen-facing pages) with an easy language toggle.
There is no page listing everything the site contains, making it harder to find something that isn't in the main menu.
Add a human-readable sitemap page linking every major section.
Reference: GIGW 3.0
There is no statement telling you what personal information this site collects about you or what it does with it.
Publish a Privacy Policy page and link it from the footer of every page.
Reference: GIGW 3.0
There is no page explaining the site's accessibility commitments or how to report an accessibility problem.
Publish an Accessibility Statement with a way to report barriers.
Reference: GIGW 3.0
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.
Add a footer statement: "Content owned by <department> — Designed, developed & hosted by <agency>".
Reference: GIGW 3.0
There is no visible date telling you when the site (not just one page) was last updated.
Show a site-wide last-updated date, typically in the footer.
Reference: GIGW 3.0
The homepage transfers an unusually large amount of data, which is slow and can be expensive on a limited mobile data plan.
5.7MB
Compress images, remove unused scripts/styles, and enable gzip/br compression on the server.
On a phone, some links or buttons are small or crowded enough that it is easy to tap the wrong one.
Increase the tap-target size and spacing for interactive elements on small screens.
Smaller accessibility issues were found; each on its own is unlikely to block anyone, but they add up.
12 moderate/minor violation(s)
Work through the moderate/minor findings from an accessibility scanner as time allows.
Reference: WCAG 2.1 AA
The page's own code fails partway through loading, which can silently break some feature on the page without any visible error message.
3 console error(s): Chart is not defined
Open the browser's developer console on this page and fix the reported script errors.
There is no way to send feedback about the site itself.
Add a feedback form or a dedicated feedback email address.
Reference: GIGW 3.0
There is no page setting out the terms for using this site.
Publish a Terms of Use page.
Reference: GIGW 3.0
There is no statement about who owns the content on this site and how it may be reused.
Publish a Copyright Policy page.
Reference: GIGW 3.0
There is no statement about how this site handles links to and from other websites.
Publish a Hyperlinking Policy page.
Reference: GIGW 3.0
There is no disclaimer covering the accuracy or official status of the information on this site.
Publish a Disclaimer page.
Reference: GIGW 3.0
There is no page pointing screen-reader users to compatible software or usage tips for this site.
Publish a Screen Reader Access page (GIGW's traditional term for this).
Reference: GIGW 3.0
There is no page explaining how to use the site itself (navigation, search, common tasks).
Publish a Help page.
Reference: GIGW 3.0
There is no way to search this site directly; you have to browse the menu to find anything.
Add a site search facility.
Reference: GIGW 3.0
Text and buttons shift position as the page finishes loading, which can make you tap the wrong thing.
0.26
Reserve space (width/height) for images and ads before they load, instead of letting them push content around.
Some images are far larger than they need to be for how they are displayed, slowing the page down for no visible benefit.
Resize images to their display dimensions and compress them (WebP/AVIF where possible).
Depending on whether you type "www." or not, you might get a different result than expected instead of one consistently redirecting to the other.
Pick one canonical form and make the other redirect to it.
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
Add a robots.txt that at least allows normal crawling.
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
Generate and serve a sitemap.xml, and reference it from robots.txt.
Without a declared UTF-8 charset, Malayalam and other non-English text can sometimes render as garbled characters in some browsers.
missing HTML5 doctype
Add <!DOCTYPE html> and a UTF-8 charset declaration to every page.
The site does not display the state or national emblem that citizens usually look for to help recognise an official government site.
Display the appropriate emblem, used correctly per government branding guidelines.
Reference: GIGW 3.0
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.
Add a <link rel="canonical"> to each page pointing at its preferred URL.
Not enough score history yet to chart a trend.