27.6 sec in total
646 ms
26.6 sec
401 ms
Click here to check amazing Kinglos content. Otherwise, check out these important facts you probably never knew about kinglos.com
Provide global customers electric violin, electric cello and electric double bass of new style and new function.
Visit kinglos.comWe analyzed Kinglos.com page load time and found that the first response time was 646 ms and then it took 27 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 were 7 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
kinglos.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value10.3 s
0/100
25%
Value11.1 s
6/100
10%
Value490 ms
59/100
30%
Value0.635
9/100
15%
Value10.0 s
27/100
10%
646 ms
1342 ms
597 ms
801 ms
605 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 94% of them (51 requests) were addressed to the original Kinglos.com, 4% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to At.alicdn.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain Kinglos.com.
Page size can be reduced by 114.4 kB (47%)
246.1 kB
131.6 kB
In fact, the total size of Kinglos.com main page is 246.1 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. 40% of websites need less resources to load. HTML takes 108.5 kB which makes up the majority of the site volume.
Potential reduce by 93.6 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 19.8 kB, which is 18% 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 93.6 kB or 86% of the original size.
Potential reduce by 2.2 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. Kinglos images are well optimized though.
Potential reduce by 18.1 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 18.1 kB or 19% of the original size.
Potential reduce by 616 B
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. Kinglos.com has all CSS files already compressed.
Number of requests can be reduced by 8 (19%)
42
34
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kinglos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
kinglos.com
646 ms
www.kinglos.com
1342 ms
index.min.css
597 ms
jquery-1.10.2.min.js
801 ms
sea.js
605 ms
swiper.min.js
824 ms
js
58 ms
kaka-1.0.0.js
1557 ms
all.min.js
608 ms
wow.min.js
1787 ms
traffic.js
1015 ms
swiper.min.css
1794 ms
font-awesome.css
1958 ms
gtm.js
77 ms
shanghai-kinglos-musical-instruments-co.-ltd.png
201 ms
violin-for-advanced-players.webp
782 ms
kinglos-string-instruments.webp
2187 ms
kinglos-string-instruments-1.webp
1211 ms
kinbglos-violin.webp
2299 ms
violin.webp
9781 ms
violin.webp
20324 ms
cell.webp
6481 ms
cello.webp
5235 ms
bass.webp
5668 ms
double-bass.webp
4067 ms
guitar.webp
7985 ms
kinglos-guitar.webp
16478 ms
ukulele.webp
7920 ms
ukulele.webp
11035 ms
piano.webp
13636 ms
piano_1642228154.webp
13456 ms
kinglos-other-music-instruments.webp
13209 ms
other-instruments.webp
13638 ms
ctds-electric-violin.webp
15011 ms
kinglos-bass.webp
14079 ms
kinglos-electric-violin.webp
17416 ms
electric-violin-dsza-series.webp
14254 ms
electric-violin-mwds-series.webp
14659 ms
electric-violin-sdds-series.webp
14851 ms
kinglos-sxds-ab-series-electric-violin.webp
15262 ms
ysds-series-acoustic-electric-violin.webp
15456 ms
dsdb-5001.jpg
18318 ms
kinglos-cello.webp
17950 ms
kinglos-string-instuments.webp
18033 ms
kinglos-instuments.webp
20318 ms
WORK%20SANS.TTF
18748 ms
fontawesome-webfont.woff
20257 ms
font_2752213_dqao7lx9mbq.woff
514 ms
PLAYFAIRDISPLAY-BOLD.TTF
20257 ms
back_1.png
20226 ms
back_2.jpg
20199 ms
misc.php
20125 ms
kinbglos-violin.webp
1305 ms
fontawesome-webfont.ttf
1835 ms
kinglos.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
Buttons do not have an accessible name
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
kinglos.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
kinglos.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kinglos.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Kinglos.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.
kinglos.com
Open Graph description is not detected on the main page of Kinglos. 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: