Website review, no card needed
hanjin.com website review
Visit site (opens in a new tab)Reviewed 30 October 202642 issues · 85 checks
This review found 42 issues worth fixing on hanjin.com, 18 of them high impact, across 85 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 24, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 25, 2026 | 80 ms |
| Aug 1, 2026 | 82 ms |
| Aug 8, 2026 | 88 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 92 ms |
| Sep 5, 2026 | 86 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 86 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 84 ms |
| Oct 10, 2026 | 79 ms |
| Oct 24, 2026 | 79 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
Speed
Render-blocking requests
4.4 s33 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.4 s.
Improve image delivery
1.8 s · 1.4 MB21 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Reduce unused JavaScript
1.1 s · 194 KiBAbout 194 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Font display
1.2 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.2 s).
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
600 ms · 145 KiBAbout 145 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
350 ms · 25 KiB1 file is served with short cache lifetimes, so returning visitors download them again (25 KiB).
Google Tag Manager adds 294 ms
294 msGoogle Tag Manager costs a phone 294 ms of main-thread work and 309 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,333 HTML elements
The page has 2,333 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 784 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, kakao.com and Unpkg and others), adding 523 KiB and 346 ms of main-thread time.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 244 ms. During a long task the page ignores taps.
Minify JavaScript
19 KiB19 KiB could be saved by minifying JavaScript.
Minify CSS
13 KiB13 KiB could be saved by minifying CSS.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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
Server response: 177 ms
177 msYour server sent the HTML in 177 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.8 s
12.8 sYour largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “한진 브리온 협약식 홍보 이미지”.
Time to Interactive: 13.2 s
13.2 sThe page becomes fully interactive after 13.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.529
0.529The layout shifts by 0.529 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
32 images without width and height
32 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 333 ms
333 msScripts block taps and scrolling for 333 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 80 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 79 ms
79 msReal visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 634 ms
634 msReal visitors wait 634 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 13.9 MB in 122 requests
13.9 MBYour homepage downloads 13.9 MB in 122 requests on a phone: fonts 6.8 MB (10), images 6.4 MB (59) and scripts 547 KiB (26). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
business1_02.jpg weighs 684 KiB. On a phone connection a single image that size takes seconds.
27 images in older formats
27 images (5.6 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 far larger than shown
282 KiB4 images are downloaded at several times the size a phone draws them, for example 5H7uI9B8MGaxfLqs.JPG at 2,000 px wide, shown at 606 px. Resized copies would save about 282 KiB.
8 images below the first screen load straight away
8 images further down the page (229 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.0 g of CO₂ per visit
3.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.95 g of CO₂e: 474.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
14 buttons without a name
14 buttons have no accessible name, so screen readers announce just “button”.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 39 images in the HTML carry an alt attribute.
SEO
Title is short (16 characters)
Your title is only 16 characters: “글로벌 종합물류기업 (주)한진”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (61 characters)
Your meta description is only 61 characters: “글로벌 종합물류기업. 국내 택배, 국내외 풀필먼트, 수출입 물류, 육상/항공/해상운송, 하역, 고객센터 안내.”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“스킵네비게이션” 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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
357 internal links, 39 external
The homepage links to 357 pages on hanjin.com and 39 external pages.
4 checks passed
Structured data in place
Structured data found: Organization.
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://www.hanjin.com/resources/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://hanjin.com/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
1 linked page is broken
Your homepage links to https://hanjin.com/kor/CMS/Contents/Contents.do, which answers with an error. Visitors hit a dead end and search engines drop it.
12 pages share a title
https://hanjin.com/kor/Main.do, https://hanjin.com/kor/CMS/DeliveryMgr/WaybillSch.do, https://hanjin.com/kor/CMS/DeliveryMgr/Reserve1.do, https://hanjin.com/kor/CMS/DeliveryMgr/Reserve3.do, https://hanjin.com/kor/CMS/DeliveryMgr/Reserve4.do and https://hanjin.com/kor/CMS/DeliveryMgr/Reserve5.do and 6 others all use the title “글로벌 종합물류기업 (주)한진”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://hanjin.com/kor/CMS/Board/Board.do has no meta description, so Google writes the search snippet from whatever text it finds.
11 pages share a meta description
https://hanjin.com/kor/CMS/DeliveryMgr/WaybillSch.do, https://hanjin.com/kor/CMS/DeliveryMgr/Reserve1.do, https://hanjin.com/kor/CMS/DeliveryMgr/Reserve3.do, https://hanjin.com/kor/CMS/DeliveryMgr/Reserve4.do, https://hanjin.com/kor/CMS/DeliveryMgr/Reserve5.do and https://hanjin.com/kor/CMS/DeliveryMgr/Reserve6.do and 5 others use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://hanjin.com/kor/CMS/Board/Board.do has no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://hanjin.com/kor/CMS/DeliveryMgr/WaybillSch.do, https://hanjin.com/kor/CMS/DeliveryMgr/Reserve4.do, https://hanjin.com/kor/CMS/DeliveryMgr/ReserveConfirm.do and https://hanjin.com/kor/CMS/TotalQuestionMgr/Write1.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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
3 checks passed
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 12 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
92 of 114 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.
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.
Only about 105 words
The homepage has only about 105 words of visible text; thin pages give Google and first-time buyers little to go on.
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
4 short forms
4 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
3 trackers load before any consent
3Before 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.
3 cookies set on arrival
3Opening 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.
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 hanjin.com, 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 © 2021.
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Company
- Employees
- 2,338
- Founded
- 1977
- Headquarters
- Seoul
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on hanjin.com, including 17 speed issues, 4 SEO issues and 5 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.