13 sec in total
1.2 sec
11.6 sec
180 ms
Visit plani.co.kr now to see the best up-to-date Plani content for South Korea and also check out these interesting facts you probably never knew about plani.co.kr
PLANI, 정보를 쉽고 가치있게
Visit plani.co.krWe analyzed Plani.co.kr page load time and found that the first response time was 1.2 sec and then it took 11.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
plani.co.kr performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value18.2 s
0/100
25%
Value16.0 s
0/100
10%
Value190 ms
91/100
30%
Value0.049
99/100
15%
Value10.4 s
24/100
10%
1210 ms
484 ms
420 ms
439 ms
482 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 98% of them (120 requests) were addressed to the original Plani.co.kr, 2% (2 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Plani.co.kr.
Page size can be reduced by 1.3 MB (7%)
20.2 MB
18.9 MB
In fact, the total size of Plani.co.kr main page is 20.2 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. 80% 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 19.4 MB which makes up the majority of the site volume.
Potential reduce by 28.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 4.4 kB, which is 13% 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 28.2 kB or 81% of the original size.
Potential reduce by 704.8 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. Plani images are well optimized though.
Potential reduce by 437.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 437.7 kB or 73% of the original size.
Potential reduce by 150.4 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. Plani.co.kr needs all CSS files to be minified and compressed as it can save up to 150.4 kB or 88% of the original size.
Number of requests can be reduced by 15 (12%)
121
106
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plani. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
plani.co.kr
1210 ms
main.css
484 ms
gBtn.css
420 ms
jquery.jgrowl.css
439 ms
jquery.showbox.css
482 ms
prettyPhoto.css
803 ms
theme.css
823 ms
5ec74a0f126e7954675f1c200cd9d0d7_1438671627.js
2297 ms
a944617d8d33d4be74fcd4c5325e75ed_1431674581.js
1090 ms
common.new.js
720 ms
jquery.mCustomScrollbar.css
1198 ms
jquery.mCustomScrollbar.concat.min.js
1201 ms
masonry-docs.css
1068 ms
packery.pkgd.min.js
1367 ms
css
76 ms
nanummyeongjo.css
53 ms
general.css
860 ms
layout.css
831 ms
notokr-regular.woff
1245 ms
logo.png
212 ms
btn_facebook.gif
270 ms
btn_allMenu.gif
277 ms
main_visual_201602.jpg
1526 ms
ci.png
243 ms
bg_award.jpg
2091 ms
img_wa01.png
481 ms
img_wa02.png
534 ms
img_wa03.png
547 ms
img_text01.png
721 ms
img_text02.png
799 ms
icon01.png
820 ms
icon02.png
959 ms
icon03.png
1066 ms
icon04.png
1091 ms
icon05.png
1197 ms
icon06.png
1332 ms
icon07.png
1366 ms
opacoty_50.png
1352 ms
december_171_1.jpg
2875 ms
december_171_2.jpg
2667 ms
december_171_3.jpg
2076 ms
december_171_4.jpg
2458 ms
december_171_5.jpg
2172 ms
december_171_6.jpg
2801 ms
december_171_7.jpg
2295 ms
december_171_8.jpg
2607 ms
december_171_9.jpg
2505 ms
december_171_10.jpg
3827 ms
december_171_11.jpg
2715 ms
december_171_12.jpg
3261 ms
december_171_13.jpg
3199 ms
december_193_1.jpg
2927 ms
december_193_2.jpg
3283 ms
december_193_3.jpg
3592 ms
LKf8nhXsWg5ybwEGXk8UBQ.woff
65 ms
notokr-light.woff
2939 ms
notokr-bold.woff
3115 ms
december_193_4.jpg
3743 ms
december_193_5.jpg
3432 ms
december_193_6.jpg
3054 ms
december_193_7.jpg
3035 ms
december_193_8.jpg
3472 ms
december_193_9.jpg
3057 ms
december_193_10.jpg
3520 ms
december_193_11.jpg
3105 ms
december_193_12.jpg
3234 ms
december_193_13.jpg
3586 ms
december_247_1.jpg
3268 ms
december_247_2.jpg
3429 ms
december_247_3.jpg
3301 ms
december_247_4.jpg
3070 ms
december_247_5.jpg
3684 ms
december_247_6.jpg
3430 ms
december_247_7.jpg
3096 ms
december_247_8.jpg
2907 ms
december_247_9.jpg
3256 ms
december_247_10.jpg
2653 ms
december_247_11.jpg
2903 ms
december_247_12.jpg
2773 ms
december_294_1.jpg
2530 ms
december_294_2.jpg
2858 ms
december_294_3.jpg
2847 ms
december_294_4.jpg
2529 ms
december_294_5.jpg
2946 ms
december_294_6.jpg
2578 ms
december_294_7.jpg
2528 ms
december_294_8.jpg
2468 ms
december_294_9.jpg
2688 ms
december_139_1.jpg
2405 ms
december_139_2.jpg
2665 ms
december_139_3.jpg
2645 ms
december_139_4.jpg
2616 ms
december_139_5.jpg
2318 ms
december_247_13.jpg
2701 ms
december_247_14.jpg
2391 ms
december_247_15.jpg
2335 ms
december_171_14.jpg
2365 ms
december_171_15.jpg
2318 ms
december_171_16.jpg
2298 ms
december_171_17.jpg
2315 ms
december_171_18.jpg
2221 ms
december_171_19.jpg
2121 ms
december_171_20.jpg
2121 ms
december_171_21.jpg
2171 ms
december_171_22.jpg
2015 ms
txt_thanks.png
2008 ms
november_bg.jpg
2336 ms
img_november01.png
2028 ms
img_november02.png
1930 ms
img_november03.png
1901 ms
img_november04.png
1783 ms
img_november05.png
1812 ms
img_november06.png
1884 ms
october_img.jpg
2480 ms
october_txt.png
1701 ms
name_ba.gif
1737 ms
september.jpg
2601 ms
august_bg.jpg
1953 ms
june_visual.jpg
2104 ms
april_visual.jpg
2284 ms
bg.gif
1688 ms
page_nextPrev.png
1813 ms
loading2.png
1978 ms
plani.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.
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.
plani.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
plani.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plani.co.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 Plani.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.
plani.co.kr
Open Graph description is not detected on the main page of Plani. 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: