Website review, no card needed

kmu.ac.ir logo

kmu.ac.ir website review

Visit site (opens in a new tab)Reviewed 26 October 202655 issues · 86 checks

This review found 55 issues worth fixing on kmu.ac.ir, 23 of them high impact, across 86 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.7 s3.2 sMay 9Oct 243.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.3 s
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.4 s
Jul 4, 20263.3 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.6 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
280 ms255 msMay 9Oct 24262 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026264 ms
May 16, 2026267 ms
May 23, 2026268 ms
May 30, 2026262 ms
Jun 6, 2026259 ms
Jun 13, 2026258 ms
Jun 20, 2026261 ms
Jun 27, 2026267 ms
Jul 4, 2026270 ms
Jul 11, 2026274 ms
Jul 18, 2026269 ms
Jul 25, 2026272 ms
Aug 1, 2026275 ms
Aug 8, 2026275 ms
Aug 15, 2026277 ms
Aug 22, 2026275 ms
Aug 29, 2026271 ms
Sep 5, 2026269 ms
Sep 12, 2026268 ms
Sep 19, 2026269 ms
Sep 26, 2026269 ms
Oct 3, 2026268 ms
Oct 10, 2026268 ms
Oct 17, 2026262 ms
Oct 24, 2026262 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 kmu.ac.ir (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kmu.ac.ir at 2.3 s2.3 s
  2. kmu.ac.ir at 4.5 s4.5 s
  3. kmu.ac.ir at 6.8 s6.8 s
  4. kmu.ac.ir at 9.1 s9.1 s
  5. kmu.ac.ir at 11.3 s11.3 s
  6. kmu.ac.ir at 13.6 s13.6 s
  7. kmu.ac.ir at 15.9 s15.9 s
  8. kmu.ac.ir at 18.1 s18.1 s

Speed

7 to fix34
  • Use efficient cache lifetimes

    16.1 s · 8.5 MB

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

  • Improve image delivery

    14.8 s · 5.0 MB

    40 images could be 5.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.8 s faster on a phone.

  • Render-blocking requests

    2.4 s

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

  • Font display

    2.4 s

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

  • Mobile performance score: 34

    34/100

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

  • Reduce unused JavaScript

    750 ms · 98 KiB

    About 98 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Minify JavaScript

    300 ms · 30 KiB

    30 KiB could be saved by minifying JavaScript.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 230 ms

    230 ms

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

Core Web Vitals

12 to fix0
  • 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 FCP: 3.1 s

    3.1 s

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • Largest Contentful Paint: 27.6 s

    27.6 s

    Your largest element takes 27.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “همایش اموزش پزشکی”.

  • Time to Interactive: 28.3 s

    28.3 s

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

  • Speed Index: 14.5 s

    14.5 s

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

  • Cumulative Layout Shift: 0.99

    0.99

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 260 ms

    260 ms

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

  • Real-user CLS: 0.22

    0.22

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

  • 50 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

1 checks passed
  • Total Blocking Time: 2 ms

    2 ms

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

Images and page weight

5 to fix18
  • Page weight: 8.7 MB in 150 requests

    8.7 MB

    Your homepage downloads 8.7 MB in 150 requests on a phone: images 7.6 MB (102), fonts 925 KiB (7) and scripts 166 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    پوستر_همایش_آموزش_علوم_پزشکی______-_Copy1111111111111__3_.pn weighs 2.0 MB. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    2.1 MB

    6 images are downloaded at several times the size a phone draws them, for example پوستر_همایش_آموزش_علوم_پزشکی______-_Copy1111111111111__3_.pn at 1,920 px wide, shown at 390 px. Resized copies would save about 2.1 MB.

  • 19 images in older formats

    19 images (4.2 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 (846 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.5 g of CO₂ per visit

    2.48 g

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

Accessibility

11 to fixGoogle 7884
  • Hidden but focusable

    39 elements hidden from screen readers can still receive keyboard focus.

  • 12 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 60 images in the HTML carry an alt attribute.

  • 33 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: 33 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 8257
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (24 characters)

    Your title is only 24 characters: “دانشگاه علوم پزشکی کرمان”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at kmu.ac.ir/robots.txt, the first file search crawlers ask for.

  • 12 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 139 internal links, 88 external

    The homepage links to 139 pages on kmu.ac.ir and 88 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://kmu.ac.ir/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://kmu.ac.ir/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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix90
  • 4 pages without a meta description

    https://kmu.ac.ir/fa/page/40188/%D8%B1-%DB%8C%D8%B3-%D9%88-%D9%85%D8%B9%D8%A7%D9%88%D9%86%DB%8C%D9%86, https://kmu.ac.ir/fa/page/39354/%D8%AF%D9%81%D8%AA%D8%B1-%D8%B1%DB%8C%D8%A7%D8%B3%D8%AA, https://kmu.ac.ir/fa/page/54502/%D8%B4%D8%B1%D8%AD-%D9%88%D8%B8%D8%A7%DB%8C%D9%81 and https://kmu.ac.ir/fa/page/54503/%D8%B3%D8%A7%D8%AE%D8%AA%D8%A7%D8%B1-%D8%AF%D8%A8%DB%8C%D8%B1%D8%AE%D8%A7%D9%86%D9%87 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://kmu.ac.ir/fa/rs, https://kmu.ac.ir/en, https://kmu.ac.ir/fa/page/39354/%D8%AF%D9%81%D8%AA%D8%B1-%D8%B1%DB%8C%D8%A7%D8%B3%D8%AA, https://kmu.ac.ir/fa/harasat, https://kmu.ac.ir/fa/isargaran and https://kmu.ac.ir/fa/bazrasi and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages with very little text

    https://kmu.ac.ir/fa/rs, https://kmu.ac.ir/fa/page/40188/%D8%B1-%DB%8C%D8%B3-%D9%88-%D9%85%D8%B9%D8%A7%D9%88%D9%86%DB%8C%D9%86, https://kmu.ac.ir/fa/page/18375/%D9%85%D8%B4%D8%A7%D9%88%D8%B1%DB%8C%D9%86, https://kmu.ac.ir/fa/page/39354/%D8%AF%D9%81%D8%AA%D8%B1-%D8%B1%DB%8C%D8%A7%D8%B3%D8%AA, https://kmu.ac.ir/fa/harasat and https://kmu.ac.ir/fa/isargaran and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 6 pages slow to respond

    https://kmu.ac.ir/fa/harasat, https://kmu.ac.ir/fa/bazrasi, https://kmu.ac.ir/fa/page/54502/%D8%B4%D8%B1%D8%AD-%D9%88%D8%B8%D8%A7%DB%8C%D9%81, https://kmu.ac.ir/fa/page/54503/%D8%B3%D8%A7%D8%AE%D8%AA%D8%A7%D8%B1-%D8%AF%D8%A8%DB%8C%D8%B1%D8%AE%D8%A7%D9%86%D9%87, https://kmu.ac.ir/fa/omana and https://kmu.ac.ir/fa/it took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 16 small tap targets

    16 of 66 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 “Failed to load resource: the server responded with a status of 404 (Not Found)”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

7 to fix36
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • A 12-field form

    Your longest form asks for 12 fields (0 required). Every extra field lowers completion.

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

  • Only about 79 words

    The homepage has only about 79 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 kmu.ac.ir, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Company

Founded
1978

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on kmu.ac.ir, including 19 speed issues, 8 SEO issues and 7 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