Website review, no card needed
uinjambi.ac.id website review
Visit site (opens in a new tab)Reviewed 19 October 202633 issues · 79 checks
This review found 33 issues worth fixing on uinjambi.ac.id, 12 of them high impact, across 79 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.2 s |
| May 9, 2026 | 3.4 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 160 ms |
| May 9, 2026 | 163 ms |
| May 16, 2026 | 168 ms |
| May 23, 2026 | 177 ms |
| May 30, 2026 | 174 ms |
| Jun 6, 2026 | 175 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 172 ms |
| Jul 4, 2026 | 190 ms |
| Jul 11, 2026 | 192 ms |
| Jul 18, 2026 | 193 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 195 ms |
| Aug 8, 2026 | 177 ms |
| Aug 15, 2026 | 172 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 177 ms |
| Sep 19, 2026 | 176 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 172 ms |
| Oct 10, 2026 | 176 ms |
| Oct 17, 2026 | 180 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
How it loaded on a phone
2.0 s
4.0 s
6.0 s
8.0 s
10.0 s
12.0 s
13.9 s
15.9 s
Speed
Render-blocking requests
2.9 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Improve image delivery
900 ms · 398 KiB3 images could be 398 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 142 KiBAbout 142 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.
Reduce initial server response time
551 msReduce initial server response time. Google estimates savings of 551 ms on a phone.
Document request latency
550 msThe HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Google Tag Manager adds 329 ms
329 msGoogle Tag Manager costs a phone 329 ms of main-thread work and 289 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.
Server response: 651 ms
651 msYour server takes 651 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Google Fonts and others), adding 363 KiB and 335 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 147 KiB21 files are served with short cache lifetimes, so returning visitors download them again (147 KiB).
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 85 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.
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 JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 483 ms of it running JavaScript. That is comfortably low.
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.4 s
4.4 sReal visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.0 s
3.0 sReal visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (6.5 s).
Speed Index: 12.0 s
12.0 sVisually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Time to Interactive: 7.4 s
7.4 sThe page becomes fully interactive after 7.4 s. Good is under 3.8 s.
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.2 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 232 ms
232 msScripts block taps and scrolling for 232 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 160 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 195 ms
195 msReal visitors wait 195 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
1 image far larger than shown
158 KiB1 image is downloaded at several times the size a phone draws it, for example logo-web-uin-diperbarui.png at 1,920 px wide, shown at 98 px. Resized copies would save about 158 KiB.
2 images in older formats
2 images (225 KiB) 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.
About 0.4 g of CO₂ per visit
0.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 43.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.3 MB in 34 requests
1.3 MBYour homepage downloads 1.3 MB in 34 requests on a phone: images 758 KiB (13), scripts 364 KiB (11) and HTML 96 KiB (1). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 163 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (89 characters)
Your title is 89 characters, so Google will cut it off around 60: “Universitas Islam Negeri Sulthan Thaha Saifuddin Jambi – Global Excellence, Local Wisdom.”.
Meta description is short (32 characters)
Your meta description is only 32 characters: “Global Excellence, Local Wisdom.”. 70 to 160 characters is enough to sell the click.
5 H1 headlines
There are 5 <h1> headlines (“Universitas Islam Negeri Sulthan Thaha Saifuddin …”, “Jelang LSHRP XVIII Sumbagsel 2026, UIN Jambi Mata…” and “Menjadi Universitas Berkelas Dunia Berbasis Keari…”). One clear main headline is easier for people and search engines.
77 internal links, 107 external
The homepage links to 77 pages on uinjambi.ac.id and 107 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://uinjambi.ac.id/engine/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage, Organization 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://uinjambi.ac.id/sitemap_index.xml.
AI search readiness
Opted out of AI training for 3 crawlers
robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (929 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://uinjambi.ac.id/llms.txt (2 KiB, 23 links), a plain-text guide to the site for AI tools.
Other pages
10 pages without a meta description
https://uinjambi.ac.id/struktur-organisasi, https://uinjambi.ac.id/pimpinan-universitas, https://uinjambi.ac.id/pimpinan-fakultas-dan-lembaga, https://uinjambi.ac.id/dosen, https://uinjambi.ac.id/tenaga-kependidikan and https://uinjambi.ac.id/ukt and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages slow to respond
https://uinjambi.ac.id/visi-dan-misi, https://uinjambi.ac.id/struktur-organisasi, https://uinjambi.ac.id/pimpinan-universitas, https://uinjambi.ac.id/pimpinan-fakultas-dan-lembaga, https://uinjambi.ac.id/dosen and https://uinjambi.ac.id/tenaga-kependidikan and 7 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 41 found) and read each the way a search engine does.
6 checks passed
Linked pages load
13 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 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 13 pages that loaded have a <title>.
Best practices
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 ()”.
2 checks passed
Tap targets are thumb-sized
40 of 43 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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 548 words of copy
The homepage carries about 548 words of visible text.
2 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and 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.
2 cookies set on arrival
2Opening 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.
5 other companies contacted
Loading the homepage contacts 5 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 uinjambi.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
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Company
- Founded
- 1967
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on uinjambi.ac.id, including 19 speed issues, 3 SEO issues and 4 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.