8.7 sec in total
666 ms
7.8 sec
194 ms
Visit whypaymore.co.kr now to see the best up-to-date Whypaymore content for South Korea and also check out these interesting facts you probably never knew about whypaymore.co.kr
Visit whypaymore.co.krWe analyzed Whypaymore.co.kr page load time and found that the first response time was 666 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
whypaymore.co.kr performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value13.7 s
0/100
25%
Value16.3 s
1/100
10%
Value2,120 ms
7/100
30%
Value0.001
100/100
15%
Value20.4 s
2/100
10%
666 ms
871 ms
969 ms
392 ms
391 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 99% of them (148 requests) were addressed to the original Whypaymore.co.kr, 1% (2 requests) were made to Gtp2.acecounter.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Whypaymore.co.kr.
Page size can be reduced by 335.7 kB (21%)
1.6 MB
1.2 MB
In fact, the total size of Whypaymore.co.kr main page is 1.6 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. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 2.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 2.2 kB, which is 76% 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 2.4 kB or 84% of the original size.
Potential reduce by 125.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. Whypaymore images are well optimized though.
Potential reduce by 186.8 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 186.8 kB or 71% of the original size.
Potential reduce by 21.6 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. Whypaymore.co.kr needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 85% of the original size.
Number of requests can be reduced by 65 (44%)
148
83
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whypaymore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
whypaymore.co.kr
666 ms
www.whypaymore.co.kr
871 ms
default.asp
969 ms
re_body.css
392 ms
base2013.css
391 ms
wpm_jquery-1.6.2.min.js
968 ms
jquery-1.7.1.min.js
998 ms
rollBanner.js
395 ms
number_slideshow.js
585 ms
calendarNew.js
585 ms
cross_home_default2013.js
788 ms
Main_Transparent.js
770 ms
number_slideshow.css
774 ms
re_top.css
776 ms
grobject.js
962 ms
HomeTop.js
991 ms
re_footer.css
422 ms
re_quick_right.css
458 ms
QuickMenu.js
583 ms
login_line.gif
198 ms
logo.gif
201 ms
white.jpg
195 ms
retopmenu_Int.gif
199 ms
retopmenu_IntAirOff.gif
193 ms
retopmenu_SmartAirOff.gif
331 ms
retopmenu_CityAirOff.gif
384 ms
retopmenu_Dom.gif
385 ms
retopmenu_DomAirOff.gif
387 ms
retopmenu_Hotel.gif
386 ms
retopmenu_Eurail.gif
389 ms
maintop_banner_1.png
526 ms
maintop_ban_img1.jpg
976 ms
mainbanner_918.jpg
986 ms
1030_mainbanner.jpg
982 ms
1039_mainbanner.jpg
964 ms
mainbanner_DL_spring.jpg
995 ms
1038_mainbanner.jpg
1115 ms
btn_num1_on.gif
1158 ms
btn_num2_out.gif
1165 ms
btn_num3_out.gif
1174 ms
btn_num4_out.gif
1176 ms
btn_num5_out.gif
1189 ms
btn_num6_out.gif
1308 ms
domQuickSearch_menu1on.png
1351 ms
domQuickSearch_menu2off.png
1360 ms
main_img34.gif
1367 ms
main_img06.gif
1367 ms
main_img07.gif
1383 ms
main_img09.gif
1504 ms
main_img10.gif
1543 ms
main_img12.gif
1550 ms
main_img13.gif
1558 ms
main_img15.gif
1558 ms
main_img16.gif
1552 ms
gtp2.acecounter.com
655 ms
gtp2.acecounter.com
679 ms
main_img17.gif
1545 ms
main_img18.gif
1553 ms
main_img19.gif
1556 ms
main_img21.gif
1562 ms
main_img22.gif
1561 ms
main_img27.gif
1582 ms
main_img28_1.gif
1568 ms
main_img30.gif
1556 ms
main_img33.gif
1555 ms
main_soto_img04.png
1572 ms
main_img01.gif
1564 ms
main_img02.gif
1588 ms
main_img03.gif
1565 ms
main_img35.gif
1166 ms
main_img36.gif
1161 ms
txt_passengerNumber_main.gif
1165 ms
btn_airTicketSearch.gif
1167 ms
main_dom_img04.png
1178 ms
maintop_service_h3.jpg
1173 ms
maintop_service_img1_2.jpg
1360 ms
maintop_service_img1.jpg
1356 ms
maintop_service_img3.jpg
1361 ms
maintop_service_bt1_on.png
1168 ms
maintop_service_bt2_out.png
1177 ms
maintop_service_bt3_out.png
1173 ms
maintop_service_img2.jpg
1384 ms
lowprice_ttl.gif
1206 ms
TaxTotal_title_regional_lowprice.gif
1313 ms
MU.gif
1345 ms
icon_RoundTrip.gif
1332 ms
UA.gif
1221 ms
LH.gif
1217 ms
AY.gif
1321 ms
SQ.gif
1346 ms
KE.gif
1346 ms
PR.gif
1340 ms
lowprice_img.jpg
1232 ms
md_ttl.gif
1222 ms
more_white.gif
1322 ms
md_img01.gif
1360 ms
md_img02.gif
1349 ms
md_img03.gif
1340 ms
md_img04.gif
1238 ms
md_img05.gif
1227 ms
long-banner.gif
1327 ms
notice_ttl.gif
1353 ms
notice_img.jpg
1366 ms
newfare_ttl.gif
1341 ms
more_lightgrey.gif
1236 ms
newfare_ribon.png
1233 ms
newfare_txt.gif
1324 ms
2008Main_ThemeGoodImg_Bullet.gif
1346 ms
NH.gif
1355 ms
ico_NewAirSale_end.gif
1342 ms
MH.gif
1229 ms
CZ.gif
1212 ms
BA.gif
1282 ms
citicard_mainbanner.jpg
1395 ms
samsungcard_mainbanner.jpg
1374 ms
kbcard_mainbanner.jpg
1379 ms
event_3.jpg
1177 ms
20151204_datashop_mainbanner.jpg
1383 ms
event_5.jpg
1358 ms
faq_ttl.gif
1191 ms
more_grey.gif
1353 ms
qna_ttl.gif
1361 ms
contents4_imgnew.jpg
1744 ms
line_dot.gif
1336 ms
lineee.gif
1272 ms
footer_img1.gif
1323 ms
footer_img2.gif
1351 ms
footer_img3.gif
1361 ms
footer_img4.gif
1359 ms
imgfooter_1.jpg
1380 ms
quickBn_dom2.jpg
1359 ms
quickmenu_ttl.gif
1348 ms
quickmenu_img1.gif
1360 ms
quickmenu_img4.gif
1367 ms
quickmenu_img3.gif
1407 ms
quickmenu_img6.gif
1460 ms
quickmenu_img6_1.gif
1381 ms
quickmenu_img10.gif
1366 ms
quickmenu_img16.gif
1361 ms
quickmenu_img17.gif
1358 ms
quickmenu_img9.gif
1409 ms
quickmenu_img10.jpg
1455 ms
quickSearch_bg.jpg
1573 ms
bg_quick_sub.gif
1371 ms
main_img08.gif
1362 ms
main_img11.gif
1356 ms
maintop_servicebg.jpg
1418 ms
dot.gif
1452 ms
footer_bg222.jpg
1403 ms
loading.gif
1353 ms
whypaymore.co.kr accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
whypaymore.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
Issues were logged in the Issues panel in Chrome Devtools
whypaymore.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
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 uses 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 Whypaymore.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 Whypaymore.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.
whypaymore.co.kr
Open Graph description is not detected on the main page of Whypaymore. 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: