26.8 sec in total
1.6 sec
24.1 sec
1.1 sec
Click here to check amazing Kingworldtoys content. Otherwise, check out these important facts you probably never knew about kingworldtoys.com
-
Visit kingworldtoys.comWe analyzed Kingworldtoys.com page load time and found that the first response time was 1.6 sec and then it took 25.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
kingworldtoys.com performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value1.8 s
98/100
25%
Value2.6 s
97/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.1 s
100/100
10%
1641 ms
1188 ms
559 ms
887 ms
885 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Kingworldtoys.com, 39% (32 requests) were made to 15399552.s21i.faiusr.com and 29% (24 requests) were made to 2.ss.faisys.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source 15399552.s21i.faiusr.com.
Page size can be reduced by 2.4 MB (67%)
3.6 MB
1.2 MB
In fact, the total size of Kingworldtoys.com main page is 3.6 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. 70% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 127.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. 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 127.3 kB or 84% of the original size.
Potential reduce by 2.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. Kingworldtoys images are well optimized though.
Potential reduce by 1.6 MB
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 1.6 MB or 71% of the original size.
Potential reduce by 747.0 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. Kingworldtoys.com needs all CSS files to be minified and compressed as it can save up to 747.0 kB or 85% of the original size.
Number of requests can be reduced by 35 (44%)
80
45
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kingworldtoys. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
kingworldtoys.com
1641 ms
outerChain.jsp
1188 ms
browserCheck.min.js
559 ms
dialog.min.css
887 ms
siteBase.min.css
885 ms
base.min.css
948 ms
module.min.css
884 ms
20006.min.css
886 ms
moduleAnimationForNoSpider.min.css
878 ms
navStyle1.min.css
926 ms
tabStyle5.min.css
945 ms
newSearchBoxStyle.min.css
927 ms
floatBtn1.min.css
947 ms
poshytipAndmCustomScrollbar.min.css
960 ms
jzcusstyle.jsp
541 ms
comMethods.min.js
822 ms
jzUtils.min.js
830 ms
polyfill.min.js
854 ms
jquery-core.min.js
854 ms
jquery-mousewheel.min.js
828 ms
frontend.min.js
831 ms
jquery-ui-core.min.js
957 ms
jquery-parallax.min.js
911 ms
monitor.min.js
914 ms
site.min.js
1151 ms
1033.min.js
958 ms
site.min.js
958 ms
fontsIco.min.css
952 ms
hawkEye.min.js
566 ms
national_en.png
164 ms
dot.gif
836 ms
ABUIABAEGAAgjfiX0gUoj7WhpwYwgA84ugU.png
2848 ms
ABUIABAEGAAguu6s0gUogLbEnQYwrgM44AI!400x400.png
1267 ms
ABUIABAEGAAgvO6s0gUogJPxkwYwrgM44AI!400x400.png
1010 ms
ABUIABAEGAAgve6s0gUooIGWugYwrgM44AI!400x400.png
1747 ms
ABUIABACGAAg4Nus0gUo3MmSmwIwgA84_gM.jpg
1447 ms
ABUIABACGAAg_Nus0gUomJjLhQYwgA84wAc.jpg
1574 ms
ABUIABAEGAAglMqd0gUosLqMyAYwrgM44AI.png
1297 ms
ABUIABAEGAAglsqd0gUo-Obw3wUwrgM44AI.png
1911 ms
ABUIABAEGAAgmMqd0gUoyvys5gQwrgM44AI.png
1456 ms
ABUIABAEGAAghsud0gUoj56nrQIwrgM44AI.png
2721 ms
ABUIABAEGAAgiMud0gUouuGC-wIwrgM44AI.png
2247 ms
ABUIABAEGAAgisud0gUoqYaj0wUwrgM44AI.png
2129 ms
ABUIABAEGAAg0sud0gUozLTdxgQwrgM44AI.png
2273 ms
ABUIABAEGAAgjs2d0gUo6sb-xAQwrgM44AI.png
6269 ms
ABUIABAEGAAgkM2d0gUouLieqwcwrgM44AI.png
2572 ms
ABUIABAEGAAgks2d0gUowcOW-QIwrgM44AI.png
3580 ms
ABUIABAEGAAgkM6d0gUomID96AUwrgM44AI.png
2913 ms
ABUIABAEGAAgks6d0gUoub_yVzCuAzjgAg.png
2766 ms
ABUIABAEGAAglM6d0gUou-3KqAcwrgM44AI.png
3884 ms
ABUIABAEGAAgs8_d0gUohemWsQEwrgM44AI.png
6879 ms
ABUIABAEGAAgtc_d0gUokPXQogIwrgM44AI.png
2923 ms
ABUIABAEGAAgts_d0gUo9rOx8wEwrgM44AI.png
20299 ms
ABUIABACGAAgpPms0gUo5brEgQcwgA847Ak.jpg
4422 ms
ABUIABACGAAgj7rT0QUovsHC0wIwrgM44AI!400x400.jpg
4061 ms
ABUIABACGAAgsLrT0QUogqKhVDCuAzjgAg!400x400.jpg
4525 ms
ABUIABACGAAgv7rT0QUoiZnJxAMwrgM44AI!400x400.jpg
4582 ms
ABUIABACGAAgz7rT0QUoosDn6AcwrgM44AI!400x400.jpg
5937 ms
locater_Arrow3.png
412 ms
national_cn.png
411 ms
navleft.gif
407 ms
navright.gif
413 ms
sound_0_on.gif
412 ms
video-js.min.css
361 ms
video.min.css
358 ms
datepicker.min.css
359 ms
ajaxLoadModuleDom_h.jsp
835 ms
mail_h.jsp
321 ms
bannerAnimation.min.css
97 ms
ABUIABAEGAAg5sqT0gUo0P_NfDCADzi6BQ.png
4700 ms
ABUIABAEGAAgt_Ws0gUo0IjWDTCfCzj6Aw!1500x1500.png
4705 ms
ABUIABAEGAAgu_as0gUo_NbdQDCfCzj6Aw!1500x1500.png
7636 ms
left.png
121 ms
right.png
122 ms
video.min.js
124 ms
bookingSubmitPanel.min.js
115 ms
photoSlide.min.js
114 ms
imageEffect.min.js
114 ms
svg.min.js
115 ms
ABUIABACGAAg_9yX0gUogJPcxgUwrAI4Wg.jpg
6058 ms
ABUIABAEGAAgqYX60AUo4IzNzAMwzgE4OA.png
5763 ms
transpace.png
62 ms
kingworldtoys.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
kingworldtoys.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
kingworldtoys.com SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kingworldtoys.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Kingworldtoys.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.
kingworldtoys.com
Open Graph description is not detected on the main page of Kingworldtoys. 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: