sk.com website review

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

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

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

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

About 289 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

1 third-party service load with your homepage (Vimeo), adding 9.2 MB and 253 ms of main-thread time.

Vimeo costs a phone 253 ms of main-thread work and 9.2 MB 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.

5 images could be 265 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

41 KiB could be saved by minifying JavaScript.

32 KiB could be saved by minifying CSS.

A phone's processor spends 2.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Scripts block taps and scrolling for 272 ms in total while the page loads. Good is under 200 ms.

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

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.

Your homepage downloads 12.8 MB in 109 requests on a phone: other files 7.9 MB (31), images 2.4 MB (40) and scripts 1.1 MB (14). Under 2 MB keeps phones on slow connections fast.

11 images (1.5 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.

6 images further down the page (1.1 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 3.64 g of CO₂e: 436.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 tap target is too small or too close together to hit reliably with a finger.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

ARIA input fields do not have accessible names (1 element).

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Your title is only 2 characters: “SK”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your canonical URL points to sk.co.kr, not sk.com, so Google may credit that host instead.

Your meta description is only 2 characters: “SK”. 70 to 160 characters is enough to sell the click.

There are 17 <h1> headlines (“”, “GNB Menu” and “Content”). One clear main headline is easier for people and search engines.

Structured data found (Organization) but with 1 problem, for example “Organization: url points at a different host (https://www.sk.co.kr)”.

The homepage links to 60 pages on sk.com and 13 external pages.

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.

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

/ and https://sk.com/en/index.jsp all use the title “SK”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://sk.com/en/index.jsp, https://sk.com/en/about/about.jsp, https://sk.com/en/about/history.jsp, https://sk.com/en/about/skms.jsp, https://sk.com/en/about/supex.jsp and https://sk.com/en/about/affiliates.jsp and 9 others use the same meta description. A description written for each page earns more clicks.

https://sk.com/en/about/history.jsp took over 3 s to send its HTML from our server.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage carries about 350 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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 9 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.