5.6 sec in total
596 ms
4.8 sec
216 ms
Click here to check amazing Plantynet content for South Korea. Otherwise, check out these important facts you probably never knew about plantynet.com
건강한 인터넷 세상과 새로운 문화공간 플랜티넷이 만들어 갑니다.
Visit plantynet.comWe analyzed Plantynet.com page load time and found that the first response time was 596 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
plantynet.com performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value13.2 s
0/100
25%
Value7.7 s
24/100
10%
Value20 ms
100/100
30%
Value0.019
100/100
15%
Value5.8 s
67/100
10%
596 ms
758 ms
942 ms
754 ms
371 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 77% of them (23 requests) were addressed to the original Plantynet.com, 17% (5 requests) were made to Cdn.jsdelivr.net and 3% (1 request) were made to Cdn.rawgit.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Plantynet.com.
Page size can be reduced by 228.5 kB (7%)
3.1 MB
2.9 MB
In fact, the total size of Plantynet.com main page is 3.1 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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 22.3 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 10.0 kB, which is 39% 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 22.3 kB or 88% of the original size.
Potential reduce by 11.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. Plantynet images are well optimized though.
Potential reduce by 140.8 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 140.8 kB or 71% of the original size.
Potential reduce by 53.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. Plantynet.com needs all CSS files to be minified and compressed as it can save up to 53.6 kB or 86% of the original size.
Number of requests can be reduced by 8 (35%)
23
15
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plantynet. 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 5 to 1 for CSS and as a result speed up the page load time.
plantynet.com
596 ms
main.asp
758 ms
main.css
942 ms
swiper.min.css
754 ms
logo1.png
371 ms
scroll.png
379 ms
logo2.png
395 ms
menu_btn.png
379 ms
close_M.png
565 ms
jquery-3.1.1.min.js
930 ms
jquery.cookie.js
376 ms
swiper.min.js
756 ms
main_ui.js
585 ms
common.js
561 ms
base.css
187 ms
nanumsquare.css
50 ms
css
38 ms
nanumsquare.css
16 ms
mainbg_3.jpg
2823 ms
mainbg_2.jpg
1702 ms
subbg_5.jpg
2705 ms
subline1.png
186 ms
view_btn2.png
326 ms
subbg_6.jpg
2634 ms
subline2.png
478 ms
view_btn3.png
490 ms
NanumSquareB.woff
9 ms
NanumSquareEB.woff
46 ms
NanumSquareR.woff
44 ms
NanumSquareL.woff
46 ms
plantynet.com accessibility score
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
plantynet.com 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
plantynet.com SEO score
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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plantynet.com 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 Plantynet.com 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.
plantynet.com
Open Graph data is detected on the main page of Plantynet. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: