Website review, no card needed

iiit.ac.in logo

iiit.ac.in website review

Visit site (opens in a new tab)Reviewed 31 October 202630 issues · 72 checks

This review found 30 issues worth fixing on iiit.ac.in, 12 of them high impact, across 72 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.9 s2.3 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.6 s
May 16, 20263.7 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.4 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.8 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
149 ms124 msMay 9Oct 24133 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026143 ms
May 16, 2026146 ms
May 23, 2026145 ms
May 30, 2026141 ms
Jun 6, 2026139 ms
Jun 13, 2026135 ms
Jun 20, 2026135 ms
Jun 27, 2026139 ms
Jul 4, 2026141 ms
Jul 11, 2026141 ms
Jul 18, 2026139 ms
Jul 25, 2026138 ms
Aug 1, 2026139 ms
Aug 8, 2026138 ms
Aug 15, 2026139 ms
Aug 22, 2026137 ms
Aug 29, 2026136 ms
Sep 5, 2026137 ms
Sep 12, 2026136 ms
Sep 19, 2026134 ms
Sep 26, 2026130 ms
Oct 3, 2026127 ms
Oct 10, 2026128 ms
Oct 17, 2026131 ms
Oct 24, 2026133 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

Full-page screenshot of iiit.ac.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. iiit.ac.in at 2.1 s2.1 s
  2. iiit.ac.in at 4.1 s4.1 s
  3. iiit.ac.in at 6.2 s6.2 s
  4. iiit.ac.in at 8.3 s8.3 s
  5. iiit.ac.in at 10.3 s10.3 s
  6. iiit.ac.in at 12.4 s12.4 s
  7. iiit.ac.in at 14.5 s14.5 s
  8. iiit.ac.in at 16.5 s16.5 s

Speed

8 to fix74
  • Render-blocking requests

    11.1 s

    33 files block the first paint until they finish downloading. Deferring or inlining them could save about 11.1 s.

  • Font display

    3.0 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).

  • Use efficient cache lifetimes

    1.4 s · 403 KiB

    54 files are served with short cache lifetimes, so returning visitors download them again (403 KiB).

  • Document request latency

    1.8 s

    The HTML itself could arrive about 1.8 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    1.8 s

    Reduce initial server response time. Google estimates savings of 1.8 s on a phone.

  • Server response: 1.9 s

    1.9 s

    Your server takes 1.9 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    450 ms · 134 KiB

    About 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Improve image delivery

    32 KiB

    1 image could be 32 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    21 KiB

    About 21 KiB of JavaScript is downloaded but never used on this page.

  • 2 third-party services on the page

    2 third-party services load with your homepage (AddToAny and Google Fonts), adding 83 KiB and 7 ms of main-thread time.

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

1 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 64 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

9 to fix33
  • 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.

  • Real-user LCP: 4.4 s

    4.4 s

    Real visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.26

    0.26

    For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.

  • Speed Index: 15.5 s

    15.5 s

    Visually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.

  • Real-user FCP: 2.8 s

    2.8 s

    Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 3.9 s

    3.9 s

    Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.2 s).

  • First Contentful Paint: 2.7 s

    2.7 s

    The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 3.9 s

    3.9 s

    The page becomes fully interactive after 3.9 s. Good is under 3.8 s.

  • Tap response (INP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 143 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 134 ms

    134 ms

    Real visitors wait 134 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 29% faster for real visitors

    -29%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.6 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.16 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.16 g of CO₂e: 19.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed
  • Page weight: 573 KiB in 87 requests

    573 KiB

    Your homepage downloads 573 KiB in 87 requests on a phone: scripts 194 KiB (30), stylesheets 161 KiB (32) and HTML 89 KiB (2). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

2 to fix93
  • 19 links without text

    19 visible links have no text or label, so screen readers cannot say where they go.

  • 15 text elements with low contrast

    15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 9275
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (21 characters)

    Your title is only 21 characters: “Home - IIIT Hyderabad”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (473 characters)

    Your meta description is 473 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 166 internal links, 40 external

    The homepage links to 166 pages on iiit.ac.in and 40 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.iiit.ac.in/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.iiit.ac.in/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.iiit.ac.in/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.

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 description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (877 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.iiit.ac.in/faculty is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.iiit.ac.in/gallery-3 and https://www.iiit.ac.in/faculty have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://www.iiit.ac.in/at-a-glance, https://www.iiit.ac.in/governing-council, https://www.iiit.ac.in/achievements, https://www.iiit.ac.in/infrastructure, https://www.iiit.ac.in/activities-reports and https://www.iiit.ac.in/disclosure and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.iiit.ac.in/at-a-glance, https://www.iiit.ac.in/history, https://www.iiit.ac.in/governing-council, https://www.iiit.ac.in/achievements, https://www.iiit.ac.in/rankings and https://www.iiit.ac.in/gallery-3 and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 75 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 6 small tap targets

    6 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 569 words of copy

    The homepage carries about 569 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “CONTACT”, “Contact Us” and “DSAA-2026: Call for Participation”.

Privacy and tracking

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

  • 3 other companies contacted

    Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 iiit.ac.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Software Technology Parks of India - Bangalore

Company

Founded
1998

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on iiit.ac.in, including 17 speed issues, 4 SEO issues and 3 conversion gaps. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25