Critical Page is effectively empty
The page loads but has almost no visible text -- there is nothing here for you to read or use.
31 visible characters
How to fix it
Check the CMS/build for a rendering error and restore the page's real content.
http://www.cpt.ac.in · audited 3 days ago · checked 22 minutes ago
The page loads but has almost no visible text -- there is nothing here for you to read or use.
College — not yet confirmed whether government or government-aided — We have not found an official document that says which one it is, so we have not guessed. See all colleges
Not scored.


The page loads but has almost no visible text -- there is nothing here for you to read or use.
Browsers show a full-page "Your connection is not private" warning. Most people cannot get past it, so the site is effectively unreachable.
Your connection to this site is not encrypted at all -- anything you type or read can be seen or altered in transit, and modern browsers show a prominent warning.
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.
The security certificate will stop working soon, at which point the site will show the same "not private" warning as an already-expired one.
The page loads a script library with a publicly known security flaw, which could let an attacker interfere with the page in your browser.
Automated testing found accessibility problems likely to make parts of this page difficult to use for some visitors.
Some text is hard to read against its background, especially for visitors with low vision or in bright sunlight on a phone.
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 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.
Another website could embed this page invisibly and trick you into clicking something you did not mean to.
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.
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.
Some images are far larger than they need to be for how they are displayed, slowing the page down for no visible benefit.
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.
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.
A minor technical hardening header is missing; on its own this rarely affects you directly.
The page loads but has almost no visible text -- there is nothing here for you to read or use.
31 visible characters
Check the CMS/build for a rendering error and restore the page's real content.
Your connection to this site is not encrypted at all -- anything you type or read can be seen or altered in transit, and modern browsers show a prominent warning.
http://www.cpt.ac.in
Get a TLS certificate (NIC issues them free for .gov.in; Let's Encrypt for others) and serve the whole site over HTTPS.
Browsers show a full-page "Your connection is not private" warning. Most people cannot get past it, so the site is effectively unreachable.
certificate chain invalid, expired, or hostname mismatch
Renew the TLS certificate (NIC issues them free for .gov.in; Let's Encrypt for others) and turn on auto-renewal.
The security certificate will stop working soon, at which point the site will show the same "not private" warning as an already-expired one.
-46 days left
Renew the certificate now and set up auto-renewal so this stops recurring.
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.11.1, jquery-ui 1.9.2, bootstrap 3.3.5
Update the affected library to a version without the known vulnerability.
Reference: OWASP A06:2021 Vulnerable and Outdated Components
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 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.
Add a Strict-Transport-Security header once HTTPS is confirmed working sitewide.
Reference: OWASP Secure Headers
Another website could embed this page invisibly and trick you into clicking something you did not mean to.
Add an X-Frame-Options header (or a frame-ancestors directive in CSP).
Reference: OWASP Secure Headers
Automated testing found accessibility problems likely to make parts of this page difficult to use for some visitors.
2 serious violation(s)
Fix the serious-impact violations an accessibility scanner reports.
Reference: WCAG 2.1 AA
Some text is hard to read against its background, especially for visitors with low vision or in bright sunlight on a phone.
2 low-contrast element(s)
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
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
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.
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.
Add a Content-Security-Policy header, starting permissive and tightening it once nothing breaks.
Reference: OWASP Secure Headers
A minor technical hardening header is missing; on its own this rarely affects you directly.
Add "X-Content-Type-Options: nosniff".
Reference: OWASP Secure Headers
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.
Add a Referrer-Policy header, e.g. "strict-origin-when-cross-origin".
Reference: OWASP Secure Headers
Smaller accessibility issues were found; each on its own is unlikely to block anyone, but they add up.
1 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.
6 console error(s): Failed to load resource: the server responded with a status of 404 (Not Found)
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
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).
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.
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.