35.6 sec in total
2.8 sec
32.3 sec
438 ms
Click here to check amazing Doomxing Blog 163 content for China. Otherwise, check out these important facts you probably never knew about doomxing.blog.163.com
Visit doomxing.blog.163.comWe analyzed Doomxing.blog.163.com page load time and found that the first response time was 2.8 sec and then it took 32.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
doomxing.blog.163.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value6.8 s
7/100
25%
Value11.0 s
6/100
10%
Value1,130 ms
23/100
30%
Value0.749
6/100
15%
Value7.2 s
51/100
10%
2848 ms
185 ms
11445 ms
662 ms
143 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Doomxing.blog.163.com, 57% (67 requests) were made to Os.blog.163.com and 12% (14 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 619.1 kB (62%)
1.0 MB
384.8 kB
In fact, the total size of Doomxing.blog.163.com main page is 1.0 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. 30% of websites need less resources to load. Javascripts take 521.3 kB which makes up the majority of the site volume.
Potential reduce by 104.5 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 104.5 kB or 81% of the original size.
Potential reduce by 9.2 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. Doomxing Blog 163 images are well optimized though.
Potential reduce by 358.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 358.3 kB or 69% of the original size.
Potential reduce by 147.1 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. Doomxing.blog.163.com needs all CSS files to be minified and compressed as it can save up to 147.1 kB or 82% of the original size.
Number of requests can be reduced by 28 (25%)
111
83
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doomxing Blog 163. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
doomxing.blog.163.com
2848 ms
c.css
185 ms
b.css
11445 ms
6630133180817252049.jpg
662 ms
xcode.png
143 ms
1.0.0.js
96 ms
pc.js
15 ms
ph.js
15 ms
3405847218200036988.jpg
19605 ms
icon.png
147 ms
4019744142406246825.jpg
19593 ms
5144799624318579746.jpg
19593 ms
4019744142406246817.jpg
19592 ms
3179259861947651886.jpg
19592 ms
5144799624318579745.jpg
19592 ms
lnkbar.png
140 ms
image.png
141 ms
arrow24.png
140 ms
newtopbaricon8.png
140 ms
crossdomain.html
686 ms
crossdomain.html
689 ms
request.s
833 ms
analyse.png
639 ms
ava.s
3173 ms
crossdomain.html
2801 ms
ava.s
1902 ms
analyse.png
693 ms
analytics.js
20 ms
collect
217 ms
HomeBeanNew.getFriends.dwr
795 ms
UserBeanNew.getVisitor.dwr
1356 ms
NoteBeanNew.getNotesForPrev.dwr
1389 ms
HomeBeanNew.getClassifyModuleData.dwr
1419 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1526 ms
blogPhotoAd
361 ms
close_01.png
25 ms
top_bg.png
38 ms
bottom_bg.png
37 ms
left_bg.png
37 ms
right_bg.png
34 ms
left_top.png
34 ms
right_top.png
30 ms
left_bottom.png
32 ms
right_bottom.png
31 ms
shadow.png
22 ms
ava.s
673 ms
ava.s
760 ms
ava.s
940 ms
ava.s
962 ms
ava.s
1128 ms
ava.s
1163 ms
ava.s
3255 ms
ava.s
3472 ms
ava.s
1531 ms
ava.s
1562 ms
ava.s
1974 ms
ava.s
2001 ms
ava.s
4907 ms
ava.s
1987 ms
ava.s
4055 ms
ava.s
2388 ms
ava.s
7375 ms
ava.s
2767 ms
ava.s
3144 ms
ava.s
3567 ms
ava.s
3724 ms
ava.s
3985 ms
ava.s
3964 ms
ava.s
4287 ms
ava.s
5622 ms
ava.s
4505 ms
ava.s
6154 ms
ava.s
6501 ms
ava.s
6213 ms
ava.s
5348 ms
ava.s
5859 ms
ava.s
6111 ms
ava.s
6351 ms
ava.s
6572 ms
r
860 ms
ava.s
6530 ms
face50.gif
61 ms
face71.gif
66 ms
face39.gif
65 ms
face56.gif
66 ms
ava.s
6161 ms
ava.s
6092 ms
ava.s
9863 ms
ava.s
8076 ms
ad
623 ms
close2.png
83 ms
ava.s
7830 ms
ava.s
6252 ms
ava.s
5909 ms
ava.s
6340 ms
ava.s
7505 ms
jquery-1.4.2.js
84 ms
ad.bid.material_f84d827cd06e43a28ef019b53849c47d
1411 ms
ava.s
8563 ms
ava.s
8354 ms
ava.s
11030 ms
ava.s
7121 ms
ava.s
6883 ms
ava.s
11049 ms
ava.s
9640 ms
ava.s
7346 ms
ava.s
7603 ms
ava.s
7626 ms
ava.s
7310 ms
ava.s
7742 ms
ava.s
8153 ms
ava.s
7592 ms
ava.s
13418 ms
ava.s
7548 ms
ava.s
7365 ms
ava.s
7401 ms
ava.s
8604 ms
ava.s
7348 ms
doomxing.blog.163.com 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.
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
Links do not have a discernible name
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.
doomxing.blog.163.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
doomxing.blog.163.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
ZH
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doomxing.blog.163.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 Doomxing.blog.163.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.
doomxing.blog.163.com
Open Graph description is not detected on the main page of Doomxing Blog 163. 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: