snu.ac.kr website review

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

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

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

30 images could be 4.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

81 files are served with short cache lifetimes, so returning visitors download them again (886 KiB).

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

145 KiB could be saved by minifying JavaScript.

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

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

Your server takes 647 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 168 KiB and 95 ms of main-thread time.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “서울대학교 개교 80주년 엠블럼(1946 ~ 2026)”.

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

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

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

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

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

Your homepage downloads 22.4 MB in 88 requests on a phone: media 13.4 MB (3), images 6.5 MB (64) and fonts 1.1 MB (7). Under 2 MB keeps phones on slow connections fast.

25 images (6.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.

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

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

9 elements hidden from screen readers can still receive keyboard focus.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Some list items are not inside a list.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 5 characters: “서울대학교”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 11 <h1> headlines (“서울대학교”, “2026 SNU FASHION SHOW 〈N/A〉 런웨이” and “2026 SNU FASHION SHOW 〈N/A〉”). One clear main headline is easier for people and search engines.

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

The homepage links to 280 pages on snu.ac.kr and 128 external pages.

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.

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

robots.txt blocks GPTBot, ClaudeBot 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.

https://snu.ac.kr/academics/undergraduate/snucollege, https://snu.ac.kr/academics/undergraduate/colleges, https://snu.ac.kr/academics/undergraduate/curriculum, https://snu.ac.kr/academics/graduate/graduate_schools, https://snu.ac.kr/academics/graduate/professional_graduate_schools and https://snu.ac.kr/academics/graduate/curriculum and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://snu.ac.kr/academics/undergraduate/snucollege, https://snu.ac.kr/academics/undergraduate/colleges, https://snu.ac.kr/academics/undergraduate/curriculum, https://snu.ac.kr/academics/graduate/graduate_schools, https://snu.ac.kr/academics/graduate/professional_graduate_schools and https://snu.ac.kr/academics/graduate/curriculum and 6 others 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.

https://snu.ac.kr/academics/undergraduate/snucollege, https://snu.ac.kr/academics/undergraduate/colleges, https://snu.ac.kr/academics/undergraduate/curriculum, https://snu.ac.kr/academics/graduate/graduate_schools, https://snu.ac.kr/academics/graduate/curriculum and https://snu.ac.kr/academics/non_degree_courses took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 94 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Executing inline event handler violates the following Content Security Policy directive 'script-src 'self' 'nonce-0b5e0…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.