Website review, no card needed
umn.ac.id website review
Visit site (opens in a new tab)Reviewed 18 November 202645 issues · 93 checks
This review found 45 issues worth fixing on umn.ac.id, 22 of them high impact, across 93 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 4.3 s |
| Oct 24, 2026 | 4.1 s |
| Oct 31, 2026 | 4.0 s |
| Nov 7, 2026 | 3.8 s |
| Nov 14, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 239 ms |
| Jun 6, 2026 | 242 ms |
| Jun 13, 2026 | 241 ms |
| Jun 20, 2026 | 243 ms |
| Jun 27, 2026 | 246 ms |
| Jul 4, 2026 | 238 ms |
| Jul 11, 2026 | 229 ms |
| Jul 18, 2026 | 220 ms |
| Jul 25, 2026 | 210 ms |
| Aug 1, 2026 | 218 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 224 ms |
| Aug 22, 2026 | 229 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 228 ms |
| Sep 12, 2026 | 223 ms |
| Sep 19, 2026 | 212 ms |
| Sep 26, 2026 | 206 ms |
| Oct 3, 2026 | 210 ms |
| Oct 10, 2026 | 206 ms |
| Oct 17, 2026 | 205 ms |
| Oct 24, 2026 | 198 ms |
| Oct 31, 2026 | 190 ms |
| Nov 7, 2026 | 196 ms |
| Nov 14, 2026 | 206 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
Speed
Render-blocking requests
4.7 s62 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Reduce unused JavaScript
1.9 s · 459 KiBAbout 459 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Reduce unused CSS
1.2 s · 240 KiBAbout 240 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Document request latency
1.4 sThe HTML itself could arrive about 1.4 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
1.3 sReduce initial server response time. Google estimates savings of 1.3 s on a phone.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
600 ms · 259 KiB7 images could be 259 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.
Minify JavaScript
300 ms · 57 KiB57 KiB could be saved by minifying JavaScript.
1,508 HTML elements
The page has 1,508 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 1.4 s
1.4 sYour server takes 1.4 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and buttonizer.io and others), adding 829 KiB and 311 ms of main-thread time.
Minify CSS
150 ms · 19 KiB19 KiB could be saved by minifying CSS.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 119 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
6 KiB4 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
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.
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.
Real-user LCP: 4.5 s
4.5 sReal visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 21.4 s
21.4 sYour largest element takes 21.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tim Mahasiswa UMN Raih Juara 3 BMNC 2026 Lewat Inovasi Plat…”.
Speed Index: 18.9 s
18.9 sVisually, the page fills in at 18.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.3 s
24.3 sThe page becomes fully interactive after 24.3 s. Good is under 3.8 s.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Real-user INP: 289 ms
289 msReal visitors wait 289 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
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: 787 ms
787 msReal visitors wait 787 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 239 ms to 206 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.4 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 173 ms
173 msScripts block the page for only 173 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 190 requests
4.9 MBYour homepage downloads 4.9 MB in 190 requests on a phone: images 2.4 MB (38), scripts 1.0 MB (66) and fonts 1,012 KiB (17). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (107 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 166.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (5 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 5 elements on the page fail this check, rated moderate by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h5 and h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 61 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 14 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Universitas Multimedia Nusantara | Universitas Multimedia Nusantara”.
5 H1 headlines
There are 5 <h1> headlines (“Tim Mahasiswa UMN Raih Juara 3 BMNC 2026 Lewat In…”, “Raih Peringkat 2 Nasional dan 13 di ASEAN Kategor…” and “Jalin Kolaborasi Internasional dengan Leeds Becke…”). One clear main headline is easier for people and search engines.
101 internal links, 57 external
The homepage links to 101 pages on umn.ac.id and 57 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.umn.ac.id/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, Person 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.umn.ac.id/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing url, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.umn.ac.id/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (918 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://www.umn.ac.id/pendaftaran, https://www.umn.ac.id/en/international, https://www.umn.ac.id/pendaftaran-rpl, https://www.umn.ac.id/sambutan-rektor, https://www.umn.ac.id/pimpinan-universitas and https://www.umn.ac.id/dosen and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.umn.ac.id/laporan-fikom, whose canonical is https://www.umn.ac.id/laporan/fikom. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.umn.ac.id/en/international, https://www.umn.ac.id/sambutan-rektor and https://www.umn.ac.id/laporan-fikom have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.umn.ac.id/dosen and https://www.umn.ac.id/laporan-fikom 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.
4 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.
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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.umn.ac.id/wp-content/plugins/visual-portfolio/assets/css/theme-betheme.css?ver…”.
2 checks passed
Tap targets are thumb-sized
24 of 29 tappable elements near the top are at least 24 px.
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 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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 522 words of copy
The homepage carries about 522 words of visible text.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and 6 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
13 other companies contacted
Loading the homepage contacts 13 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 umn.ac.id, 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
- Astro
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Company
- Founded
- 2006
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on umn.ac.id, including 20 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.