7.5 sec in total
1 sec
5.8 sec
682 ms
Click here to check amazing Gmpart content for South Korea. Otherwise, check out these important facts you probably never knew about gmpart.co.kr
Visit gmpart.co.krWe analyzed Gmpart.co.kr page load time and found that the first response time was 1 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
gmpart.co.kr performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value14.7 s
0/100
25%
Value9.1 s
13/100
10%
Value11,540 ms
0/100
30%
Value0.335
34/100
15%
Value22.2 s
1/100
10%
1041 ms
221 ms
402 ms
18 ms
440 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 77% of them (104 requests) were addressed to the original Gmpart.co.kr, 7% (9 requests) were made to Img.echosting.cafe24.com and 3% (4 requests) were made to App-storage-005.cafe24.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Gmpart.co.kr.
Page size can be reduced by 142.9 kB (10%)
1.5 MB
1.3 MB
In fact, the total size of Gmpart.co.kr main page is 1.5 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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 72.2 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 8.6 kB, which is 11% 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 72.2 kB or 89% of the original size.
Potential reduce by 44.4 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. Gmpart images are well optimized though.
Potential reduce by 26.3 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 26.3 kB or 68% of the original size.
Number of requests can be reduced by 17 (13%)
126
109
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gmpart. 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 as a result speed up the page load time.
gmpart.co.kr
1041 ms
common.js
221 ms
cid.generate.js
402 ms
wcslog.js
18 ms
optimizer.php
440 ms
photoslide2.app-runtime.cafe24.com
634 ms
optimizer.php
1070 ms
c40793c1a6a984e4f5ed58b694d81ba6.jpg
654 ms
mainboard2.html
287 ms
btn_prd_zoom.gif
390 ms
todayviewbn_01.jpg
627 ms
mainboard.html
294 ms
logo.png
204 ms
bookmark.png
215 ms
search_01.jpg
396 ms
search_03.jpg
405 ms
loginmenu_01.png
427 ms
loginmenu_02.png
482 ms
topmenu_01.png
489 ms
topmenu_02.png
593 ms
topmenu_03.png
605 ms
topmenu_04.png
640 ms
joinicon.gif
744 ms
category_tt.png
743 ms
community_tt.png
790 ms
bdmenu_01.png
806 ms
bdmenu_02.png
851 ms
bdmenu_03.png
848 ms
bdmenu_04.png
888 ms
bdmenu_05.png
898 ms
bdmenu_06.png
986 ms
call.png
1004 ms
bank.png
1050 ms
dailycheck.png
1061 ms
link_bn_01.png
1088 ms
link_bn_02.png
1108 ms
link_bn_03.png
1182 ms
link_bn_04.png
1204 ms
cc0b33a81eb28560b9ce9476b32042f7.jpg
1252 ms
banner_01.png
1273 ms
banner_02.png
1288 ms
banner_03.png
1317 ms
banner_04.png
1379 ms
todayviewbn_02.jpg
612 ms
icon_cash.gif
391 ms
icon_rec.gif
391 ms
icon_new_p.gif
394 ms
txt_progress.gif
394 ms
img_loading.gif
785 ms
26d2d1b33c4566bcd069cd36a7816acc.jpg
630 ms
9e70f098610811c598751a4dd9a1d46e.jpg
633 ms
2dba93ebf807e5519da74cd972a75f40.jpg
733 ms
banner_05.png
1402 ms
m
408 ms
centerroll_01.jpg
1386 ms
besticon.png
1291 ms
ygreen0614_2398.jpg
1484 ms
btn_board_more.gif
301 ms
optimizer.php
1268 ms
optimizer.php
1301 ms
optimizer.php
1630 ms
ygreen0614_1941.jpg
1263 ms
ygreen0614_2424.jpg
1493 ms
ygreen0614_2078.jpg
1270 ms
ygreen0614_2017.gif
1695 ms
ygreen0614_3053.jpg
1278 ms
ygreen0614_2428.jpg
1496 ms
c40793c1a6a984e4f5ed58b694d81ba6.jpg
628 ms
26d2d1b33c4566bcd069cd36a7816acc.jpg
629 ms
ygreen0614_2076.jpg
1321 ms
9e70f098610811c598751a4dd9a1d46e.jpg
631 ms
weblog.js
725 ms
bg-title.png
196 ms
2dba93ebf807e5519da74cd972a75f40.jpg
529 ms
async
1444 ms
SubCategory
1660 ms
ygreen0614_2429.jpg
1485 ms
ygreen0614_2475.jpg
1452 ms
ygreen0614_2474.jpg
1730 ms
ygreen0614_2529.jpg
1492 ms
ygreen0614_2383.jpg
1496 ms
ygreen0614_2479.jpg
1510 ms
ygreen0614_2538.jpg
1497 ms
centerroll_02.jpg
1527 ms
centerroll_04.jpg
1543 ms
maintt_02.png
1559 ms
ygreen0614_3263.jpg
1592 ms
ygreen0614_3258.jpg
1520 ms
ygreen0614_3259.jpg
1574 ms
ygreen0614_3251.jpg
1751 ms
c40793c1a6a984e4f5ed58b694d81ba6.jpg
1023 ms
26d2d1b33c4566bcd069cd36a7816acc.jpg
1237 ms
2dba93ebf807e5519da74cd972a75f40.jpg
1241 ms
9e70f098610811c598751a4dd9a1d46e.jpg
1039 ms
ygreen0614_3248.jpg
1750 ms
ygreen0614_3249.jpg
1562 ms
ygreen0614_3250.jpg
1588 ms
ygreen0614_3252.jpg
1525 ms
ygreen0614_3253.jpg
1570 ms
ygreen0614_3254.jpg
1597 ms
ygreen0614_3255.jpg
1622 ms
ico_board_main.gif
196 ms
m
456 ms
ygreen0614_3256.jpg
1569 ms
m
443 ms
ygreen0614_3257.jpg
1575 ms
ygreen0614_3260.jpg
1556 ms
ygreen0614_3261.jpg
1754 ms
ygreen0614_3262.jpg
1514 ms
ygreen0614_3264.jpg
1450 ms
ygreen0614_3265.jpg
1401 ms
ygreen0614_2355.jpg
1420 ms
weblog.js
197 ms
weblog.js
385 ms
ygreen0614_2352.jpg
1398 ms
rightmenu_04.jpg
1470 ms
bottommenu_01.png
1373 ms
bottommenu_02.png
1398 ms
bottommenu_03.png
1366 ms
bottommenu_04.png
1361 ms
bottommenu_05.png
1325 ms
bottommenu_06.png
1371 ms
bottom_call.png
1374 ms
bottom_bdmenu_01.png
1320 ms
bottom_bdmenu_02.png
1367 ms
bottom_bdmenu_03.png
1354 ms
bottom_bdmenu_04.png
1326 ms
bottom_bdmenu_05.png
1377 ms
bottom_review_tt.jpg
1385 ms
bottom_info.png
1321 ms
bottom_banner_01.png
1295 ms
bottom_banner_02.png
1256 ms
bottom_banner_03.png
1265 ms
main_notice_icon.png
1309 ms
arrow_img.png
1298 ms
gmpart.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-*] attributes do not match their roles
[role]s are not contained by their required parent element
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
gmpart.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
gmpart.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 uses legible font sizes
Tap targets are not sized appropriately
N/A
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gmpart.co.kr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Korean. Our system also found out that Gmpart.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.
gmpart.co.kr
Open Graph description is not detected on the main page of Gmpart. 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: