40.6 sec in total
6.3 sec
33.7 sec
600 ms
Click here to check amazing Lequ content for China. Otherwise, check out these important facts you probably never knew about lequ.com
乐趣H5游戏平台是目前中国最大的H5手机网页游戏平台,提供在线玩的H5手机小游戏,最火爆的微信小游戏,最好玩的手机小游戏排行榜,让您能结识到H5游戏玩家和H5小游戏里的朋友,无需下载,点击马上玩!
Visit lequ.comWe analyzed Lequ.com page load time and found that the first response time was 6.3 sec and then it took 34.3 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 18 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lequ.com performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value10.9 s
0/100
25%
Value8.1 s
21/100
10%
Value10 ms
100/100
30%
Value0.039
100/100
15%
Value7.5 s
48/100
10%
6324 ms
3665 ms
1436 ms
1431 ms
1220 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 70% of them (47 requests) were addressed to the original Lequ.com, 24% (16 requests) were made to Res.lequ.com and 3% (2 requests) were made to Count26.51yes.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Lequ.com.
Page size can be reduced by 787.3 kB (37%)
2.1 MB
1.3 MB
In fact, the total size of Lequ.com main page is 2.1 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. 40% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 60.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 60.4 kB or 82% of the original size.
Potential reduce by 538.3 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, Lequ needs image optimization as it can save up to 538.3 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 133.2 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 133.2 kB or 59% of the original size.
Potential reduce by 55.4 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. Lequ.com needs all CSS files to be minified and compressed as it can save up to 55.4 kB or 80% of the original size.
Number of requests can be reduced by 3 (6%)
47
44
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lequ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
lequ.com
6324 ms
www.lequ.com
3665 ms
common.css
1436 ms
index.css
1431 ms
click.aspx
1220 ms
stat.js
1070 ms
jquery1.9.js
265 ms
require.js
263 ms
noavatar_small.gif
1258 ms
ce9ce919c0b2e3add313fe9d6f6b32f7.jpg
432 ms
list_mhj.png
839 ms
list_ahzs.png
2787 ms
list_dwby.png
2794 ms
list_khbd.png
1763 ms
list_wly.png
5672 ms
list_mycs.png
4273 ms
list_mhjh.png
1270 ms
list_tqsg.png
2140 ms
list_zhtx.png
2682 ms
list_lswd.png
5958 ms
list_tssj.png
6367 ms
list_dsg.png
7215 ms
list_sxd.png
3978 ms
list_zlcq.png
5924 ms
index_ht_wly.jpg
19612 ms
index_ht_wly_over.jpg
19612 ms
index_ht_khbd.jpg
15093 ms
index_ht_khbd_over.jpg
11460 ms
game_dsg.jpg
10143 ms
game_dsg_s.jpg
9540 ms
game_dwby.jpg
13047 ms
game_dwby_s.jpg
13333 ms
game_mhj.jpg
16185 ms
game_mhj_s.jpg
16569 ms
game_tssj.jpg
16005 ms
game_tssj_s.jpg
18600 ms
game_mhjh.jpg
18593 ms
game_mhjh_s.jpg
19608 ms
game_mycs.jpg
19051 ms
game_mycs_s.jpg
19602 ms
game_tqsg.jpg
19602 ms
game_zlcq.jpg
19602 ms
game_wssb.jpg
19602 ms
game_djwy.jpg
19602 ms
game_ahzs.jpg
19602 ms
icon-index.jpg
147 ms
icon-top.png
127 ms
logo.png
130 ms
point.png
140 ms
login.png
129 ms
middot.jpg
139 ms
icon-index1.png
139 ms
icon-index.jpg
143 ms
kstd.png
139 ms
kf.jpg
145 ms
index_min.css
11 ms
game_sq.jpg
20211 ms
game_sxd.jpg
19780 ms
count1.gif
891 ms
game_zhtx.jpg
20348 ms
index.js
23 ms
game_lj.jpg
19857 ms
function_u8.js
20475 ms
game_ldqk.jpg
19933 ms
game_jjsg.jpg
19833 ms
game_astd.jpg
19826 ms
yxtj-title.png
19635 ms
lequ.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
lequ.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lequ.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lequ.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 Lequ.com main page’s claimed encoding is gbk. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
lequ.com
Open Graph description is not detected on the main page of Lequ. 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: