Website review, no card needed

unnes.ac.id logo

unnes.ac.id website review

Visit site (opens in a new tab)Reviewed 30 October 202625 issues · 77 checks

This review found 25 issues worth fixing on unnes.ac.id, 7 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
2.7 s1.7 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.3 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
306 ms189 msMay 9Oct 24269 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026233 ms
May 16, 2026228 ms
May 23, 2026230 ms
May 30, 2026202 ms
Jun 6, 2026202 ms
Jun 13, 2026204 ms
Jun 20, 2026204 ms
Jun 27, 2026206 ms
Jul 4, 2026206 ms
Jul 11, 2026206 ms
Jul 18, 2026215 ms
Jul 25, 2026232 ms
Aug 1, 2026243 ms
Aug 8, 2026260 ms
Aug 15, 2026266 ms
Aug 22, 2026279 ms
Aug 29, 2026287 ms
Sep 5, 2026292 ms
Sep 12, 2026292 ms
Sep 19, 2026287 ms
Sep 26, 2026280 ms
Oct 3, 2026271 ms
Oct 10, 2026268 ms
Oct 17, 2026269 ms
Oct 24, 2026269 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 unnes.ac.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. unnes.ac.id at 0.4 s0.4 s
  2. unnes.ac.id at 0.8 s0.8 s
  3. unnes.ac.id at 1.1 s1.1 s
  4. unnes.ac.id at 1.5 s1.5 s
  5. unnes.ac.id at 1.9 s1.9 s
  6. unnes.ac.id at 2.3 s2.3 s
  7. unnes.ac.id at 2.6 s2.6 s
  8. unnes.ac.id at 3.0 s3.0 s

Speed

4 to fix80
  • Render-blocking requests

    2.2 s

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

  • Mobile performance score: 80

    80/100

    Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    460 ms · 114 KiB

    About 114 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • rocketcdn.me adds 18 ms

    18 ms

    rocketcdn.me costs a phone 18 ms of main-thread work and 715 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.

  • 2 third-party services on the page

    2 third-party services load with your homepage (rocketcdn.me and Cloudflare), adding 726 KiB and 23 ms of main-thread time.

  • Improve image delivery

    47 KiB

    4 images could be 47 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

  • Use efficient cache lifetimes

    5 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (5 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.

2 checks passed
  • Main-thread work: 0.4 s

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

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

7 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 CLS: 0.38

    0.38

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A manifestation of Universitas Negeri Semarang’s commitment…”.

  • Real-user INP: 274 ms

    274 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Time to Interactive: 4.6 s

    4.6 s

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

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

    +17%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 233 ms to 269 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 2.2 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 747 ms

    747 ms

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

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • 3 images below the first screen load straight away

    3 images further down the page (77 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.3 g of CO₂ per visit

    0.26 g

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

3 checks passed
  • Page weight: 943 KiB in 60 requests

    943 KiB

    Your homepage downloads 943 KiB in 60 requests on a phone: images 375 KiB (25), fonts 317 KiB (10) and stylesheets 186 KiB (20). That is a lean page.

  • 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

6 to fixGoogle 8691
  • Unlabelled dropdowns

    1 dropdown has no label.

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

  • 3 images without alt text

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

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

    All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.

  • 19 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • Meta description is long (163 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 6 links with vague text

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

  • 191 internal links, 34 external

    The homepage links to 191 pages on unnes.ac.id and 34 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “UNNES Berdampak”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Welcome to UNNES Homepage - Universitas Negeri Semarang”.

  • Canonical URL set

    The canonical URL is https://unnes.ac.id/.

  • Structured data in place

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

  • 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://unnes.ac.id/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://unnes.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.

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,946 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 10 pages without a meta description

    https://unnes.ac.id/admission/en/home, https://unnes.ac.id/international-undergraduate-program, https://unnes.ac.id/short-courses, https://unnes.ac.id/experts, https://unnes.ac.id/library/e-journals and https://unnes.ac.id/research-collaboration and 4 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://unnes.ac.id/international-undergraduate-program, whose canonical is https://unnes.ac.id/study-at-unnes/international-undergraduate-program. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 10 pages without an H1

    https://unnes.ac.id/study-at-unnes/faculties-and-departments, https://unnes.ac.id/international-undergraduate-program, https://unnes.ac.id/short-courses, https://unnes.ac.id/research, https://unnes.ac.id/research-facilities and https://unnes.ac.id/library/e-journals and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://unnes.ac.id/admission/en/home took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 83 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. 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 1,070 words of copy

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact” and “Learn More”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts 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 unnes.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 Tag Manager
Hosting
Cloudflare

Company

Founded
1965

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on unnes.ac.id, including 11 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

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