Website review, no card needed
collegedekho.com website review
Visit site (opens in a new tab)Reviewed 30 October 202633 issues · 82 checks
This review found 33 issues worth fixing on collegedekho.com, 13 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 223 ms |
| May 16, 2026 | 224 ms |
| May 23, 2026 | 226 ms |
| May 30, 2026 | 229 ms |
| Jun 6, 2026 | 232 ms |
| Jun 13, 2026 | 237 ms |
| Jun 20, 2026 | 232 ms |
| Jun 27, 2026 | 219 ms |
| Jul 4, 2026 | 202 ms |
| Jul 11, 2026 | 177 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 160 ms |
| Aug 15, 2026 | 160 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 160 ms |
| Sep 12, 2026 | 161 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 164 ms |
| Oct 24, 2026 | 166 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.9 s
1.8 s
2.8 s
3.7 s
4.6 s
5.5 s
6.4 s
7.4 s
Speed
Render-blocking requests
1.6 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Reduce unused JavaScript
1.2 s · 242 KiBAbout 242 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Reduce unused CSS
1.1 s · 116 KiBAbout 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Improve image delivery
600 ms · 442 KiB10 images could be 442 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
300 ms · 43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
2,956 HTML elements
The page has 2,956 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Analytics and YouTube), adding 322 KiB and 190 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 133 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
131 KiB14 files are served with short cache lifetimes, so returning visitors download them again (131 KiB).
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 697 ms of it running JavaScript. That is comfortably low.
Server response: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 11.2 s
11.2 sYour largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Play”.
Time to Interactive: 11.3 s
11.3 sThe page becomes fully interactive after 11.3 s. Good is under 3.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 220 ms
220 msScripts block taps and scrolling for 220 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 735 ms
735 msReal visitors wait 735 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 223 ms to 166 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 1.0 s
1.0 sThe first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.2 MB in 93 requests
2.2 MBYour homepage downloads 2.2 MB in 93 requests on a phone: images 1.0 MB (56), scripts 884 KiB (23) and stylesheets 161 KiB (7). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (178 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 0.6 g of CO₂ per visit
0.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
Hidden but focusable
21 elements hidden from screen readers can still receive keyboard focus.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (44 elements)
All page content should be contained by landmarks: 44 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 124 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (92 characters)
Your title is 92 characters, so Google will cut it off around 60: “Find Top Colleges & Universities in India | Explore Courses, Exams, Admissions & Latest N…”.
2 H1 headlines
There are 2 <h1> headlines (“Right Guidance, Bright Future” and “Online Degrees”). One clear main headline is easier for people and search engines.
Meta description is long (204 characters)
Your meta description is 204 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
627 internal links, 29 external
The homepage links to 627 pages on collegedekho.com and 29 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.collegedekho.com/.
Structured data in place
Structured data found: Organization, WebSite and webpage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.collegedekho.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.collegedekho.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
Opted out of AI training for 2 crawlers
robots.txt blocks GPTBot and ClaudeBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,067 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://www.collegedekho.com/common-application-form has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.collegedekho.com/news/jee-main-unofficial-answer-key-21-january-2026-live-updates-subject-expert-coaching-institute-answer-keys-76615 and https://www.collegedekho.com/articles/ap-eamcet-second-phase-counselling-2025-dates-web-options-seat-allotment took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
16 small tap targets
16 of 41 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'register')”.
9 distorted images
9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,729 words of copy
The homepage carries about 1,729 words of visible text.
4 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Let’s start your application”, “Talk to a college expert” and “Start Your Application”.
Social proof on the page
Social proof on the homepage: 19 customer or partner logos, 6 trust badges and “250+ Companies”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at collegedekho.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Analytics
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on collegedekho.com, including 14 speed issues, 4 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.