20.3 sec in total
1.1 sec
18.6 sec
641 ms
Click here to check amazing Phonesawa content for South Korea. Otherwise, check out these important facts you probably never knew about phonesawa.co.kr
폰사와::갤럭시 Z플립5 사전예약 ● 갤럭시 Z폴드5 사전예약 혜택 ● 30만원 이상 할인 ● 갤럭시 워치5 프로 등 선택사은품 ● Galaxy 제트플립5 & 제트폴드5 사전예약 제조사 사은품, 갤럭시 Z플립5 & Z폴드5 출시일, SKT, KT, LGU+ Galaxy Z flip 5 & Z fold 5 통신사용 사전예약 할인, 사전예약 개통 6개월 유지기...
Visit phonesawa.co.krWe analyzed Phonesawa.co.kr page load time and found that the first response time was 1.1 sec and then it took 19.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
phonesawa.co.kr performance score
name
value
score
weighting
Value13.4 s
0/100
10%
Value21.2 s
0/100
25%
Value30.5 s
0/100
10%
Value2,770 ms
3/100
30%
Value0.99
2/100
15%
Value39.8 s
0/100
10%
1104 ms
159 ms
248 ms
602 ms
607 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 85% of them (135 requests) were addressed to the original Phonesawa.co.kr, 2% (3 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Cdn.channel.io. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Phonesawa.co.kr.
Page size can be reduced by 411.0 kB (13%)
3.3 MB
2.9 MB
In fact, the total size of Phonesawa.co.kr main page is 3.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. 65% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 117.3 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 31.1 kB, which is 23% 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 117.3 kB or 86% of the original size.
Potential reduce by 109.0 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. Phonesawa images are well optimized though.
Potential reduce by 170.7 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 170.7 kB or 28% of the original size.
Potential reduce by 13.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. Phonesawa.co.kr needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 42% of the original size.
Number of requests can be reduced by 41 (27%)
151
110
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phonesawa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
index
1104 ms
wcslog.js
159 ms
kp.js
248 ms
common.css
602 ms
buttons.css
607 ms
jquery-ui-1.8.16.custom.css
629 ms
jquery.min.js
851 ms
jquery-ui.min.js
1260 ms
jquery.poshytip.min.js
1163 ms
jquery.activity-indicator-1.0.0.min.js
1173 ms
jquery.cookie.js
1175 ms
jquery.slides.min.js
1214 ms
jquery.bxslider.js
1494 ms
jquery.placeholder.js
1731 ms
custom-select-box.js
1757 ms
common.js
1798 ms
front-layout.js
1837 ms
base64.js
1889 ms
goods-display.js
2130 ms
board-display.js
2296 ms
script.js
2435 ms
highcharts.js
58 ms
protect_script_v2.js
995 ms
js
77 ms
jquery.ui.touch-punch.min.js
2416 ms
jquery.anibanner.js
2463 ms
anibanner.css
2454 ms
facebook.js
2516 ms
roosevelt.js
1072 ms
nanumgothic.css
38 ms
common-function.js
1077 ms
echo.js
445 ms
analytics.js
44 ms
icoHeader01.png
375 ms
icoHeader03.png
401 ms
icoHeader04.png
425 ms
logo.png
629 ms
btnSearch.png
629 ms
menu01.png
1006 ms
menu02.png
1032 ms
usim_btn.jpg
1056 ms
ip9.jpg
1070 ms
event.png
1232 ms
menu09_3.png
1248 ms
menu06.png
1626 ms
menu07.png
1663 ms
moneytree.png
1646 ms
faq.png
1688 ms
hogaeng.png
1797 ms
contact.png
1867 ms
ttmobile.jpg
2250 ms
top.png
2260 ms
popup_17145414262706.png
2480 ms
popup_17134991787840.jpg
2738 ms
band_btn_close.gif
2363 ms
band_btn_open.gif
2481 ms
titleHeader01.jpg
2833 ms
3278_2023120814240844.jpg
2852 ms
icoView.png
2936 ms
3289_2024010815082860.jpg
3321 ms
3288_2024010815042968.jpg
3322 ms
3292_2024010815231268.jpg
3526 ms
3293_2024010815463561.jpg
3587 ms
3286_2024010814072469.jpg
3616 ms
3323_2024041118184359.png
3913 ms
25120022list1.png
4306 ms
29112753list1.jpg
3941 ms
19192951list1.jpg
4366 ms
PN_3Rfi-oW3hYwmKDpxS7F_D-djb.ttf
50 ms
PN_oRfi-oW3hYwmKDpxS7F_LQv3LyVsj.ttf
78 ms
PN_oRfi-oW3hYwmKDpxS7F_LXv7LyVsj.ttf
80 ms
collect
39 ms
sdk.js
39 ms
b240110e162242u852
768 ms
sdk.js
36 ms
aac
987 ms
ch-plugin-web.js
27 ms
ch-plugin-core.bb5f2d30.vendor.js
14 ms
ch-plugin-core-20240813181636.js
19 ms
09160227list1.jpg
4011 ms
titleHeader02.jpg
4282 ms
06134328list1.png
4298 ms
01174843list1.jpg
4208 ms
01174742list1.jpg
4300 ms
ba.v1.0.0.min.js
20 ms
ba
780 ms
01174628list1.jpg
3937 ms
3285_2024010814072160.jpg
4199 ms
3284_2024010814071567.jpg
4447 ms
3283_2024010814070966.jpg
4498 ms
27105028list1.png
4423 ms
titleHeader03.jpg
4264 ms
23141218list1.png
4100 ms
3140_2023021711210467.png
4403 ms
3302_2024011716131863.jpg
4425 ms
3303_2024011716165765.jpg
4407 ms
ba
426 ms
3287_2024010815004965.jpg
4598 ms
3290_2024010815110262.jpg
4593 ms
titleHeader04.jpg
4063 ms
3306_2024011717262361.jpg
4375 ms
3305_2024011717251366.jpg
4313 ms
3304_2024011717235068.jpg
4228 ms
3294_2024010815500862.jpg
4613 ms
3291_2024010815202269.jpg
4454 ms
3279_2023120814373148.jpg
4218 ms
31194709list1.jpg
4564 ms
19170959list1.jpg
4355 ms
3297_2024011016372064.png
4143 ms
3199_2023083016465265.jpg
4528 ms
ictmarket.png
4149 ms
txtTel.png
4229 ms
icoClose.png
4293 ms
icon_bar_open.png
4082 ms
icon_bar_closebtn.png
4097 ms
rmenu01.png
4040 ms
rmenu02.png
4134 ms
rmenu03.png
4069 ms
btnCompare.png
4132 ms
btnDantong2.png
3912 ms
titleRight01.png
3891 ms
_thumb_37caedc94a5632cd199ebd49449cc4ce1857343.png
4009 ms
_thumb_c1137649f9fb16425664505933a7d8c32339243.png
4495 ms
_thumb_70a6afda95917c31b7f7394bab0236ea1208155.jpg
4338 ms
_thumb_85c0857ba49058c6d8792279ab795b811743304.jpg
3895 ms
titleRight02.png
3715 ms
btnAllright02.png
3720 ms
titleRight03.png
3896 ms
gong_title_btn.png
4102 ms
bgSearch.png
4299 ms
menu_under.png
3799 ms
btnAllmenu.png
3818 ms
icoCompany.png
3906 ms
boxPrice.png
3750 ms
boxPrice2.png
3961 ms
bgHotdeal.png
4767 ms
boxbanner01.jpg
4097 ms
boxbanner02.jpg
4267 ms
boxbanner03.jpg
4457 ms
bgRight.png
3595 ms
btnBg.gif
4020 ms
bgRight01.png
4296 ms
bgRight02.png
4230 ms
bgRight03.png
4303 ms
images_1.jpg
4682 ms
images_2.jpg
4637 ms
images_3.jpg
4866 ms
images_4.jpg
4617 ms
images_5.jpg
4652 ms
btn4_prev.png
4322 ms
btn4_next.png
4696 ms
navi_squ_on.png
4622 ms
navi_squ.png
4476 ms
4629 ms
images_1.jpg
5378 ms
images_2.jpg
5115 ms
4709 ms
403.html
581 ms
403.html
408 ms
phonesawa.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
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>).
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.
phonesawa.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
phonesawa.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
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phonesawa.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Phonesawa.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.
phonesawa.co.kr
Open Graph description is not detected on the main page of Phonesawa. 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: