52.1 sec in total
1.3 sec
49.9 sec
841 ms
Visit lmqy.net now to see the best up-to-date Lmqy content and also check out these interesting facts you probably never knew about lmqy.net
浪漫情缘故事网-04-19年记录
Visit lmqy.netWe analyzed Lmqy.net page load time and found that the first response time was 1.3 sec and then it took 50.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lmqy.net performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value3.3 s
69/100
25%
Value9.6 s
11/100
10%
Value40 ms
100/100
30%
Value0.405
25/100
15%
Value3.0 s
96/100
10%
1335 ms
3898 ms
866 ms
20095 ms
8059 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 59% of them (27 requests) were addressed to the original Lmqy.net, 17% (8 requests) were made to Cpro.baidustatic.com and 7% (3 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Lmqy.net.
Page size can be reduced by 346.5 kB (63%)
548.3 kB
201.8 kB
In fact, the total size of Lmqy.net main page is 548.3 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 361.3 kB which makes up the majority of the site volume.
Potential reduce by 45.4 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 45.4 kB or 79% of the original size.
Potential reduce by 5.8 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. Lmqy images are well optimized though.
Potential reduce by 239.3 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 239.3 kB or 66% of the original size.
Potential reduce by 56.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. Lmqy.net needs all CSS files to be minified and compressed as it can save up to 56.0 kB or 85% of the original size.
Number of requests can be reduced by 21 (50%)
42
21
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lmqy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
lmqy.net
1335 ms
www.lmqy.net
3898 ms
wp-emoji-release.min.js
866 ms
genericons.css
20095 ms
style.css
8059 ms
jquery.js
2049 ms
jquery-migrate.min.js
1307 ms
c.js
1069 ms
core-min.js
1291 ms
shCore-min.css
1039 ms
shThemeDefault-min.css
1155 ms
masonry.min.js
1511 ms
jquery.masonry.min.js
1663 ms
functions.js
1537 ms
wp-embed.min.js
1703 ms
circle.png
2299 ms
search-icon.png
521 ms
addReduce.png
709 ms
alert.png
630 ms
drag.png
2829 ms
fixedMenu.png
932 ms
dropdown.png
2965 ms
slider.png
1244 ms
city.png
1267 ms
zoom.png
1382 ms
zoom.gif
19933 ms
icrm
816 ms
shBrushXml-min.js
1611 ms
shBrushJScript-min.js
1604 ms
hm.js
7248 ms
icrm
2355 ms
cpro.js
832 ms
adx.php
786 ms
icon_12px.png
578 ms
reduce_bd-logo1_oper.png
545 ms
closefeedback.min.js
506 ms
reduce_promotion_oper.png
539 ms
bd_logo.png
538 ms
bg_rb.png
545 ms
hm.gif
378 ms
o.htm
805 ms
hm.gif
4925 ms
wh.js
764 ms
ac.js
539 ms
fp.htm
900 ms
fp.htm
2242 ms
lmqy.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
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.
lmqy.net 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
Browser errors were logged to the console
lmqy.net SEO score
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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lmqy.net 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 Chinese language. Our system also found out that Lmqy.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.
lmqy.net
Open Graph description is not detected on the main page of Lmqy. 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: