12.1 sec in total
4 sec
7.6 sec
499 ms
Welcome to seesay.co.kr homepage info - get ready to check See Say best content right away, or after learning these important things about seesay.co.kr
디자이너들이 직접 기획 및 디자인하여 생산하는 감성 디자인 가구 브랜드 시세이(SEESAY)입니다.
Visit seesay.co.krWe analyzed Seesay.co.kr page load time and found that the first response time was 4 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
seesay.co.kr performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value107.5 s
0/100
25%
Value14.0 s
1/100
10%
Value2,090 ms
7/100
30%
Value0.882
3/100
15%
Value16.4 s
5/100
10%
4038 ms
1192 ms
1085 ms
852 ms
1086 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 29% of them (42 requests) were addressed to the original Seesay.co.kr, 21% (30 requests) were made to Scontent.cdninstagram.com and 8% (12 requests) were made to App-storage-005.cafe24.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Seesay.co.kr.
Page size can be reduced by 497.7 kB (30%)
1.7 MB
1.2 MB
In fact, the total size of Seesay.co.kr main page is 1.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. 55% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 61.4 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 10.5 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 61.4 kB or 85% of the original size.
Potential reduce by 19.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. See Say images are well optimized though.
Potential reduce by 302.6 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 302.6 kB or 70% of the original size.
Potential reduce by 114.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. Seesay.co.kr needs all CSS files to be minified and compressed as it can save up to 114.2 kB or 82% of the original size.
Number of requests can be reduced by 32 (28%)
113
81
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of See Say. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
seesay.co.kr
4038 ms
jquery.min.js
1192 ms
common.js
1085 ms
css
852 ms
css
1086 ms
css
1190 ms
css
1190 ms
cid.generate.js
1083 ms
wcslog.js
886 ms
optimizer.php
1084 ms
sidemenu.js
1868 ms
side_modernizr.js
1094 ms
photoslide2.app-runtime.cafe24.com
1775 ms
optimizer.php
2090 ms
ef3acae31d7d60846203199505b7970c.jpg
655 ms
1423 ms
txt_progress.gif
701 ms
search_btn.gif
359 ms
top_logo.png
361 ms
banner1.jpg
687 ms
4th_banner1.jpg
360 ms
4th_banner2.jpg
684 ms
4th_banner3.jpg
498 ms
4th_banner4.jpg
688 ms
2th_banner1.jpg
1309 ms
2th_banner2.jpg
1295 ms
1th_banner1.jpg
2642 ms
footer_bn01.gif
853 ms
footer_bn02.gif
853 ms
footer_bn03.gif
855 ms
side_facebook.png
1049 ms
side_instagram.png
1046 ms
side_top.png
1050 ms
img_loading.gif
1055 ms
0e554d2939a50cd6fe7c3042baaa31f9.jpg
569 ms
4b4e8eb3446eb0f75251042d133cdc6c.jpg
571 ms
d2a4920b2594ae2cbf6e15d2b48a8a3f.jpg
571 ms
ba8a2e89c7eb5c2c5e0eff203be21fa9.jpg
574 ms
30d77e60806f92e5a7d2e1fb9fabc36a.jpg
574 ms
2930e0aae18bb2b074e35ab023164f6e.jpg
736 ms
b032f1a98d75f5635dbc7069e3db15d2.jpg
813 ms
688a9caa14a71a3607fd386ddc8af1a9.jpg
812 ms
8c41454677fc8e0a6bd004d64b82a6ea.jpg
815 ms
80d8b32e5ac9835b04b7eb3ac23fce1b.jpg
814 ms
82f4d7073237369b30575afaeb33c310.jpg
814 ms
bstrk.1.js
1112 ms
wkfQbvfT_02e2IWO3yYueQ.woff
26 ms
BVtM30trf7q_jfqYeHfjtA.woff
70 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
71 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
71 ms
boeCNmOCCh-EWFLSfVffDg.woff
70 ms
m
624 ms
slide_nav.png
724 ms
sfix-ico.png
535 ms
sfix-ico.png
590 ms
design102popup_3rd.html
822 ms
popup_1.html
739 ms
weblog.js
694 ms
SubCategory
1011 ms
side_tab.png
1009 ms
ef3acae31d7d60846203199505b7970c.jpg
661 ms
0e554d2939a50cd6fe7c3042baaa31f9.jpg
665 ms
4b4e8eb3446eb0f75251042d133cdc6c.jpg
661 ms
d2a4920b2594ae2cbf6e15d2b48a8a3f.jpg
663 ms
ba8a2e89c7eb5c2c5e0eff203be21fa9.jpg
656 ms
30d77e60806f92e5a7d2e1fb9fabc36a.jpg
658 ms
2930e0aae18bb2b074e35ab023164f6e.jpg
680 ms
b032f1a98d75f5635dbc7069e3db15d2.jpg
608 ms
688a9caa14a71a3607fd386ddc8af1a9.jpg
609 ms
80d8b32e5ac9835b04b7eb3ac23fce1b.jpg
604 ms
82f4d7073237369b30575afaeb33c310.jpg
607 ms
8c41454677fc8e0a6bd004d64b82a6ea.jpg
609 ms
ef3acae31d7d60846203199505b7970c.jpg
1306 ms
ba8a2e89c7eb5c2c5e0eff203be21fa9.jpg
2007 ms
4b4e8eb3446eb0f75251042d133cdc6c.jpg
2412 ms
30d77e60806f92e5a7d2e1fb9fabc36a.jpg
1838 ms
0e554d2939a50cd6fe7c3042baaa31f9.jpg
1738 ms
d2a4920b2594ae2cbf6e15d2b48a8a3f.jpg
2030 ms
logger.v4.1.js
529 ms
optimizer.php
288 ms
160316_login_popup.jpg
1052 ms
optimizer.php
581 ms
combined.css
27 ms
smoothDivScroll.css
25 ms
stack_161235.js
134 ms
jquery.min.js
32 ms
design102popupver2.css
364 ms
jquery-1.11.2.min.js
381 ms
design102popupver2.min.js
396 ms
2930e0aae18bb2b074e35ab023164f6e.jpg
2411 ms
80d8b32e5ac9835b04b7eb3ac23fce1b.jpg
1856 ms
b032f1a98d75f5635dbc7069e3db15d2.jpg
2632 ms
688a9caa14a71a3607fd386ddc8af1a9.jpg
2450 ms
82f4d7073237369b30575afaeb33c310.jpg
2059 ms
8c41454677fc8e0a6bd004d64b82a6ea.jpg
2057 ms
analytics.js
81 ms
stackpile.api-2ece4e50df.js
82 ms
12749838_542603302568307_1999332149_n.jpg
394 ms
12519584_248461742153390_247237142_n.jpg
395 ms
12797917_1749040761993958_668214383_n.jpg
466 ms
12826185_1513144372328346_218359355_n.jpg
530 ms
12822485_468380910032075_2062722816_n.jpg
531 ms
12826043_607982656018483_1265778302_n.jpg
534 ms
12728420_101667083561814_1977693792_n.jpg
558 ms
12784094_977922122296231_1743227493_n.jpg
557 ms
12328104_1023437987721721_1475557291_n.jpg
560 ms
12729650_199192833775936_2116926225_n.jpg
609 ms
1168402_1680743615535351_1918059141_n.jpg
607 ms
10632423_1577185485835531_1377623676_n.jpg
609 ms
12317850_1489514068022102_499591532_n.jpg
641 ms
12519145_738243029652803_237312840_n.jpg
643 ms
12558326_1038058052927288_86203816_n.jpg
642 ms
12547514_1499476577025628_1491646075_n.jpg
671 ms
12558895_1652088071719701_1235675909_n.jpg
672 ms
12558352_976683662425713_351766126_n.jpg
671 ms
12556055_1728949574004130_704503053_n.jpg
768 ms
10734991_483667305107135_993447577_n.jpg
770 ms
10732037_1535967913310575_1436071584_n.jpg
770 ms
10735351_1504056113197355_14445678_n.jpg
773 ms
10919602_717488458348136_1392899398_n.jpg
772 ms
10948337_326623387546060_2051996205_n.jpg
772 ms
10895375_341912756016265_805275037_n.jpg
848 ms
10955165_1559361437638742_585077605_n.jpg
846 ms
11023243_648113651984920_1221234448_n.jpg
849 ms
10956721_287485008042625_836500920_n.jpg
835 ms
11190746_772982169438002_2030430995_n.jpg
835 ms
11208483_1574450039509751_1051271404_n.jpg
839 ms
m
418 ms
collect
5 ms
collect
143 ms
popupbanner1.jpg
198 ms
popupbanner2.jpg
198 ms
popupbanner3.jpg
215 ms
btn1a.jpg
208 ms
btn2a.jpg
335 ms
btn3a.jpg
392 ms
btn1.jpg
359 ms
btn2.jpg
365 ms
btn3.jpg
385 ms
m
423 ms
tracker.1.tsp
1227 ms
nr-918.min.js
45 ms
a53393d12f
54 ms
seesay.co.kr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
seesay.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
seesay.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
Tap targets are not sized appropriately
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Seesay.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 Seesay.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.
seesay.co.kr
Open Graph description is not detected on the main page of See Say. 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: