7.8 sec in total
756 ms
6.8 sec
176 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 756 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
bigissue2.kr performance score
name
value
score
weighting
Value14.3 s
0/100
10%
Value56.3 s
0/100
25%
Value47.1 s
0/100
10%
Value870 ms
33/100
30%
Value0.27
45/100
15%
Value37.9 s
0/100
10%
756 ms
1020 ms
672 ms
474 ms
522 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that all of those requests were addressed to Bigissue2.kr and no external sources were called. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Bigissue2.kr.
Page size can be reduced by 132.5 kB (19%)
707.5 kB
575.1 kB
In fact, the total size of Bigissue2.kr main page is 707.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 600.8 kB which makes up the majority of the site volume.
Potential reduce by 15.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 15.0 kB or 80% of the original size.
Potential reduce by 48.5 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 61.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 61.9 kB or 78% of the original size.
Potential reduce by 7.1 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 7.1 kB or 80% of the original size.
Number of requests can be reduced by 17 (43%)
40
23
The browser has sent 40 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 and as a result speed up the page load time.
index.php
756 ms
common.js
1020 ms
godo.cart_tab.js
672 ms
style.css
474 ms
style.css
522 ms
style_horizontal.css
225 ms
close.gif
393 ms
btn_mypage_go.gif
400 ms
logo.jpg
804 ms
topmenu_login.gif
455 ms
topmenu_join.gif
460 ms
topmenu_cart.gif
680 ms
topmenu_order.gif
792 ms
topmenu_wishlist.gif
853 ms
topmenu_cs.gif
908 ms
topmenu_my.gif
917 ms
topmenu_today.gif
1131 ms
topmenu_community.gif
1194 ms
default_outbg.gif
1022 ms
main.jpg
2995 ms
1457915773290i0.jpg
1378 ms
good_icon_new.gif
1198 ms
1456709308389i0.jpg
1585 ms
1455503529192i0.jpg
1579 ms
1454033391405i0.jpg
1697 ms
1452748357649i0.jpg
1987 ms
good_icon_soldout.gif
1771 ms
1451357260966i0.jpg
2279 ms
1450071109399i0.jpg
2344 ms
1448848523396i0.jpg
2306 ms
1447471407238i0.jpg
2545 ms
1446208220792i0.jpg
2375 ms
bottom_bu_company.gif
2770 ms
bottom_bu_private.gif
2804 ms
bottom_bu_agreed.gif
2749 ms
bottom_bu_center.gif
2897 ms
bottom_bu_guide.gif
2999 ms
bottom_bu_idpw.gif
3153 ms
foo.gif
3666 ms
btn_c_view.gif
3197 ms
footer_godomall.png
3296 ms
icon_soldout
3439 ms
blank.php
3346 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.
[aria-*] attributes do not have valid values
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
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
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 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 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.
bigissue2.kr
Open Graph description is not detected on the main page of Bigissue 2. 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: