20.1 sec in total
4.1 sec
15.7 sec
216 ms
Welcome to god2speed.blog.163.com homepage info - get ready to check God 2 Speed Blog 163 best content for China right away, or after learning these important things about god2speed.blog.163.com
Visit god2speed.blog.163.comWe analyzed God2speed.blog.163.com page load time and found that the first response time was 4.1 sec and then it took 16 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
god2speed.blog.163.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value7.6 s
3/100
25%
Value12.2 s
3/100
10%
Value830 ms
35/100
30%
Value0.75
6/100
15%
Value7.8 s
44/100
10%
4126 ms
13 ms
3509 ms
7495 ms
5491 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original God2speed.blog.163.com, 18% (6 requests) were made to Img3.126.net and 18% (6 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source G.163.com.
Page size can be reduced by 564.2 kB (67%)
844.8 kB
280.6 kB
In fact, the total size of God2speed.blog.163.com main page is 844.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. 40% of websites need less resources to load. Javascripts take 521.4 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.4 kB or 77% of the original size.
Potential reduce by 10.5 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, God 2 Speed Blog 163 needs image optimization as it can save up to 10.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 358.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 358.4 kB or 69% of the original size.
Potential reduce by 154.8 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. God2speed.blog.163.com needs all CSS files to be minified and compressed as it can save up to 154.8 kB or 82% of the original size.
Number of requests can be reduced by 14 (42%)
33
19
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of God 2 Speed 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 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
god2speed.blog.163.com
4126 ms
c.css
13 ms
b.css
3509 ms
r
7495 ms
ava.s
5491 ms
6630133180817252049.jpg
1027 ms
xcode.png
7 ms
1.0.0.js
379 ms
pc.js
1943 ms
ph.js
1960 ms
4564961172310468132.jpg
1285 ms
icon.png
38 ms
2869918862558887485.jpg
1281 ms
4022277417212311633.jpg
1288 ms
lnkbar.png
36 ms
image.png
36 ms
arrow24.png
37 ms
newtopbaricon8.png
37 ms
analyse.png
980 ms
analytics.js
19 ms
collect
13 ms
rec.s
4146 ms
reset.css
9 ms
ad.css
10 ms
02f4cd9972c54c039cd470a7fc1832c0.jpg
1062 ms
jquery-1.4.2.js
10 ms
scroll.js
19 ms
d78d380a9fda455c95bfba1f4d27592d.jpg
1588 ms
cc69c48c43d14af5a8cf92aa2159d936.jpg
1065 ms
3e61bf8b33624ca2ba2fbaba615d615c.jpg
1149 ms
e02c6b842b084e92a2b201d5cf869a84.jpg
1396 ms
7ef7298b-0ef4-42dd-81d0-7de96f1ca798
2208 ms
logo-24.png
31 ms
discount-1.png
32 ms
god2speed.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.
god2speed.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
god2speed.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 God2speed.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 God2speed.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.
god2speed.blog.163.com
Open Graph description is not detected on the main page of God 2 Speed 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: