13.5 sec in total
1.4 sec
11.7 sec
375 ms
Click here to check amazing Invil content for South Korea. Otherwise, check out these important facts you probably never knew about invil.org
정보화마을
Visit invil.orgWe analyzed Invil.org page load time and found that the first response time was 1.4 sec and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
invil.org performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value9.2 s
1/100
25%
Value11.6 s
4/100
10%
Value50 ms
100/100
30%
Value0.327
35/100
15%
Value9.2 s
32/100
10%
1401 ms
400 ms
1003 ms
412 ms
408 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 89% of them (51 requests) were addressed to the original Invil.org, 5% (3 requests) were made to Vilman.invil.org and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (8.5 sec) belongs to the original domain Invil.org.
Page size can be reduced by 458.9 kB (52%)
879.4 kB
420.4 kB
In fact, the total size of Invil.org main page is 879.4 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. 25% of websites need less resources to load. Images take 393.2 kB which makes up the majority of the site volume.
Potential reduce by 55.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 10.0 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 55.2 kB or 81% of the original size.
Potential reduce by 85.4 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. Obviously, Invil needs image optimization as it can save up to 85.4 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 119.5 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 119.5 kB or 63% of the original size.
Potential reduce by 198.9 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. Invil.org needs all CSS files to be minified and compressed as it can save up to 198.9 kB or 88% of the original size.
Number of requests can be reduced by 19 (34%)
56
37
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Invil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
invil.org
1401 ms
base.css
400 ms
jquery-1.8.3.min.js
1003 ms
common.js
412 ms
slider_danvi.css
408 ms
js-image-slider.js
427 ms
slider_danvi.js
813 ms
invilcomm.js
840 ms
menu.js
1047 ms
common.css
638 ms
layout.css
869 ms
contents.css
1697 ms
event_201512090937305390
1426 ms
event_201602290910522060
2849 ms
event_201601180220491170
4549 ms
logo.gif
414 ms
icon_menu.gif
414 ms
logo.png
632 ms
btn_sld_prev.png
424 ms
btn_sld_stop.png
428 ms
btn_sld_play.png
430 ms
btn_sld_next.png
809 ms
newsArtcl_201602230526053880
2500 ms
newsArtcl_201602210242376990
2439 ms
newsArtcl_201602230226110460
2561 ms
newsArtcl_201602231144142210
2466 ms
todayVill_201503021144443190
3787 ms
disp_201602170355594650
3642 ms
disp_201602170426023300
3038 ms
disp_201602170427542700
3296 ms
disp_201602170428458250
3348 ms
disp_201602170428088010
3641 ms
disp_201601191128225530
3662 ms
disp_201601191139190400
4141 ms
disp_201601191135114450
4616 ms
disp_201601191135520110
4441 ms
disp_201601191136313010
4498 ms
img_bn01.gif
4085 ms
KLID_LogoType06.gif
4210 ms
img_bn02.gif
4525 ms
img_bn03.gif
4552 ms
logo_footer.gif
4635 ms
img_web_accessibility_cert_mark.png
5042 ms
analytics.js
29 ms
bg_tmenu_bar.gif
4918 ms
icon.png
5342 ms
bg_all_menu.png
4943 ms
collect
35 ms
sld_num_bg.png
4974 ms
icon_main_link.gif
5002 ms
bg_cont02.jpg
8531 ms
icon_main.png
5301 ms
acecounter_V70.js;jsessionid=HobndiZDGnYlLWNj5H6MPpyK.www
5569 ms
weblog.invil.org
436 ms
bg_footer.gif
205 ms
bg_foot_bar.gif
404 ms
bullet.png
429 ms
invil.org 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
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.
invil.org 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
invil.org 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
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 Invil.org 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 Invil.org 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.
invil.org
Open Graph description is not detected on the main page of Invil. 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: