Website review, no card needed

habib.edu.pk logo

habib.edu.pk website review

Visit site (opens in a new tab)Reviewed 1 November 202647 issues · 92 checks

This review found 47 issues worth fixing on habib.edu.pk, 25 of them high impact, across 92 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
5.8 s3.8 sMay 9Oct 245.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.1 s
May 16, 20264.0 s
May 23, 20264.0 s
May 30, 20264.0 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.2 s
Jul 11, 20264.4 s
Jul 18, 20264.5 s
Jul 25, 20265.0 s
Aug 1, 20265.3 s
Aug 8, 20265.4 s
Aug 15, 20265.6 s
Aug 22, 20265.2 s
Aug 29, 20265.1 s
Sep 5, 20265.1 s
Sep 12, 20264.9 s
Sep 19, 20264.6 s
Sep 26, 20264.5 s
Oct 3, 20265.1 s
Oct 10, 20265.1 s
Oct 17, 20265.1 s
Oct 24, 20265.6 s
Real-visitor tap response (INP)75th percentile, phones
304 ms227 msMay 9Oct 24294 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026238 ms
May 16, 2026236 ms
May 23, 2026242 ms
May 30, 2026243 ms
Jun 6, 2026245 ms
Jun 13, 2026246 ms
Jun 20, 2026246 ms
Jun 27, 2026245 ms
Jul 4, 2026250 ms
Jul 11, 2026261 ms
Jul 18, 2026272 ms
Jul 25, 2026294 ms
Aug 1, 2026294 ms
Aug 8, 2026295 ms
Aug 15, 2026289 ms
Aug 22, 2026277 ms
Aug 29, 2026278 ms
Sep 5, 2026277 ms
Sep 12, 2026273 ms
Sep 19, 2026265 ms
Sep 26, 2026257 ms
Oct 3, 2026265 ms
Oct 10, 2026271 ms
Oct 17, 2026280 ms
Oct 24, 2026294 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 habib.edu.pk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. habib.edu.pk at 1.5 s1.5 s
  2. habib.edu.pk at 3.0 s3.0 s
  3. habib.edu.pk at 4.5 s4.5 s
  4. habib.edu.pk at 6.0 s6.0 s
  5. habib.edu.pk at 7.5 s7.5 s
  6. habib.edu.pk at 9.0 s9.0 s
  7. habib.edu.pk at 10.5 s10.5 s
  8. habib.edu.pk at 12.0 s12.0 s

Speed

13 to fix28
  • Use efficient cache lifetimes

    9.9 s · 7.7 MB

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

  • Render-blocking requests

    6.0 s

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

  • Reduce unused JavaScript

    4.5 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.

  • Reduce unused CSS

    2.5 s · 545 KiB

    About 545 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Google Tag Manager adds 1.3 s

    1.3 s

    Google Tag Manager costs a phone 1.3 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 28

    28/100

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

  • Main-thread work: 7.4 s

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

  • Improve image delivery

    750 ms · 2.7 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Intercom and Facebook and others), adding 2.4 MB and 2.9 s of main-thread time.

  • Intercom adds 954 ms

    954 ms

    Intercom costs a phone 954 ms of main-thread work and 967 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.

  • Minify CSS

    600 ms · 128 KiB

    128 KiB could be saved by minifying CSS.

  • 20 long tasks on the main thread

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

  • Facebook adds 302 ms

    302 ms

    Facebook costs a phone 302 ms of main-thread work and 227 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.

  • Minify JavaScript

    150 ms · 20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Document request latency

    149 KiB

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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: 379 ms

    379 ms

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

Core Web Vitals

13 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: 5.2 s

    5.2 s

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

  • Real-user FCP: 4.4 s

    4.4 s

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

  • Real-user TTFB: 2.4 s

    2.4 s

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

  • First Contentful Paint: 7.6 s

    7.6 s

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

  • Largest Contentful Paint: 42.0 s

    42.0 s

    Your largest element takes 42.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 18.6 s

    18.6 s

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

  • Time to Interactive: 47.7 s

    47.7 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Real-user INP: 329 ms

    329 ms

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

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

    +21%

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

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

    +33%

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

  • 16 images without width and height

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

2 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.037

    0.037

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

Images and page weight

5 to fix28
  • Page weight: 10.4 MB in 190 requests

    10.4 MB

    Your homepage downloads 10.4 MB in 190 requests on a phone: images 6.8 MB (90), scripts 2.6 MB (40) and stylesheets 561 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Muneera-Batool22-scaled.jpg weighs 850 KiB. On a phone connection a single image that size takes seconds.

  • 14 images in older formats

    14 images (2.0 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.

  • 12 images below the first screen load straight away

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

  • 3 images far larger than shown

    46 KiB

    3 images are downloaded at several times the size a phone draws them, for example dhss.webp at 986 px wide, shown at 300 px. Resized copies would save about 46 KiB.

  • About 3.0 g of CO₂ per visit

    2.95 g

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

Accessibility

7 to fixGoogle 8387
  • Hidden but focusable

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

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

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

  • Headings skip levels

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

1 checks passed
  • 35 automated accessibility rules passed

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

SEO

1 to fixGoogle 8598
  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 198 internal links, 38 external

    The homepage links to 198 pages on habib.edu.pk and 38 external pages.

8 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Habib University ranks top among Pakistan's Best Universities in Karachi for liberal arts & sciences education with a u…”.

  • One H1 headline

    Your main headline reads: “Bringing World-Class Liberal Arts Education to Pakistan”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Habib University: Best University in Pakistan for Liberal Arts”.

  • Canonical URL set

    The canonical URL is https://habib.edu.pk/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, LocalBusiness, Organization 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://habib.edu.pk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://habib.edu.pk/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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix76
  • 1 page points its canonical at the homepage

    https://habib.edu.pk/covid19 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.

  • 4 pages share 2 titles

    / and https://habib.edu.pk/covid19 all use the title “Habib University: Best University in Pakistan for Liberal Arts”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://habib.edu.pk/hu-careers/staff-careers, https://habib.edu.pk/hu-careers/offices-at-habib-university, https://habib.edu.pk/embark and https://habib.edu.pk/hu-careers/open-apply have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://habib.edu.pk/ace and https://habib.edu.pk/ace-edge use the same meta description. A description written for each page earns more clicks.

  • 2 pages slow to respond

    https://habib.edu.pk/covid19 and https://habib.edu.pk/hu-careers took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix78
  • 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 social proof

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 541 words of visible text.

7 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Apply for Admissions”, “Open Apply” and “Contact Us”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity, Hotjar and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 17 cookies set on arrival

    17

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

  • 29 other companies contacted

    Loading the homepage contacts 29 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 habib.edu.pk, 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 | Google Tag Manager | Hotjar | Microsoft Clarity
Hosting
AWS

Company

Founded
2014

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on habib.edu.pk, including 26 speed issues, 1 SEO issue 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
habib.edu.pk website review: scores and fixes | Programmable