38.9 sec in total
3.8 sec
31.2 sec
4 sec
Visit rosiexqh.diandian.com now to see the best up-to-date Rosiexqh Diandian content for China and also check out these interesting facts you probably never knew about rosiexqh.diandian.com
点点数据,专业移动应用/游戏App数据查询分析平台,为您提供App市场份额分析(App下载/收入数据)、用户行为分析(App活跃、App留存、使用次数、使用时长、用户画像)等App数据分析统计。
Visit rosiexqh.diandian.comWe analyzed Rosiexqh.diandian.com page load time and found that the first response time was 3.8 sec and then it took 35.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. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
rosiexqh.diandian.com performance score
name
value
score
weighting
Value16.6 s
0/100
10%
Value17.8 s
0/100
25%
Value25.8 s
0/100
10%
Value1,690 ms
11/100
30%
Value0.011
100/100
15%
Value19.0 s
3/100
10%
3792 ms
3025 ms
2708 ms
457 ms
2645 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Rosiexqh.diandian.com, 54% (29 requests) were made to S.srcdd.com and 19% (10 requests) were made to M3.img.srcdd.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source M1.img.srcdd.com.
Page size can be reduced by 418.9 kB (68%)
617.8 kB
198.9 kB
In fact, the total size of Rosiexqh.diandian.com main page is 617.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. 45% of websites need less resources to load. Javascripts take 277.8 kB which makes up the majority of the site volume.
Potential reduce by 134.7 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. This page needs HTML code to be minified as it can gain 34.0 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 134.7 kB or 90% of the original size.
Potential reduce by 10.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. Obviously, Rosiexqh Diandian needs image optimization as it can save up to 10.9 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 180.5 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 180.5 kB or 65% of the original size.
Potential reduce by 92.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. Rosiexqh.diandian.com needs all CSS files to be minified and compressed as it can save up to 92.8 kB or 86% of the original size.
Number of requests can be reduced by 12 (25%)
48
36
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rosiexqh Diandian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
rosiexqh.diandian.com
3792 ms
startpage.$7250.less
3025 ms
seed.$6804.js
2708 ms
trackerbase.js
457 ms
feed.$7227.js
2645 ms
util.$7202.js
445 ms
DD6DD1EA2A1F2FBF15141F72BD7B9C438C062A7A0153B_500_167.GIF
1705 ms
htmlbg.$5752.png
432 ms
header.$5752.png
2325 ms
logo-0518.$6396.png
808 ms
split.$6883.png
808 ms
content-holder.$5106.png
807 ms
feed-icons.$6973.png
3432 ms
feed-bg-sprites.$5106.png
1148 ms
8FA5F72EA0B42727AE4BE40B42A01E0A_S64_64_64.jpeg
1609 ms
loading-small.$6925.gif
1073 ms
feed-img-too-high-tip.$5594.png
3717 ms
D3E62DB058802CA5E2002AE07F6C3932_S64_64_64.JPEG
1120 ms
sky.$6939.js
2581 ms
core.js
2263 ms
aside-reg-login-line.$7164.png
2253 ms
aside-login-register-btn.$7164.png
2914 ms
reg-login-formv2.$7176.js
2615 ms
sidemenu.$6372.png
5627 ms
sidemenu-item.$5106.png
2910 ms
sidemenu-sub-item.$5106.png
2931 ms
DAFB9BA8E02EB40B8873B5087B1620CE_S40_40_40.PNG
1226 ms
5DBDF4B52332BB4E3C8DA2BBE143D992_S40_40_40.JPEG
19889 ms
2C329347AC6CF87E423162C8B63DDC31_S40_40_40.JPEG
19888 ms
EAA48D281AA5B2A2C123887F4E21F04E_S40_40_40.jpeg
754 ms
t.gif
358 ms
ga.$5928.js
6136 ms
feed-short-tip.$6396.png
3226 ms
template.js
1077 ms
Dialog.js
2266 ms
feedslide.js
3004 ms
photo-reply.js
11518 ms
__utm.gif
1019 ms
frameupload.js
304 ms
4EB9238A67EDF3505087AFDE2674C713_ORIG_245_150.gif
4286 ms
83619575B159C4ED6AC9B0A1F79071D4_ORIG_245_150.gif
5620 ms
ABA2D0CF682E5C1E0C89B412A3012FBE_ORIG_245_150.gif
4685 ms
F5B931C1A4345E1B713295099A006233_ORIG_245_150.gif
2445 ms
030139D9DBA6235CA36A0ECE10B8BC06_ORIG_500_250.gif
2252 ms
78E9AEF3117641A482555D8DDAACFAE202122212555E3_500_273.GIF
2776 ms
EC81A35F774BD22D7BBB49C93CBB6C3F_B500_900_500_625.jpeg
1154 ms
1B3774DA3923B9A69193BFE2C092CDB2_B250_400_250_202.jpeg
1208 ms
C1F458F18DFFE79B8AEED1003977342829C08AF51B3A4_500_184.GIF
1715 ms
2395F46B27762710C5F42830AE1E8BF08E078112DAC5E_500_184.GIF
3143 ms
9C88D000DB79689114E5F4B54DBFD3F6_ORIG_500_272.gif
9615 ms
B413524B94C4DC33B3CFDE6EFE748F17_500_275.GIF
4682 ms
12877904B1EA310A0235C08B623C3E8504D6375CA6333_500_184.GIF
2505 ms
5A95E27DB039782F053F59C2952ABB24024289544F237_500_184.GIF
1404 ms
proxy.html
5402 ms
rosiexqh.diandian.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
Image elements do not have [alt] attributes
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.
rosiexqh.diandian.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
rosiexqh.diandian.com 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 doesn't use legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rosiexqh.diandian.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Rosiexqh.diandian.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.
rosiexqh.diandian.com
Open Graph description is not detected on the main page of Rosiexqh Diandian. 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: