Website review, no card needed

atmajaya.ac.id logo

atmajaya.ac.id website review

Visit site (opens in a new tab)Reviewed 25 October 202640 issues · 59 checks

This review found 40 issues worth fixing on atmajaya.ac.id, 15 of them high impact, across 59 checks. The most urgent: reduce unused JavaScript. 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

Full-page screenshot of atmajaya.ac.id (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. atmajaya.ac.id at 3.1 s3.1 s
  2. atmajaya.ac.id at 6.3 s6.3 s
  3. atmajaya.ac.id at 9.4 s9.4 s
  4. atmajaya.ac.id at 12.6 s12.6 s
  5. atmajaya.ac.id at 15.7 s15.7 s
  6. atmajaya.ac.id at 18.9 s18.9 s
  7. atmajaya.ac.id at 22.0 s22.0 s
  8. atmajaya.ac.id at 25.2 s25.2 s

Speed

4 to fix56
  • Reduce unused JavaScript

    2.4 s · 286 KiB

    About 286 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56 (desktop: 61). Pages that score under 90 lose visitors before the first paint.

  • Avoid multiple page redirects

    822 ms

    The page goes through 2 redirects before it starts loading, costing about 822 ms. Link and advertise the final URL directly.

  • Minify JavaScript

    500 ms · 57 KiB

    57 KiB could be saved by minifying JavaScript.

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    61 KiB

    About 61 KiB of CSS is downloaded but never applied on this page.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix58
  • Largest Contentful Paint: 11.1 s

    11.1 s

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

  • Speed Index: 17.4 s

    17.4 s

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

  • Time to Interactive: 11.1 s

    11.1 s

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

  • 32 images without width and height

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

  • Cumulative Layout Shift: 0.157

    0.157

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 69 ms

    69 ms

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

Images and page weight

1 to fix70
  • Page weight: 11.0 MB in 99 requests

    11.0 MB

    Your homepage downloads 11.0 MB in 99 requests on a phone: images 10.1 MB (58), scripts 638 KiB (15) and fonts 202 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (38 KiB) is 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 3.1 g of CO₂ per visit

    3.12 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fix65
  • 29 buttons without a name

    29 buttons have no accessible name, so screen readers announce just “button”.

  • 39 text elements with low contrast

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

  • 21 tap targets too small

    21 tap targets are too small or too close together to hit reliably with a finger.

  • 5 links without text

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

  • 1 form field without a label

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

SEO

11 to fixGoogle 7543
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

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

  • 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 XML sitemap

    No XML sitemap at https://atmajaya.ac.id/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 5 links crawlers can't follow

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

AI search readiness

2 to fix42
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 396 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

Best practices

6 to fixGoogle 9241
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 1 broken image

    1 image failed to load on a phone, for example https://atmajaya.ac.id/id/.

  • 22 small tap targets

    22 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • No character set

    No character set is declared, so some characters can render as gibberish.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Content and conversion

4 to fix30
  • 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.

  • 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 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 396 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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

    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.

  • 8 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

Analytics
Google Analytics

Company

Founded
1960

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on atmajaya.ac.id, including 10 speed issues, 11 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

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