Access qidian.com. 小说,小说网,最新热门小说-起点中文网_阅文集团旗下网站

qidian.com screenshot

23

Performance

Renders faster than
42% of other websites
61

Accessibility

Visual factors better than
that of 27% of websites
75

Best Practices

More advanced features
available than in
36% of websites
91

SEO

Google-friendlier than
71% of websites

First Response

1.1 sec

Resources Loaded

22.3 sec

Page Rendered

1.3 sec

qidian.com screenshot

About Website

Visit qidian.com now to see the best up-to-date Qidian content for China and also check out these interesting facts you probably never knew about qidian.com

起点中文网,最新热门小说网站，提供玄幻小说、武侠小说、原创小说、网游小说、都市小说、言情小说、青春小说、科幻小说等首发小说,最新章节在线阅读。更多精彩尽在起点中文网小说网。

Visit qidian.com

Key Findings

We analyzed Qidian.com page load time and found that the first response time was 1.1 sec and then it took 23.6 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.

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,130 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

qidian.com

1112 ms

index.aspx

1633 ms

Default.aspx

36 ms

default.css

26 ms

frame_login_up2014.css

24 ms

Our browser made a total of 189 requests to load all elements on the main page. We found that 28% of them (53 requests) were addressed to the original Qidian.com, 31% (59 requests) were made to Image.cmfu.com and 10% (18 requests) were made to A.game.qidian.com. The less responsive or slowest element that took the longest time to load (17.3 sec) relates to the external source Tajs.qq.com.

Content Size

5.4 MB

After Optimization

2.8 MB

In fact, the total size of Qidian.com main page is 5.4 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. 65% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 412.8 kB

Original 494.0 kB
After minification 462.1 kB
After compression 81.2 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 412.8 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 147.2 kB

Original 2.2 MB
After minification 2.0 MB

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. Qidian images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 1.4 MB

Original 2.0 MB
After minification 1.8 MB
After compression 569.6 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 1.4 MB or 72% of the original size.

CSS Optimization

-84%

Potential reduce by 603.3 kB

Original 721.3 kB
After minification 658.6 kB
After compression 118.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. Qidian.com needs all CSS files to be minified and compressed as it can save up to 603.3 kB or 84% of the original size.

Requests Now

174

After Optimization

135

The browser has sent 174 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qidian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ZH
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qidian.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 Qidian.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.

Social Sharing Optimization

qidian.com

Open Graph description is not detected on the main page of Qidian. 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: