13.6 sec in total
1.5 sec
11.4 sec
675 ms
Click here to check amazing Bigissue 2 content for South Korea. Otherwise, check out these important facts you probably never knew about bigissue2.kr
홈리스의 자립을 돕는 빅이슈코리아의 온라인 몰입니다.
Visit bigissue2.krWe analyzed Bigissue2.kr page load time and found that the first response time was 1.5 sec and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
bigissue2.kr performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value57.4 s
0/100
25%
Value15.8 s
0/100
10%
Value1,490 ms
14/100
30%
Value1.017
2/100
15%
Value13.9 s
10/100
10%
1519 ms
66 ms
552 ms
562 ms
563 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 39% of them (36 requests) were addressed to the original Bigissue2.kr, 33% (30 requests) were made to Cdn-pro-web-228-145.cdn-nhncommerce.com and 12% (11 requests) were made to Rlix6mlbu.toastcdn.net. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Cdn-pro-web-228-145.cdn-nhncommerce.com.
Page size can be reduced by 868.6 kB (10%)
8.7 MB
7.8 MB
In fact, the total size of Bigissue2.kr main page is 8.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 8.4 MB which makes up the majority of the site volume.
Potential reduce by 67.7 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 19.2 kB, which is 24% 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 67.7 kB or 86% of the original size.
Potential reduce by 766.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. Bigissue 2 images are well optimized though.
Potential reduce by 25.9 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 25.9 kB or 19% of the original size.
Potential reduce by 8.0 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. Bigissue2.kr needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 14% of the original size.
Number of requests can be reduced by 43 (51%)
84
41
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bigissue 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.bigissue2.kr
1519 ms
js
66 ms
reset.css
552 ms
common.css
562 ms
layer.css
563 ms
layout.css
557 ms
animate.css
567 ms
list.css
554 ms
button.css
1096 ms
main.css
1096 ms
chosen.css
1100 ms
custom.css
1104 ms
all.css
50 ms
gd_gettext.js
1106 ms
jquery.min.js
1305 ms
underscore-min.js
1645 ms
jquery.validate.min.js
1648 ms
additional-methods.min.js
1652 ms
numeral.min.js
1654 ms
accounting.min.js
1655 ms
money.min.js
1841 ms
chosen.jquery.min.js
2194 ms
placeholders.jquery.min.js
2197 ms
clipboard.min.js
2204 ms
jquery.vticker.js
2206 ms
gd_ui.js
2209 ms
ml_ui.js
2390 ms
gd_common.js
2742 ms
gd_visit.js
2740 ms
jquery.cookie.js
2746 ms
gd_popup.js
2761 ms
gd_cookie.js
2759 ms
wcslog.js
89 ms
naverCommonInflowScript.js
2917 ms
js
50 ms
js
77 ms
slick.js
3300 ms
gmogs_image_125-50_en_dblue.js
73 ms
css
81 ms
fbevents.js
78 ms
layer-close.png
2980 ms
449_add3_014.png
156 ms
gs_noscript_125-50_en.gif
96 ms
374_add3_051.jpg
504 ms
314_add3_017.jpg
171 ms
448_add4_088.jpg
156 ms
449_add4_09.png
221 ms
447_add4_042.jpg
243 ms
446_add4_024.jpg
209 ms
443_add4_048.jpg
2767 ms
400_add4_045.jpg
2766 ms
instagram-brands.png
2965 ms
facebook-square-brands.png
3000 ms
mypage_btn_open.png
3001 ms
09b73aa35fadd195257a19a3e5e98afb_19108.png
2981 ms
fabd1db34765e4da701822b247229bdc_24242.png
2968 ms
b58562a24251eb8f7688d9b7354af3d3_52042.jpg
3924 ms
5922c08209201005fdada5b5a30ba69d_38225.png
4319 ms
b504e114513f7dd6ee4ab2344be8dae4_39017.png
4159 ms
good_icon_special.gif
3197 ms
good_icon_recomm.gif
3198 ms
good_icon_new.gif
3226 ms
goods_icon_order.gif
3411 ms
good_icon_popular.gif
3395 ms
scroll-banner-right01.jpg
3452 ms
quick_btn_open.png
3590 ms
quick_btn_cart.png
3625 ms
quick_btn_delivery.png
3677 ms
758ad5d899b78ca5e7b28a57cfe3293d_62243.png
3786 ms
quick_btn_today.png
3840 ms
search.png
3902 ms
quick_btn_up.png
3983 ms
quick_btn_down.png
4055 ms
btn_scroll_prev.png
4127 ms
btn_scroll_next.png
4118 ms
ico_cart_menu01.jpg
4179 ms
ico_cart_menu02.jpg
4276 ms
ico_cart_menu03.jpg
4314 ms
btn_cart_open.png
4356 ms
btn_cart_close.png
4363 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
53 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLPg9A.ttf
64 ms
fa-solid-900.woff
41 ms
fa-regular-400.woff
40 ms
siteSeal.do
2928 ms
bg_cart_bar.png
341 ms
popup_ps.php
396 ms
e1bd642280c16888bfd5b02526b78a7a.png
1961 ms
0c222648fd2170726c27bf293f5be273.png
50 ms
layer-close.png
550 ms
check_off_small.png
557 ms
siteSealImage.do
2673 ms
bigissue2.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Form elements do not have associated labels
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.
bigissue2.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
Page has valid source maps
bigissue2.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bigissue2.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 Bigissue2.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.
bigissue2.kr
Open Graph data is detected on the main page of Bigissue 2. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: