2.9 sec in total
303 ms
2.4 sec
264 ms
Visit 400didi.com now to see the best up-to-date 400 Didi content and also check out these interesting facts you probably never knew about 400didi.com
Visit 400didi.comWe analyzed 400didi.com page load time and found that the first response time was 303 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
400didi.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value3.8 s
54/100
25%
Value3.8 s
84/100
10%
Value110 ms
97/100
30%
Value0.032
100/100
15%
Value4.1 s
86/100
10%
303 ms
124 ms
130 ms
304 ms
91 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that 32% of them (8 requests) were addressed to the original 400didi.com, 48% (12 requests) were made to 44img1.bbbplayer.com and 4% (1 request) were made to S0.qhimg.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source 44img1.bbbplayer.com.
Page size can be reduced by 96.6 kB (33%)
294.7 kB
198.0 kB
In fact, the total size of 400didi.com main page is 294.7 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. 20% of websites need less resources to load. Images take 163.9 kB which makes up the majority of the site volume.
Potential reduce by 12.9 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 12.9 kB or 75% of the original size.
Potential reduce by 7.9 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. 400 Didi images are well optimized though.
Potential reduce by 68.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 68.3 kB or 66% of the original size.
Potential reduce by 7.6 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. 400didi.com needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 77% of the original size.
Number of requests can be reduced by 5 (21%)
24
19
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 400 Didi. 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 as a result speed up the page load time.
400didi.com
303 ms
style.css
124 ms
top.js
130 ms
171.js
304 ms
jquery.lazyload.js
91 ms
tj.js
130 ms
TB2x4j9dFXXXXX.XpXXXXXXXXXX_!!1731999033.gif
306 ms
005M5Ibcgw1f1d5gnlocmg30qo01odgs.gif
28 ms
160328064632360.jpg
1750 ms
160328064625308.jpg
1750 ms
160328064623436.jpg
1750 ms
160328064607462.jpg
1752 ms
160328064604451.jpg
1752 ms
160328064601440.jpg
1752 ms
160328064421257.jpg
1815 ms
160328064414705.jpg
1815 ms
160328063905902.jpg
1879 ms
160328063902548.jpg
1882 ms
160328063855076.jpg
1881 ms
160328063850817.jpg
1881 ms
jc.js
68 ms
006eoLkfgw1ex92jggtkdg30r801owl9.gif
42 ms
ico.png
129 ms
text.png
128 ms
18712263.js
1014 ms
400didi.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.
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
400didi.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
400didi.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
N/A
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 400didi.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 400didi.com main page’s claimed encoding is gb2312. 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.
400didi.com
Open Graph description is not detected on the main page of 400 Didi. 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: