Website review, no card needed

iit.ac.lk logo

iit.ac.lk website review

Visit site (opens in a new tab)Reviewed 26 October 202641 issues · 89 checks

This review found 41 issues worth fixing on iit.ac.lk, 16 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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.6 s2.9 sMay 9Oct 243.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.2 s
May 16, 20263.2 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.2 s
Jul 4, 20263.4 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.4 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
180 ms139 msMay 9Oct 24175 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026153 ms
May 16, 2026157 ms
May 23, 2026160 ms
May 30, 2026163 ms
Jun 6, 2026160 ms
Jun 13, 2026155 ms
Jun 20, 2026145 ms
Jun 27, 2026144 ms
Jul 4, 2026145 ms
Jul 11, 2026149 ms
Jul 18, 2026154 ms
Jul 25, 2026151 ms
Aug 1, 2026149 ms
Aug 8, 2026146 ms
Aug 15, 2026145 ms
Aug 22, 2026146 ms
Aug 29, 2026146 ms
Sep 5, 2026146 ms
Sep 12, 2026147 ms
Sep 19, 2026148 ms
Sep 26, 2026152 ms
Oct 3, 2026159 ms
Oct 10, 2026164 ms
Oct 17, 2026174 ms
Oct 24, 2026175 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 iit.ac.lk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. iit.ac.lk at 1.7 s1.7 s
  2. iit.ac.lk at 3.3 s3.3 s
  3. iit.ac.lk at 5.0 s5.0 s
  4. iit.ac.lk at 6.6 s6.6 s
  5. iit.ac.lk at 8.3 s8.3 s
  6. iit.ac.lk at 9.9 s9.9 s
  7. iit.ac.lk at 11.6 s11.6 s
  8. iit.ac.lk at 13.2 s13.2 s

Speed

10 to fix48
  • Use efficient cache lifetimes

    2.9 s · 1.4 MB

    43 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    350 ms · 7.1 MB

    20 images could be 7.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, hsappstatic.net and Hubspot and others), adding 1.7 MB and 924 ms of main-thread time.

  • Reduce unused JavaScript

    658 KiB

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

  • Google Tag Manager adds 472 ms

    472 ms

    Google Tag Manager costs a phone 472 ms of main-thread work and 864 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused CSS

    450 ms · 107 KiB

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

  • hsappstatic.net adds 319 ms

    319 ms

    hsappstatic.net costs a phone 319 ms of main-thread work and 697 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 3.1 s

    A phone's processor spends 3.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 205 ms. During a long task the page ignores taps.

  • Minify CSS

    150 ms · 18 KiB

    18 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    21 KiB

    Polyfills for old browsers add 21 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 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.3 s

    4.3 s

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

  • Real-user FCP: 3.3 s

    3.3 s

    Real visitors see the first content after 3.3 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: 9.8 s

    9.8 s

    Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At IIT, we offer UK degrees in Computing and Business that …”. Most of its time is element render delay (5.3 s).

  • Speed Index: 27.4 s

    27.4 s

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

  • Time to Interactive: 34.0 s

    34.0 s

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

  • Real-user CLS: 0.19

    0.19

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

  • Cumulative Layout Shift: 0.184

    0.184

    The layout shifts by 0.184 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 274 ms

    274 ms

    Scripts block taps and scrolling for 274 ms in total while the page loads. Good is under 200 ms.

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 13% slower for real visitors

    +13%

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

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

1 checks passed
  • Real-user INP: 176 ms

    176 ms

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

Images and page weight

5 to fix18
  • Page weight: 20.3 MB in 136 requests

    20.3 MB

    Your homepage downloads 20.3 MB in 136 requests on a phone: images 18.1 MB (63), scripts 1.7 MB (37) and fonts 209 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 8 images over 500 KB

    8 images weigh 12.1 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    2.6 MB

    9 images are downloaded at several times the size a phone draws them, for example Sri-Lanka-Skills-Expo-2026-Booth-Showcase.png at 1,983 px wide, shown at 374 px. Resized copies would save about 2.6 MB.

  • 18 images in older formats

    18 images (13.7 MB) 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.

  • 10 images below the first screen load straight away

    10 images further down the page (4.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.8 g of CO₂ per visit

    5.76 g

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

Accessibility

5 to fixGoogle 8693
  • 3 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • All page content should be contained by landmarks (15 elements)

    All page content should be contained by landmarks: 15 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.

  • 14 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 84 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • 40 links with vague text

    40 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Meta description is long (503 characters)

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

  • 178 internal links, 18 external

    The homepage links to 178 pages on iit.ac.lk and 18 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “IIT provides globally recognized qualifications in the field of IT & Business”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “IIT Sri Lanka | British IT and Business Degrees in Colombo”.

  • Canonical URL set

    The canonical URL is https://www.iit.ac.lk/.

  • Structured data in place

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

  • 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.iit.ac.lk/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles) and description; logo and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.iit.ac.lk/llms.txt (79 KiB, 657 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix85
  • 1 page points its canonical at the homepage

    https://www.iit.ac.lk/webinars declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 14 pages without a meta description

    https://www.iit.ac.lk/research, https://www.iit.ac.lk/scholarships, https://www.iit.ac.lk/study/global-pathways, https://www.iit.ac.lk/international-students, https://www.iit.ac.lk/international-students/visa-guidelines and https://www.iit.ac.lk/alumni and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages slow to respond

    https://www.iit.ac.lk/international-students/visa-guidelines, https://www.iit.ac.lk/course, https://www.iit.ac.lk/study/business and https://www.iit.ac.lk/study/computing took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 6994
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    48 of 48 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 1,337 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Apply Now” and “Contact Us”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact Us” and “Apply Now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 iit.ac.lk, 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
Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on iit.ac.lk, including 22 speed issues, 2 SEO issues and 2 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
iit.ac.lk website review: scores and fixes | Programmable