Website review, no card needed

cau.ac.kr logo

cau.ac.kr website review

Visit site (opens in a new tab)Reviewed 4 November 202648 issues · 89 checks

This review found 48 issues worth fixing on cau.ac.kr, 21 of them high impact, across 89 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
1.4 s1.0 sMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
125 ms83 msMay 16Oct 3195 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026104 ms
May 30, 2026103 ms
Jun 6, 2026103 ms
Jun 13, 2026104 ms
Jun 20, 2026102 ms
Jun 27, 2026103 ms
Jul 4, 2026104 ms
Jul 11, 2026105 ms
Jul 18, 2026109 ms
Jul 25, 2026108 ms
Aug 1, 2026113 ms
Aug 8, 2026108 ms
Aug 15, 202693 ms
Aug 22, 202688 ms
Aug 29, 202688 ms
Sep 5, 202692 ms
Sep 12, 2026104 ms
Sep 19, 2026114 ms
Sep 26, 2026120 ms
Oct 3, 2026111 ms
Oct 10, 2026108 ms
Oct 17, 2026103 ms
Oct 24, 2026100 ms
Oct 31, 202695 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 cau.ac.kr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cau.ac.kr at 1.4 s1.4 s
  2. cau.ac.kr at 2.8 s2.8 s
  3. cau.ac.kr at 4.2 s4.2 s
  4. cau.ac.kr at 5.5 s5.5 s
  5. cau.ac.kr at 6.9 s6.9 s
  6. cau.ac.kr at 8.3 s8.3 s
  7. cau.ac.kr at 9.7 s9.7 s
  8. cau.ac.kr at 11.1 s11.1 s

Speed

12 to fix53
  • Use efficient cache lifetimes

    13.3 s · 14.3 MB

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

  • Improve image delivery

    4.8 s · 11.1 MB

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

  • Render-blocking requests

    6.5 s

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

  • Reduce unused JavaScript

    1.7 s · 395 KiB

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

  • Font display

    1.8 s

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

  • Document request latency

    1.0 s · 690 KiB

    The HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce unused CSS

    950 ms · 206 KiB

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

  • Mobile performance score: 53

    53/100

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

  • Reduce initial server response time

    981 ms

    Reduce initial server response time. Google estimates savings of 981 ms on a phone.

  • Minify JavaScript

    790 ms · 127 KiB

    127 KiB could be saved by minifying JavaScript.

  • 1,562 HTML elements

    The page has 1,562 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 1.1 s

    1.1 s

    Your server takes 1.1 s 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, Google Fonts and YouTube and others), adding 382 KiB and 200 ms of main-thread time.

  • Minify CSS

    160 ms · 32 KiB

    32 KiB could be saved by minifying CSS.

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 149 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.

1 checks passed
  • Main-thread work: 1.4 s

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

Core Web Vitals

5 to fix100
  • First Contentful Paint: 11.1 s

    11.1 s

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

  • Largest Contentful Paint: 29.4 s

    29.4 s

    Your largest element takes 29.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “개교 110주년 맞아 노벨물리학상 수상자 배리쉬 교수에 명예이학박사 학위 수여”.

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 29.8 s

    29.8 s

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

  • 30 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 95 ms

    95 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 625 ms

    625 ms

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

  • Total Blocking Time: 159 ms

    159 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

5 to fix18
  • Page weight: 15.7 MB in 85 requests

    15.7 MB

    Your homepage downloads 15.7 MB in 85 requests on a phone: images 12.8 MB (52), HTML 1.0 MB (1) and fonts 844 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 8.4 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    6.9 MB

    2 images are downloaded at several times the size a phone draws them, for example 1788244553238.png at 1,920 px wide, shown at 273 px. Resized copies would save about 6.9 MB.

  • 9 images in older formats

    9 images (10.0 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.

  • 4 images below the first screen load straight away

    4 images further down the page (8.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.4 g of CO₂ per visit

    4.45 g

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

Accessibility

8 to fixGoogle 8689
  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • Interactive controls must not be nested (8 elements)

    Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.

  • 6 tap targets too small

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

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

8 to fixGoogle 8362
  • No meta description

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

  • Title is short (5 characters)

    Your title is only 5 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.

  • 3 H1 headlines

    There are 3 <h1> headlines (“CAU 중앙대학교 CHUNG-ANG UNIVERSITY”, “비밀번호 확인” and “사이트맵”). One clear main headline is easier for people and search engines.

  • 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://www.cau.ac.kr/sitemap.xml, so Google discovers your pages only by following links.

  • 11 links crawlers can't follow

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

  • 298 internal links, 240 external

    The homepage links to 298 pages on cau.ac.kr and 240 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

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://www.cau.ac.kr/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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

3 to fix83
  • 3 pages share a title

    https://www.cau.ac.kr/index.do, / and https://www.cau.ac.kr/cms/FR_CON/BoardView.do all use the title “중앙대학교”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    /, https://www.cau.ac.kr/cms/FR_CON/index.do, https://www.cau.ac.kr/vr2020/seoul and https://www.cau.ac.kr/cms/FR_CON/BoardView.do have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.cau.ac.kr/vr2020/seoul and https://www.cau.ac.kr/cms/FR_CON/BoardView.do have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    /, https://www.cau.ac.kr/cms/FR_CON/index.do and https://www.cau.ac.kr/cms/FR_CON/BoardView.do 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.

  • 1 page slow to respond

    / took over 3 s to send its HTML from our server.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 33 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 97 words

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

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

2 checks passed
  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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 cau.ac.kr, 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 © 2018.

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
Chung-Ang University

Company

Founded
1918

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on cau.ac.kr, including 17 speed issues, 8 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