9.5 sec in total
1 sec
6.8 sec
1.6 sec
Visit princessmarie.co.kr now to see the best up-to-date Princessmarie content and also check out these interesting facts you probably never knew about princessmarie.co.kr
Visit princessmarie.co.krWe analyzed Princessmarie.co.kr page load time and found that the first response time was 1 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
princessmarie.co.kr performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value24.3 s
0/100
25%
Value13.6 s
2/100
10%
Value200 ms
90/100
30%
Value0.834
4/100
15%
Value11.2 s
20/100
10%
1036 ms
983 ms
22 ms
1224 ms
791 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 90% of them (128 requests) were addressed to the original Princessmarie.co.kr, 2% (3 requests) were made to Web15.logcounter.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Princessmarie.co.kr.
Page size can be reduced by 801.6 kB (13%)
6.3 MB
5.5 MB
In fact, the total size of Princessmarie.co.kr main page is 6.3 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. 80% 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 5.9 MB which makes up the majority of the site volume.
Potential reduce by 69.8 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 12.4 kB, which is 15% 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 69.8 kB or 83% of the original size.
Potential reduce by 434.7 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. Princessmarie images are well optimized though.
Potential reduce by 261.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 261.0 kB or 76% of the original size.
Potential reduce by 36.1 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. Princessmarie.co.kr needs all CSS files to be minified and compressed as it can save up to 36.1 kB or 83% of the original size.
Number of requests can be reduced by 21 (15%)
140
119
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Princessmarie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
princessmarie.co.kr
1036 ms
common.css
983 ms
wcslog.js
22 ms
jquery-1.7.2.min.js
1224 ms
flash.js
791 ms
rightbanner.js
593 ms
bookmark.js
404 ms
shopRbanner.html
600 ms
header.1.css
605 ms
css
24 ms
css
36 ms
main.js
607 ms
rollbar.js
611 ms
footer.1.js
423 ms
detailpage.js
619 ms
jquery.language.js
619 ms
jquery.option.js
1004 ms
Log_script_logsid.html
625 ms
cookie.js
789 ms
common.js
796 ms
icon_cs.gif
198 ms
toplogo.gif
220 ms
icon_all.gif
380 ms
popup_icon_01.png
386 ms
popup_icon_02.png
392 ms
popup_icon_03.png
420 ms
popup_icon_04.png
425 ms
pop_btn_close.png
578 ms
icon_search.gif
581 ms
btn_board.png
589 ms
btn_close.png
595 ms
mainimg01.jpg
2033 ms
mainimg02.jpg
2674 ms
mainimg03.jpg
1363 ms
view_notice.gif
776 ms
leftimg.jpg
1570 ms
imgbanner_01.jpg
790 ms
imgbanner_02.jpg
1167 ms
imgbanner_03.jpg
1185 ms
imgbanner_04.jpg
1560 ms
mainbtn_01.png
1383 ms
mainbtn_02.png
1556 ms
0130050000043.jpg
1777 ms
0160040000063.jpg
1755 ms
0160040000023.jpg
1951 ms
0130050000053.jpg
1959 ms
0130020000383.jpg
1950 ms
0160040000033.jpg
1974 ms
0120010000643.jpg
2147 ms
0150020000233.jpg
2148 ms
0130050000063.jpg
2348 ms
23
2163 ms
4411
2056 ms
0130060000403.gif
2163 ms
4304
2162 ms
4412
2163 ms
scroll.css
2191 ms
0130060000363.jpg
2231 ms
4413
2226 ms
0130020000033.jpg
2218 ms
4305
2215 ms
0130030000413.jpg
2238 ms
20
2382 ms
0160040000073.jpg
2226 ms
4414
2223 ms
0120030000083.jpg
2215 ms
0130050000073.gif
2249 ms
0160040000053.jpg
2290 ms
0160040000043.jpg
2209 ms
0150020000213.jpg
1833 ms
4410
1811 ms
0130060000663.jpg
1641 ms
0120010000593.jpg
1661 ms
0120020000273.jpg
1637 ms
6
1634 ms
0120020000263.jpg
1631 ms
0120010000633.jpg
1441 ms
0120020000613.jpg
1470 ms
0120010000623.jpg
1508 ms
4303
1436 ms
0120020000283.jpg
1431 ms
21
1421 ms
22
1366 ms
0130020000223.jpg
1301 ms
0130060000543.jpg
1433 ms
0120010000413.jpg
1413 ms
0130060000383.jpg
1360 ms
0130010000043.jpg
1249 ms
0120020000483.jpg
1302 ms
0120020000223.jpg
1500 ms
0120020000213.jpg
1410 ms
fbevents.js
32 ms
0130030000123.jpg
1319 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
35 ms
wkfQbvfT_02e2IWO3yYueQ.woff
40 ms
106 ms
0120020000233.jpg
1187 ms
0140010000253.gif
1190 ms
0130020000053.jpg
1250 ms
0120030000143.jpg
1374 ms
m
413 ms
[sr].gif
600 ms
mslog.js
1060 ms
user_basket_quantity.html
1535 ms
0130030000053.jpg
1314 ms
0130060000413.gif
1194 ms
0130030000213.jpg
1451 ms
0130030000423.jpg
1257 ms
0120010000073.jpg
1375 ms
0120020000313.jpg
1352 ms
0120020000063.jpg
1196 ms
0130030000023.jpg
1264 ms
0130020000013.jpg
1377 ms
0130020000093.jpg
1380 ms
0130060000353.jpg
1342 ms
0130060000653.jpg
1323 ms
0120020000333.jpg
1453 ms
0140010000373.jpg
1270 ms
0150020000013.jpg
1378 ms
0130030000273.jpg
1381 ms
Conf_dlfp2013.js
394 ms
0150020000243.jpg
1336 ms
0150020000223.jpg
1198 ms
0120010000673.jpg
1276 ms
0120020000643.jpg
1377 ms
escrow_01.gif
1380 ms
escrow_02.gif
1331 ms
escrow_03.gif
1326 ms
escrow_04.gif
1259 ms
escrow_05.gif
1283 ms
escrow_06.gif
1378 ms
f_menu01.gif
1384 ms
[sr].gif
395 ms
emd_pt.js
394 ms
f_menu02.gif
1328 ms
ms.log
401 ms
f_menu03.gif
1200 ms
f_menu04.gif
1258 ms
btn_top.png
1282 ms
line_log.gif
1372 ms
line_main_tit.gif
1319 ms
line_cs.gif
1321 ms
HTTP_s.js
785 ms
princessmarie.co.kr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
princessmarie.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
princessmarie.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Princessmarie.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 Princessmarie.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.
princessmarie.co.kr
Open Graph description is not detected on the main page of Princessmarie. 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: