47.1 sec in total
2.9 sec
42.1 sec
2.1 sec
Click here to check amazing Resom content for South Korea. Otherwise, check out these important facts you probably never knew about resom.co.kr
리솜리조트
Visit resom.co.krWe analyzed Resom.co.kr page load time and found that the first response time was 2.9 sec and then it took 44.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 20 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
resom.co.kr performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value6.7 s
7/100
25%
Value9.5 s
11/100
10%
Value60 ms
100/100
30%
Value0.92
3/100
15%
Value5.8 s
67/100
10%
2881 ms
273 ms
1584 ms
723 ms
1228 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 85% of them (98 requests) were addressed to the original Resom.co.kr, 3% (4 requests) were made to F.vimeocdn.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Resom.co.kr.
Page size can be reduced by 871.0 kB (23%)
3.7 MB
2.9 MB
In fact, the total size of Resom.co.kr main page is 3.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 43.0 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 8.8 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.0 kB or 80% of the original size.
Potential reduce by 181.8 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Resom images are well optimized though.
Potential reduce by 380.0 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 380.0 kB or 72% of the original size.
Potential reduce by 266.2 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Resom.co.kr needs all CSS files to be minified and compressed as it can save up to 266.2 kB or 86% of the original size.
Number of requests can be reduced by 17 (19%)
88
71
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Resom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
resom.co.kr
2881 ms
273 ms
main.asp
1584 ms
reset.css
723 ms
layout.css
1228 ms
style.css
4043 ms
jquery.min.js
146 ms
top_navi.js
481 ms
jquery.fancybox-1.3.4.pack.js
1539 ms
jquery.fancybox-1.3.4.css
967 ms
main.css
1212 ms
owl.carousel.css
1236 ms
owl.theme.css
1495 ms
owl.transitions.css
1512 ms
jquery.flexslider.js
2745 ms
owl.carousel.js
2734 ms
nanumgothic.css
54 ms
analytics.js
211 ms
ico_alert.gif
352 ms
ico_ie.gif
343 ms
ico_chrome.gif
352 ms
ico_mozila.gif
343 ms
ico_safari.gif
349 ms
ico_opera.gif
353 ms
ico_close.gif
566 ms
reservation_btn.gif
566 ms
logo.gif
577 ms
all_menu.gif
570 ms
m_logo.gif
1529 ms
calendar_btn.gif
734 ms
menu_close_btn.png
1462 ms
L2016033109273221950_00.jpg
11170 ms
L2016033010583493500_01.jpg
2345 ms
L2016031715180591960_00.jpg
20289 ms
L2016031616500192260_01.jpg
3138 ms
L2016031715175548850_00.jpg
13969 ms
L2015052610540164020_01.jpg
2820 ms
L2016031715272273590_00.jpg
17001 ms
L2015102320170899310_01.jpg
4411 ms
notice_arrow01.gif
3368 ms
notice_arrow02.gif
3614 ms
main_icon01.gif
3858 ms
main_icon02.gif
4111 ms
main_icon03.gif
4349 ms
main_icon04.gif
4623 ms
all_event.gif
4643 ms
L2016040814052446300_01.jpg
6895 ms
L2016040717115359810_01.jpg
8341 ms
L2016040513160382130_01.jpg
9935 ms
L2016040513150652680_01.jpg
11449 ms
L2016040418350571200_01.jpg
14218 ms
L2016032515381757600_01.jpg
13789 ms
L2016031409025816450_01.jpg
16907 ms
L2016030816071897710_01.jpg
16022 ms
L2016022919474297570_01.jpg
16929 ms
L2016022919150195540_01.jpg
16786 ms
L2016022918570366950_01.jpg
18921 ms
L2016022918232952600_01.jpg
19249 ms
L2016022918210266110_01.jpg
18346 ms
collect
105 ms
NanumGothic-Bold.woff
1030 ms
NanumGothic-ExtraBold.woff
1378 ms
NanumGothic-Regular.woff
1423 ms
L2016012713411974440_01.jpg
18360 ms
collect
924 ms
L2015102211174743460_01.jpg
19326 ms
L2015093011310186510_01.jpg
19728 ms
L2016011512463375250_01.jpg
19723 ms
L2016031509483525800_01.jpg
19562 ms
114522894
1081 ms
L2015082513281246810_01.jpg
19541 ms
L2015082513193427400_01.jpg
19820 ms
player.js
567 ms
player.css
383 ms
ga.js
462 ms
vuid.min.js
543 ms
160407%EA%B5%AD%ED%9A%8C%EC%9D%98%EC%9B%90%EC%84%A0%EA%B1%B0_%EB%B2%A0%EB%84%88.jpg
20479 ms
__utm.gif
261 ms
proxy.html
318 ms
news_img02.jpg
19707 ms
__utm.gif
150 ms
close_btn.png
17957 ms
default-gray_60x60.png
125 ms
news_img03.jpg
19121 ms
zzz.jpg
19176 ms
top_arrow01.png
17404 ms
1455931998318.jpg
20409 ms
1455931998867.jpg
20157 ms
DSC09801.jpg
19912 ms
2016%EA%B2%A8%EC%9A%B8%20%EC%95%88%EB%A9%B4%EB%8F%84%20(3).jpg
19871 ms
%EB%B6%80%ED%83%81%ED%95%B4%EC%9A%94%EC%97%84%EB%A7%88_%EC%A0%9C%EC%B2%9C_%EA%B0%9D%EC%8B%A4%20%EB%82%AE3.jpg
19638 ms
%EB%A6%AC%EC%86%9C%ED%8F%AC%EB%A0%88%EC%8A%A4%ED%8A%B8%EA%B2%A8%EC%9A%B830%EC%B4%88_%EC%B5%9C%EC%A2%85%200000026885ms.png
19617 ms
aaa.jpg
20360 ms
%EB%B9%9B1%20(25).JPG
19910 ms
IMG_6079.jpg
20311 ms
df1.jpg
20125 ms
DSC09060.jpg
19801 ms
%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_R%203.jpg
17245 ms
ddf.jpg
20271 ms
df.jpg
20023 ms
banner.jpg
17515 ms
blog_btn.gif
14394 ms
facebook_btn.gif
14592 ms
norton_logo.gif
14910 ms
icon_f01.png
14785 ms
icon_f02.png
13181 ms
header_bg01.gif
13307 ms
gnb_bg01.gif
13038 ms
point_07.gif
12722 ms
bg_story.gif
12495 ms
footer_gap01.gif
12286 ms
ms_on.png
12297 ms
ms_off.png
12339 ms
m01_l.png
12519 ms
m01_r.png
12536 ms
resom.co.kr accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
resom.co.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
resom.co.kr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document doesn't use legible font sizes
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Resom.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Resom.co.kr main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
resom.co.kr
Open Graph description is not detected on the main page of Resom. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: