11.4 sec in total
2.4 sec
8.5 sec
520 ms
Welcome to livingnart.or.kr homepage info - get ready to check Livingnart best content right away, or after learning these important things about livingnart.or.kr
일상예술창작센터의 공식 홈페이지 입니다.
Visit livingnart.or.krWe analyzed Livingnart.or.kr page load time and found that the first response time was 2.4 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
livingnart.or.kr performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value12.5 s
0/100
25%
Value8.7 s
16/100
10%
Value610 ms
49/100
30%
Value0.002
100/100
15%
Value15.6 s
6/100
10%
2387 ms
370 ms
581 ms
394 ms
395 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 77% of them (67 requests) were addressed to the original Livingnart.or.kr, 11% (10 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Livingnart.or.kr.
Page size can be reduced by 2.2 MB (32%)
6.7 MB
4.5 MB
In fact, the total size of Livingnart.or.kr main page is 6.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 107.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 19.5 kB, which is 15% 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 107.2 kB or 83% of the original size.
Potential reduce by 181.7 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. Livingnart images are well optimized though.
Potential reduce by 940.7 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 940.7 kB or 71% of the original size.
Potential reduce by 937.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. Livingnart.or.kr needs all CSS files to be minified and compressed as it can save up to 937.6 kB or 85% of the original size.
Number of requests can be reduced by 53 (72%)
74
21
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Livingnart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
www.livingnart.or.kr
2387 ms
wp-emoji-release.min.js
370 ms
js_composer.css
581 ms
styles.css
394 ms
buttons.min.css
395 ms
dashicons.min.css
602 ms
mediaelementplayer.min.css
403 ms
wp-mediaelement.css
562 ms
media-views.min.css
599 ms
imgareaselect.css
602 ms
settings.css
605 ms
font-awesome.min.css
756 ms
style.css
776 ms
wpex-visual-composer.css
784 ms
wpex-visual-composer-extend.css
786 ms
skin.css
785 ms
nanumgothic.css
39 ms
responsive.css
806 ms
style.css
947 ms
font-awesome.min.css
969 ms
style.css
976 ms
jquery.js
1172 ms
jquery-migrate.min.js
990 ms
utils.min.js
1002 ms
plupload.full.min.js
1331 ms
js
81 ms
jquery.themepunch.tools.min.js
1167 ms
jquery.themepunch.revolution.min.js
1378 ms
css
68 ms
jquery.form.min.js
1031 ms
scripts.js
1040 ms
underscore.min.js
1213 ms
shortcode.min.js
1244 ms
backbone.min.js
1316 ms
wp-util.min.js
1317 ms
wp-backbone.min.js
1396 ms
media-models.min.js
1466 ms
wp-plupload.min.js
1464 ms
core.min.js
1470 ms
widget.min.js
1474 ms
mouse.min.js
1284 ms
sortable.min.js
1374 ms
mediaelement-and-player.min.js
1519 ms
wp-mediaelement.js
1516 ms
media-views.min.js
1359 ms
media-editor.min.js
1326 ms
media-audiovideo.min.js
1321 ms
comment-reply.min.js
1345 ms
total-min.js
1624 ms
js_composer_front.js
1650 ms
waypoints.min.js
1291 ms
logo-main2.png
649 ms
vDdabZWWExM
230 ms
%EC%9B%B9_03xx15.png
2578 ms
%ED%94%84%EB%A6%AC%EB%A7%88%EC%BC%93.png
1039 ms
%EC%B1%84%EC%9A%A9%EA%B3%B5%EA%B3%A00216.png
730 ms
%EC%84%9C%EC%9A%B8-%ED%81%AC%EB%A6%AC%EC%8A%A4%EB%A7%88%EC%8A%A4-%EB%A7%88%EC%BC%93_1223.png
983 ms
%ED%94%84%EB%A6%AC%EB%A7%88%EC%BC%93_%EB%82%B4%EB%85%84%EC%97%90-%EB%8B%A4%EC%8B%9C%EB%A7%8C%EB%82%98%EC%9A%94.png
983 ms
%ED%82%A4%EC%97%B0%EB%A7%90%EC%86%8C%EA%B0%9C_11281.png
1201 ms
%EB%A7%88%EC%9D%84%EC%A7%80%EB%8F%84-3-1.jpg
2185 ms
%EB%94%B0%EB%82%A8_%EA%B0%80%EC%9D%84%EC%9E%A5-1.jpg
1222 ms
%ED%99%9C%EB%8F%99%EA%B0%80-%EB%AA%A8%EC%A7%91.jpg
1501 ms
logo-freemarket.png
1240 ms
%EB%AA%85%EB%9E%91%EC%8B%9C%EC%9E%A5.png
1394 ms
logo-skk.png
1417 ms
logo-ynmarket.png
1440 ms
%ED%8E%98%EC%96%B4.png
1588 ms
logo-key.png
1612 ms
facebook.png
1639 ms
twitter.png
1693 ms
uYKcPVoh6c5R0NpdEY5A-Q.woff
27 ms
DXI1ORHCpsQm3Vp6mXoaTRsxEYwM7FgeyaSgU71cLG0.woff
70 ms
MTP_ySUJH_bn48VBG8sNShsxEYwM7FgeyaSgU71cLG0.woff
150 ms
k3k702ZOKiLJc3WVjuplzBsxEYwM7FgeyaSgU71cLG0.woff
166 ms
EInbV5DfGHOiMmvb1Xr-hhsxEYwM7FgeyaSgU71cLG0.woff
168 ms
fontawesome-webfont.woff
1695 ms
fontawesome-webfont.woff
1721 ms
NanumGothic-Regular.woff
164 ms
NanumGothic-Bold.woff
201 ms
NanumGothic-ExtraBold.woff
226 ms
www-embed-player-vflfNyN_r.css
96 ms
www-embed-player.js
137 ms
base.js
200 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
39 ms
ad_status.js
44 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
23 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
livingnart.or.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.
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 IDs are not unique
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
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.
livingnart.or.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
livingnart.or.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Livingnart.or.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Livingnart.or.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.
livingnart.or.kr
Open Graph description is not detected on the main page of Livingnart. 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: