3.1 sec in total
390 ms
2.6 sec
108 ms
Click here to check amazing 18 content. Otherwise, check out these important facts you probably never knew about 18.lc
腾讯云域名注册, 腾讯云旗下品牌。腾讯云域名注册是中国领先的域名注册服务提供商, 并提供云主机、网站建设等网络服务。
Visit 18.lcWe analyzed 18.lc page load time and found that the first response time was 390 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
18.lc performance score
390 ms
614 ms
263 ms
246 ms
295 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 76% of them (31 requests) were addressed to the original 18.lc, 12% (5 requests) were made to Translate.googleapis.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (953 ms) belongs to the original domain 18.lc.
Page size can be reduced by 330.7 kB (56%)
587.1 kB
256.4 kB
In fact, the total size of 18.lc main page is 587.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. 30% of websites need less resources to load. Javascripts take 454.0 kB which makes up the majority of the site volume.
Potential reduce by 15.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 4.4 kB, which is 22% 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 15.2 kB or 78% of the original size.
Potential reduce by 854 B
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. 18 images are well optimized though.
Potential reduce by 261.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 261.1 kB or 58% of the original size.
Potential reduce by 53.5 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. 18.lc needs all CSS files to be minified and compressed as it can save up to 53.5 kB or 80% of the original size.
Number of requests can be reduced by 31 (79%)
39
8
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 18. 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 from 4 to 1 for CSS and as a result speed up the page load time.
18.lc
390 ms
www.18.lc
614 ms
jquery-ui-1.8.4.custom.css
263 ms
style.css
246 ms
magnific-popup.css
295 ms
jquery-1.7.2.min.js
390 ms
jquery-ui-1.8.4.custom.min.js
495 ms
jquery.cookies.js
328 ms
jquery.equalheights.js
508 ms
jquery.json-2.2.js
520 ms
jquery.magnific-popup.js
552 ms
element.js
31 ms
arrow_right.gif
256 ms
ja.gif
299 ms
de.gif
266 ms
en.gif
299 ms
logo.gif
267 ms
door_in.png
332 ms
exclamation.png
516 ms
house.png
511 ms
star.png
518 ms
user_add.png
604 ms
bullet_go.png
590 ms
world.png
663 ms
translateelement.css
58 ms
main.js
83 ms
ga.js
17 ms
shadow_right.jpg
698 ms
tab_right.png
719 ms
tab_left.png
730 ms
transp.png
891 ms
title.png
809 ms
transp2.png
862 ms
button.png
953 ms
footer.png
949 ms
element_main.js
39 ms
__utm.gif
12 ms
translate_24dp.png
27 ms
l
50 ms
cleardot.gif
528 ms
te_ctrl3.gif
11 ms
18.lc SEO score
ZH
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 18.lc can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed German language. Our system also found out that 18.lc 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.
18.lc
Open Graph description is not detected on the main page of 18. 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: