55.7 sec in total
1.4 sec
53.7 sec
523 ms
Visit leiue.com now to see the best up-to-date Leiue content for Taiwan and also check out these interesting facts you probably never knew about leiue.com
垒阅网(LEIUE.COM)是一个互联网泛科技网络媒体,专注于互联网消费动态及行业发展趋势,为互联网创业者和企业提供有价值的商业讯息。泪雪旗下站点。
Visit leiue.comWe analyzed Leiue.com page load time and found that the first response time was 1.4 sec and then it took 54.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 32 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
leiue.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value5.1 s
26/100
25%
Value10.3 s
8/100
10%
Value1,430 ms
15/100
30%
Value0
100/100
15%
Value12.5 s
14/100
10%
1440 ms
17892 ms
886 ms
913 ms
11891 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 57% of them (60 requests) were addressed to the original Leiue.com, 5% (5 requests) were made to Pagead2.googlesyndication.com and 4% (4 requests) were made to Static.js.weather.com.cn. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Leiue.com.
Page size can be reduced by 227.9 kB (56%)
406.9 kB
179.0 kB
In fact, the total size of Leiue.com main page is 406.9 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. Javascripts take 263.1 kB which makes up the majority of the site volume.
Potential reduce by 59.3 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 59.3 kB or 75% of the original size.
Potential reduce by 18.6 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, Leiue needs image optimization as it can save up to 18.6 kB or 49% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 129.4 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 129.4 kB or 49% of the original size.
Potential reduce by 20.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. Leiue.com needs all CSS files to be minified and compressed as it can save up to 20.5 kB or 77% of the original size.
Number of requests can be reduced by 42 (61%)
69
27
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leiue. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
leiue.com
1440 ms
www.leiue.com
17892 ms
global.css
886 ms
index.css
913 ms
jquery.js
11891 ms
leiue.js
2952 ms
loginjs.php
1411 ms
89530.js
3554 ms
adx9.js
3125 ms
adx1.js
3450 ms
adx2.js
2099 ms
adx10.js
4389 ms
inlay.js
852 ms
getJScode.asp
3984 ms
stat.php
1081 ms
ghs.png
12045 ms
favicon.png
2133 ms
83a09eda204ca85261b76e9938b1b49b.jpg
20405 ms
91af391ca853f628facab213f289942b.jpg
9218 ms
9dbbc55f3df0137402def8bec0e151d1.jpg
18014 ms
248babdc83ac72fc1be316cae4a209c3.jpg
12769 ms
92194b4396aa1069b4ab3561063cdeb2.jpg
3719 ms
65bcd8ecafbf6580c98fb59515b4f96c.jpg
20405 ms
67a116b3f93804c2cb0d7ba28ed07c4c.jpg
6931 ms
3c70e34da9f236954190a23e79b98657.png
20407 ms
c663a86408f9b2f3f61b314bd76f9d89.jpg
20407 ms
02a2af0ffc0e3367493bf3700b2d0fa6.jpg
20408 ms
416fd8a6d201089c5ca725748d992e6c.png
20409 ms
7d2b6d47558a8c95459ca17ce817ee35.jpg
20411 ms
c74a4c3c1087a8bdea3eabd7c25f65f9.jpg
20411 ms
ad01.jpg
20412 ms
ad02.jpg
20411 ms
8acc06569aa57e5d7a2359d5d2ddc0b8.png
20411 ms
857b86e82af316068879575f3e93ff32.jpg
20412 ms
33f2bf5f0c60b93ec8f716af1203f284.jpg
20413 ms
2594392d343d6f0d13d24126d41a0955.png
20414 ms
af3ab4a3239a29a72e5c3369714d1a1f.png
20414 ms
ad07.jpg
20414 ms
95de13cccbebf89bc514b1f9ca723796.jpg
20415 ms
17c73a06f12ddaed895cf9e8ea4dacb6.jpg
20416 ms
c057420d41c239f0315ff2a8e1c99b34.png
20416 ms
acff3f1aaee3dbec8e1f7f8a031b7f0e.jpg
20417 ms
5b4686b6b2f98468311599ee8666c6fb.jpg
20416 ms
9224e3b40623acc5adf785a347750beb.png
20392 ms
qrcode.gif
20392 ms
a_bg.png
20377 ms
xlogo_1x.png
20377 ms
i.png
20377 ms
s_but.png
20376 ms
jb.png
20368 ms
main_nav_icon1.jpg
20367 ms
main_nav_icon2.jpg
20367 ms
89530.html
6205 ms
adsbygoogle.js
13 ms
throw
702 ms
throw
664 ms
ca-pub-4413237575816591.js
212 ms
zrt_lookup.html
204 ms
show_ads_impl.js
148 ms
throw
722 ms
1000x90.gif
20131 ms
hm.js
20128 ms
stat.htm
669 ms
core.php
2048 ms
ads
249 ms
osd.js
15 ms
m_js_controller.js
55 ms
abg.js
66 ms
googlelogo_color_112x36dp.png
43 ms
mobile_unified_button_icon_white.png
27 ms
s
15 ms
x_button_blue2.png
4 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
7 ms
monitor.js
1249 ms
m.js
23 ms
runtime.js
30 ms
link.js
20 ms
cm.mediav.com
2621 ms
logo2.png
79 ms
yd.jpg
19205 ms
9.gif
3983 ms
sj.jpg
17645 ms
cm
1952 ms
6.css
6504 ms
jquery.js
8499 ms
b.js
8404 ms
6.js
5817 ms
10.js
5820 ms
app.gif
1060 ms
tm.png
14441 ms
yd2.jpg
12183 ms
gj_title.jpg
11178 ms
b.css
595 ms
h.js
8510 ms
gn_title.jpg
3741 ms
title_bg1.jpg
1812 ms
loading.gif
1442 ms
title_bg2.jpg
1957 ms
t_bg3.jpg
1749 ms
scroll.png
5374 ms
tleft.gif
1952 ms
tright.gif
4078 ms
101270101.json
929 ms
hm.gif
312 ms
mini.png
1457 ms
pluginlog.aspx
1551 ms
leiue.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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.
leiue.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
leiue.com 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
Tap targets are not sized appropriately
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leiue.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Leiue.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.
leiue.com
Open Graph description is not detected on the main page of Leiue. 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: