9.9 sec in total
1.5 sec
7.8 sec
688 ms
Welcome to progainer.co.kr homepage info - get ready to check Progainer best content right away, or after learning these important things about progainer.co.kr
믿을 수 있는 단백질 프로게이너 식약처 건강기능식품, GMP, 식품이력추적, 단백질보충제, 헬스보충제
Visit progainer.co.krWe analyzed Progainer.co.kr page load time and found that the first response time was 1.5 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
progainer.co.kr performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value7.6 s
4/100
25%
Value12.4 s
3/100
10%
Value780 ms
37/100
30%
Value0.079
94/100
15%
Value21.9 s
1/100
10%
1454 ms
1040 ms
62 ms
1278 ms
838 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 92% of them (101 requests) were addressed to the original Progainer.co.kr, 3% (3 requests) were made to Web15.logcounter.com and 2% (2 requests) were made to Serial15.logcounter.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Progainer.co.kr.
Page size can be reduced by 1.1 MB (46%)
2.3 MB
1.3 MB
In fact, the total size of Progainer.co.kr main page is 2.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. 45% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 52.1 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.3 kB, which is 20% 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 52.1 kB or 84% of the original size.
Potential reduce by 778.9 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. Obviously, Progainer needs image optimization as it can save up to 778.9 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 191.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 191.6 kB or 72% of the original size.
Potential reduce by 30.7 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. Progainer.co.kr needs all CSS files to be minified and compressed as it can save up to 30.7 kB or 81% of the original size.
Number of requests can be reduced by 20 (18%)
109
89
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Progainer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
progainer.co.kr
1454 ms
common.css
1040 ms
wcslog.js
62 ms
jquery-1.7.2.min.js
1278 ms
flash.js
838 ms
rightbanner.js
641 ms
bookmark.js
439 ms
main.css
622 ms
mainimg.js
640 ms
rolling.js
822 ms
shopRbanner.html
688 ms
header.1.css
657 ms
sliding_header.js
849 ms
header.1.js
898 ms
footer.1.css
896 ms
footer.1.js
897 ms
main.js
1078 ms
detailpage.js
1082 ms
Log_script_logsid.html
1134 ms
cookie.js
1134 ms
index_03.gif
439 ms
index_04.gif
441 ms
index_05.gif
448 ms
index_06.gif
454 ms
index_07.gif
452 ms
index_09.gif
475 ms
index_10.gif
633 ms
main_14.png
635 ms
topboard_02.png
646 ms
topboard_03.png
651 ms
topboard_04.png
651 ms
topboard_06.png
680 ms
index_23.png
861 ms
cate_01.gif
864 ms
cate_top.png
868 ms
cate_img1.jpg
1346 ms
cate_02.gif
876 ms
cate_img2.jpg
1399 ms
cate_03.gif
1544 ms
cate_img3.jpg
1756 ms
cate_04.gif
1105 ms
cate_img4.jpg
1551 ms
cate_05.gif
1323 ms
cate_img5.jpg
1549 ms
cate_06.gif
1550 ms
cate_img6.jpg
1590 ms
cate_07.gif
1748 ms
cate_img7.jpg
1762 ms
mainimg1.jpg
3035 ms
mainimg2.jpg
2870 ms
mainimg3.jpg
2946 ms
mainimg4.jpg
4974 ms
scroll.css
1733 ms
mbtn_01_ov.png
1761 ms
mbtn_02.png
1930 ms
mbtn_03.png
1957 ms
mbtn_04.png
1976 ms
index_118.gif
2001 ms
0010000000012.jpg
3956 ms
0010000000142.jpg
2632 ms
0010000000152.jpg
2873 ms
0010000000672.jpg
2799 ms
0010000000172.jpg
2853 ms
0010000000182.jpg
4334 ms
0010000000652.jpg
2835 ms
0010000000752.jpg
3071 ms
index_89.gif
3026 ms
main_title_01.gif
3002 ms
0010000000732.jpg
3021 ms
0010000000722.jpg
3210 ms
0010000000712.jpg
3053 ms
main_title_02.gif
3203 ms
0010000000902.jpg
2997 ms
0010000000912.jpg
3121 ms
main_title_03.gif
2930 ms
0010000000862.jpg
2925 ms
0010000000872.jpg
2933 ms
0010000000892.jpg
2951 ms
0010000000882.jpg
4007 ms
index_140.gif
3090 ms
index_141.gif
3067 ms
index_142.gif
2948 ms
index_143.gif
3090 ms
index_146.gif
3090 ms
main_146.gif
2893 ms
main_148.gif
3000 ms
m
463 ms
[sr].gif
674 ms
mslog.js
934 ms
main_150.gif
2878 ms
index_155.gif
2890 ms
index_157.gif
2759 ms
index_159.gif
2823 ms
Conf_progainer.js
427 ms
index_161.gif
2377 ms
ms.log
222 ms
index_163.gif
2252 ms
main_174.gif
2285 ms
index_46.gif
2232 ms
[sr].gif
596 ms
emd_pt.js
596 ms
index_49.gif
2183 ms
index_50.gif
2153 ms
index_51.gif
2036 ms
index_52.gif
2077 ms
index_56.gif
1908 ms
top_pt6.gif
1972 ms
btn01.png
1956 ms
HTTP_s.js
805 ms
btn02.png
1833 ms
progainer.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
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
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.
progainer.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
progainer.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
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Progainer.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 Progainer.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.
progainer.co.kr
Open Graph description is not detected on the main page of Progainer. 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: