50.3 sec in total
9.5 sec
40.3 sec
433 ms
Visit lentor.net now to see the best up-to-date Lentor content for China and also check out these interesting facts you probably never knew about lentor.net
网页描述
Visit lentor.netWe analyzed Lentor.net page load time and found that the first response time was 9.5 sec and then it took 40.7 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 20 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lentor.net performance score
name
value
score
weighting
Value1.6 s
93/100
10%
Value4.3 s
41/100
25%
Value2.9 s
95/100
10%
Value30 ms
100/100
30%
Value0.011
100/100
15%
Value1.9 s
100/100
10%
9547 ms
1026 ms
3350 ms
15826 ms
1219 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 60% of them (27 requests) were addressed to the original Lentor.net, 18% (8 requests) were made to Platform.lentor.net and 18% (8 requests) were made to Qr.liantu.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Platform.lentor.net.
Page size can be reduced by 207.3 kB (52%)
398.7 kB
191.5 kB
In fact, the total size of Lentor.net main page is 398.7 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. 15% of websites need less resources to load. Images take 161.0 kB which makes up the majority of the site volume.
Potential reduce by 27.5 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.0 kB, which is 12% 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 27.5 kB or 85% of the original size.
Potential reduce by 45.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. Obviously, Lentor needs image optimization as it can save up to 45.2 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 91.9 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 91.9 kB or 60% of the original size.
Potential reduce by 42.8 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. Lentor.net needs all CSS files to be minified and compressed as it can save up to 42.8 kB or 83% of the original size.
Number of requests can be reduced by 7 (29%)
24
17
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lentor. 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 as a result speed up the page load time.
lentor.net
9547 ms
global.css
1026 ms
layout.css
3350 ms
jquery.min.js
15826 ms
jquery.easing.js
1219 ms
slides.min.jquery.js
1553 ms
global.js
3478 ms
jquery.localScroll.min.js
1566 ms
jquery.scrollTo.min.js
2165 ms
mousewheel.js
2648 ms
analytics.js
118 ms
20140731162356012.jpg
8788 ms
api.php
724 ms
api.php
1764 ms
api.php
1177 ms
api.php
1084 ms
api.php
1171 ms
api.php
1176 ms
api.php
1285 ms
api.php
1867 ms
20140731100337179.jpg
3760 ms
20140731100333178.jpg
19779 ms
20140731100309792.jpg
16727 ms
20140731100300451.jpg
19779 ms
20140731100343990.jpg
8372 ms
20140731100328003.jpg
19778 ms
20140731100321916.jpg
19778 ms
logo.jpg
19778 ms
nav_li_bg.png
14172 ms
banner4.jpg
19777 ms
banner3.jpg
19778 ms
banner2.jpg
19773 ms
banner1.jpg
19772 ms
ind_wei_tb1.jpg
19773 ms
ind_wei_tb2.jpg
19772 ms
ind_wei_tb4.jpg
19772 ms
ind_wei_tb3.jpg
19773 ms
ind_box_bg.jpg
19773 ms
ind_an_h2.png
19773 ms
int_an_appBg.png
19773 ms
int_an_ddBg.png
19774 ms
ind_an_xapp.png
19774 ms
num_bj2.png
19773 ms
num_bj1.png
19774 ms
collect
56 ms
lentor.net 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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
lentor.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
lentor.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lentor.net 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 Lentor.net 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.
lentor.net
Open Graph description is not detected on the main page of Lentor. 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: