13.9 sec in total
865 ms
12.1 sec
848 ms
Visit simuline.com now to see the best up-to-date Simuline content for South Korea and also check out these interesting facts you probably never knew about simuline.com
Visit simuline.comWe analyzed Simuline.com page load time and found that the first response time was 865 ms and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
simuline.com performance score
865 ms
399 ms
596 ms
599 ms
402 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 97% of them (117 requests) were addressed to the original Simuline.com, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Themes.googleusercontent.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Simuline.com.
Page size can be reduced by 434.0 kB (14%)
3.1 MB
2.7 MB
In fact, the total size of Simuline.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.6 MB which makes up the majority of the site volume.
Potential reduce by 31.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 31.0 kB or 78% of the original size.
Potential reduce by 9.0 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. Simuline images are well optimized though.
Potential reduce by 357.4 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 357.4 kB or 77% of the original size.
Potential reduce by 36.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. Simuline.com needs all CSS files to be minified and compressed as it can save up to 36.6 kB or 85% of the original size.
Number of requests can be reduced by 34 (29%)
118
84
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Simuline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
simuline.com
865 ms
common.css
399 ms
style.css
596 ms
javascript.js
599 ms
publish.js
402 ms
common.js
401 ms
maintab.js
590 ms
jquery-1.8.3.min.js
1382 ms
plani.visual.js
795 ms
main.js
804 ms
common.js
1970 ms
jquery.colorbox.js
1185 ms
analytics.js
42 ms
banner2.jpg
391 ms
banner2_on.jpg
399 ms
banner1.jpg
397 ms
banner1_on.jpg
401 ms
banner3.jpg
404 ms
banner3_on.jpg
402 ms
logo.png
805 ms
menu01.png
798 ms
menu02.png
800 ms
menu03.png
798 ms
go.png
803 ms
stop.png
800 ms
on.png
1200 ms
off.png
1197 ms
visual01.jpg
1988 ms
visual02.jpg
2621 ms
visual03.jpg
2861 ms
visual04.jpg
2625 ms
visual05.jpg
2969 ms
visual06.jpg
3013 ms
visual07.jpg
3560 ms
wedo_img1.jpg
3420 ms
ttaba1_on.jpg
3017 ms
motion_base.jpg
3851 ms
ttaba2.jpg
3354 ms
controller.jpg
3998 ms
ttaba3.jpg
3406 ms
immersive_4d_effects.jpg
4574 ms
history_img1.jpg
4396 ms
tab01.jpg
3810 ms
tab02.jpg
3949 ms
tab03.jpg
4206 ms
banner1.jpg
4244 ms
banner1_on.jpg
4345 ms
banner2.jpg
4397 ms
banner2_on.jpg
4605 ms
collect
18 ms
3Cf9ylHiOcKOk4ynsFHbiw.woff
96 ms
OVZZzjcZ3Hkq2ojVcUtDjT8E0i7KZn-EPnyo3HZu7kw.woff
155 ms
location.php
4278 ms
banner3.jpg
4372 ms
banner3_on.jpg
4413 ms
banner4.jpg
4414 ms
banner4_on.jpg
4599 ms
banner5.jpg
4626 ms
banner5_on.jpg
4259 ms
banner6.jpg
4366 ms
banner6_on.jpg
4408 ms
banner25.jpg
4418 ms
banner25_on.jpg
4592 ms
banner7.jpg
4624 ms
banner7_on.jpg
4255 ms
banner8.jpg
4360 ms
banner8_on.jpg
3625 ms
banner9.jpg
2994 ms
banner9_on.jpg
3156 ms
banner10.jpg
2961 ms
banner10_on.jpg
2867 ms
banner11.jpg
2933 ms
banner11_on.jpg
2980 ms
banner12.jpg
2651 ms
banner12_on.jpg
2762 ms
banner13.png
2788 ms
banner13_on.png
2672 ms
banner14.jpg
2535 ms
banner14_on.jpg
2538 ms
banner19.jpg
2448 ms
banner19_on.jpg
2569 ms
banner20.jpg
2392 ms
banner20_on.jpg
2375 ms
banner15.jpg
2395 ms
banner15_on.jpg
2396 ms
banner16.jpg
2394 ms
banner16_on.jpg
2387 ms
banner17.jpg
2381 ms
jquery.royalslider.min.js
2783 ms
banner17_on.jpg
2389 ms
banner18.jpg
2393 ms
banner18_on.jpg
2402 ms
send.jpg
2374 ms
tab01_over.jpg
2381 ms
repeat.jpg
2496 ms
overlay.png
2437 ms
main_world_img1.jpg
1178 ms
korea.png
286 ms
china.png
397 ms
indonesia.png
398 ms
brazil.png
473 ms
kyrgyzstan.png
515 ms
malaysia.png
682 ms
newzealand.png
793 ms
russia.png
802 ms
singapore.png
875 ms
turkey.png
910 ms
usa.png
1076 ms
saudiarabia.png
1197 ms
thailand.png
1198 ms
southafrica.png
1268 ms
bahrain.png
1303 ms
azerbaijan.png
1470 ms
syria.png
1574 ms
iraq.png
1589 ms
india.png
1591 ms
sudan.png
1661 ms
canada.png
1696 ms
kenya.png
1871 ms
kuwait.png
1969 ms
guam.png
1983 ms
simuline.com SEO score
EN
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Simuline.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Korean language. Our system also found out that Simuline.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.
simuline.com
Open Graph description is not detected on the main page of Simuline. 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: