7.4 sec in total
1.4 sec
5.8 sec
300 ms
Click here to check amazing Imperial Palace content for South Korea. Otherwise, check out these important facts you probably never knew about imperialpalace.co.kr
임피리얼팰리스서울
Visit imperialpalace.co.krWe analyzed Imperialpalace.co.kr page load time and found that the first response time was 1.4 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
imperialpalace.co.kr performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value5.6 s
17/100
25%
Value16.6 s
0/100
10%
Value740 ms
40/100
30%
Value0.069
96/100
15%
Value13.5 s
11/100
10%
1378 ms
1282 ms
1089 ms
1490 ms
1530 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 94% of them (63 requests) were addressed to the original Imperialpalace.co.kr, 4% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Imperialpalace.co.kr.
Page size can be reduced by 421.0 kB (14%)
3.0 MB
2.5 MB
In fact, the total size of Imperialpalace.co.kr main page is 3.0 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.5 MB which makes up the majority of the site volume.
Potential reduce by 44.6 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 7.1 kB, which is 14% 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 44.6 kB or 86% of the original size.
Potential reduce by 41.5 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. Imperial Palace images are well optimized though.
Potential reduce by 276.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 276.0 kB or 79% of the original size.
Potential reduce by 58.9 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. Imperialpalace.co.kr needs all CSS files to be minified and compressed as it can save up to 58.9 kB or 84% of the original size.
Number of requests can be reduced by 11 (17%)
63
52
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imperial Palace. 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 4 to 1 for CSS and as a result speed up the page load time.
imperialpalace.co.kr
1378 ms
style.css
1282 ms
jquery-ui.css
1089 ms
jquery-1.9.1.min.js
1490 ms
jquery-ui.js
1530 ms
jquery.easing.1.3.js
724 ms
jquery.bxslider.js
1059 ms
jquery.gray.js
938 ms
script.js
1161 ms
respond.src.js
1263 ms
iscroll.js
1507 ms
common.js
1395 ms
reset.css
212 ms
kopubbatang.css
27 ms
pro_160405_maestro01_thum.jpg
2367 ms
pro_160405_thebar01_thum.jpg
3148 ms
pkg_1603_cine01_thum.jpg
2470 ms
pro_160316_jap01_thum.jpg
2673 ms
pkg_1603_luxury01_thum.jpg
2443 ms
pro_jap_160225_01_thum.jpg
2399 ms
pro_chi_160224_01_thum.jpg
2775 ms
pkg_160205_spring01_thum.jpg
2913 ms
img_logo.png
284 ms
ico_bar01.png
281 ms
ico_sns01.png
281 ms
ico_sns02.png
286 ms
ico_sns03.png
285 ms
ico_sns04.png
283 ms
ico_sns05.png
453 ms
gnb01.png
453 ms
gnb02.png
454 ms
gnb03.png
454 ms
gnb04.png
454 ms
gnb05.png
454 ms
gnb06.png
610 ms
gnb07.png
615 ms
gnb08.png
625 ms
btn_fullmenu.png
630 ms
btn_fullmenu2.png
634 ms
btn_close.png
660 ms
btn_mobile_prev.png
815 ms
bg_fullmenu.png
823 ms
popup_160404_01.jpg
1059 ms
img_main01.jpg
2092 ms
img_main02.jpg
2113 ms
img_main03.jpg
2155 ms
bg_main02.png
1035 ms
btn_more.png
1048 ms
popup_160404_02.jpg
1708 ms
tit_reservation.png
1325 ms
btn_reservation.png
1337 ms
ico_footer_sns01.png
1551 ms
ico_footer_sns02.png
1569 ms
ico_footer_sns03.png
1774 ms
ico_footer_sns04.png
1783 ms
ico_footer_sns05.png
1910 ms
ico_bar02.png
1977 ms
img_footer01.png
1946 ms
KoPubBatang-Bold.woff
134 ms
KoPubBatang-Regular.woff
243 ms
KoPubBatang-Light.woff
328 ms
img_footer02.png
1836 ms
img_footer03.png
1908 ms
img_footer04.png
1926 ms
ico_calendar.png
2012 ms
btn_prev.png
226 ms
btn_next.png
222 ms
imperialpalace.co.kr accessibility score
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
imperialpalace.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
imperialpalace.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imperialpalace.co.kr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Korean language. Our system also found out that Imperialpalace.co.kr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
imperialpalace.co.kr
Open Graph description is not detected on the main page of Imperial Palace. 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: