102.6 sec in total
4.5 sec
10.9 sec
87.2 sec
Visit lread.net now to see the best up-to-date Lread content for Taiwan and also check out these interesting facts you probably never knew about lread.net
乐阅读是广大书友最值得收藏的小说阅读网,网站收录了当前最火热的玄幻小说、修真小说、穿越小说、都市小说、网游小说、科幻小说等网络小说,提供高质量的免费小说阅读,是广大网络小说爱好者必备的小说阅读网。
Visit lread.netWe analyzed Lread.net page load time and found that the first response time was 4.5 sec and then it took 98.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
lread.net performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value2.8 s
83/100
25%
Value25.7 s
0/100
10%
Value0 ms
100/100
30%
Value0.06
98/100
15%
Value2.7 s
97/100
10%
4454 ms
2816 ms
567 ms
559 ms
565 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 84% of them (47 requests) were addressed to the original Lread.net, 11% (6 requests) were made to Bdimg.share.baidu.com and 4% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Lread.net.
Page size can be reduced by 96.4 kB (24%)
397.8 kB
301.4 kB
In fact, the total size of Lread.net main page is 397.8 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. Images take 324.1 kB which makes up the majority of the site volume.
Potential reduce by 26.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 26.3 kB or 68% of the original size.
Potential reduce by 49.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. Obviously, Lread needs image optimization as it can save up to 49.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 20.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 20.2 kB or 61% of the original size.
Potential reduce by 17 B
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. Lread.net has all CSS files already compressed.
Number of requests can be reduced by 17 (31%)
54
37
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lread. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
lread.net
4454 ms
www.lread.net
2816 ms
common.css
567 ms
style.css
559 ms
style.js
565 ms
top.css
553 ms
denglu.js
563 ms
sethome.gif
375 ms
addfavorites.gif
373 ms
153s.jpg
1584 ms
413s.jpg
1602 ms
233s.jpg
1580 ms
347s.jpg
1597 ms
393s.jpg
1577 ms
394s.jpg
1598 ms
395s.jpg
1599 ms
396s.jpg
1599 ms
397s.jpg
1600 ms
398s.jpg
1601 ms
399s.jpg
1599 ms
400s.jpg
1600 ms
401s.jpg
1684 ms
402s.jpg
1684 ms
403s.jpg
1857 ms
375s.jpg
1863 ms
20s.jpg
1861 ms
646s.jpg
1924 ms
9260s.jpg
2075 ms
753s.jpg
2220 ms
16288s.jpg
2434 ms
27s.jpg
2413 ms
213s.jpg
2500 ms
81s.jpg
2474 ms
24s.jpg
2583 ms
13s.jpg
2725 ms
85s.jpg
2964 ms
9759s.jpg
2969 ms
149s.jpg
2970 ms
58s.jpg
3019 ms
148s.jpg
3222 ms
238s.jpg
3022 ms
login_oa_bar.gif
2638 ms
logo.gif
2656 ms
index.js
2790 ms
bookname.js
1978 ms
showall.js
2041 ms
17332s.jpg
2012 ms
shell_v2.js
541 ms
bds_s_v2.js
657 ms
bdsstyle.css
307 ms
getnum
824 ms
is.png
578 ms
sc.png
637 ms
h.js
529 ms
logger.js
299 ms
hm.gif
278 ms
lread.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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
lread.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
General
Impact
Issue
Browser errors were logged to the console
lread.net SEO score
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 Lread.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 Lread.net 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.
lread.net
Open Graph description is not detected on the main page of Lread. 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: