15.6 sec in total
1.2 sec
13.8 sec
635 ms
Welcome to diglog.com homepage info - get ready to check Diglog best content for China right away, or after learning these important things about diglog.com
收集网络上最新鲜有趣的内容,让你感觉到值得分享给朋友。
Visit diglog.comWe analyzed Diglog.com page load time and found that the first response time was 1.2 sec and then it took 14.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
diglog.com performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value2.7 s
86/100
25%
Value3.0 s
94/100
10%
Value500 ms
58/100
30%
Value0.061
97/100
15%
Value7.2 s
51/100
10%
1191 ms
5456 ms
1784 ms
1394 ms
4266 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Diglog.com, 49% (33 requests) were made to Img.diglog.com and 15% (10 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (5.7 sec) relates to the external source Img.diglog.com.
Page size can be reduced by 543.7 kB (46%)
1.2 MB
637.6 kB
In fact, the total size of Diglog.com main page is 1.2 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. 35% of websites need less resources to load. Javascripts take 550.1 kB which makes up the majority of the site volume.
Potential reduce by 43.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 43.5 kB or 74% of the original size.
Potential reduce by 82.6 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, Diglog needs image optimization as it can save up to 82.6 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 368.7 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 368.7 kB or 67% of the original size.
Potential reduce by 48.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. Diglog.com needs all CSS files to be minified and compressed as it can save up to 48.8 kB or 82% of the original size.
Number of requests can be reduced by 21 (32%)
65
44
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Diglog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
diglog.com
1191 ms
www.diglog.com
5456 ms
pure-min.css
1784 ms
css.css
1394 ms
jquery-1.4.2.min.js
4266 ms
c.js
717 ms
f.js
972 ms
dig.js
387 ms
hm.js
2488 ms
logo.v2013.jpg
816 ms
good_24_24.png
416 ms
thumb_fc7b44a6-af5c-49c4-aec6-2aefc44faa5c.jpg
1061 ms
thumb_2c179050-927b-49ca-b3da-7962dbd8478e.jpg
1548 ms
thumb_ab1e40d0-85e2-467a-ad69-81a035ae8722.jpg
1177 ms
thumb_613c0972-ee29-49de-9b80-0b87b1ed21b3.jpg
1205 ms
thumb_2057b47e-66e9-4d93-821d-2b715be5e2d0.jpg
2564 ms
thumb_7114d1c8-0aa4-4a17-b9af-12807461ed34.jpg
2026 ms
hcrm
1523 ms
thumb_b5e0316d-a395-482f-8cfb-6374add8a292.jpg
1406 ms
thumb_9249f778-b75a-4aed-ad32-1464d24dc167.jpg
1893 ms
thumb_fbd31559-d0ee-4eee-abea-8739e3a2d858.jpg
1905 ms
thumb_5aa78622-6f1c-4b81-ad3f-b0b42db71c98.jpg
2254 ms
thumb_52f2fd85-e0cd-488e-84a0-9937ddd40612.jpg
3288 ms
thumb_efaa6c6a-edcb-410e-a138-0c1a0294dc95.jpg
2912 ms
thumb_7a101ba4-f374-4f08-894e-5ae7cb6e38eb.jpg
3060 ms
thumb_e4489d5c-8555-4152-9ddc-816a138a5025.jpg
3580 ms
thumb_7d9c8a8f-ad9e-4d03-a0db-e45f53459d46.jpg
3731 ms
thumb_411531e6-b40d-4374-bf76-e65700d3546a.jpg
4059 ms
thumb_667509f4-b0ed-4bd1-ba1f-da6c688d0b12.jpg
3402 ms
thumb_f8ab97b1-b60b-4182-8d02-7c4b15132501.jpg
3442 ms
thumb_afdc824c-b6a5-49c2-855c-743d926c6165.jpg
4151 ms
thumb_fb9aa8f5-15c8-44e9-9a5f-15148f669c70.jpg
5100 ms
thumb_aedcf8af-e664-4759-bbde-d07f5ad48015.jpg
4268 ms
thumb_d11d0db1-5a24-4ca9-a1dc-0d28d5e9cfd6.jpg
4389 ms
thumb_ea490519-15a5-4664-9aec-3a0b0e117dbe.jpg
4530 ms
thumb_435e0d84-9698-4db4-a802-a731af82851a.jpg
4458 ms
thumb_d5e9521d-f298-4e1a-bb1b-c046a044192c.jpg
4973 ms
thumb_76a0e4d2-f3a8-49a6-b36e-ac845c91f8c0.jpg
4645 ms
thumb_430f163a-cadd-461e-8c09-aaacabc4b74e.jpg
5654 ms
hcrm
931 ms
hcrm
802 ms
dynamicFloat.js
531 ms
hcrm
1136 ms
xuanfu_close.png
482 ms
hcrm
2052 ms
hcrm
570 ms
cpro.js
695 ms
adx.php
732 ms
icon_12px.png
528 ms
adPic.new.20150909.min.js
112 ms
adx.php
868 ms
hm.gif
454 ms
adx.php
663 ms
rBEhWlJYrAEIAAAAAAACetYAYQwAAECuwP__W4AAAKS951.png
87 ms
570791e4N689af156.jpg
99 ms
click.min.js
42 ms
bot-patch.min.js
71 ms
reduce_bd-logo1_oper.png
525 ms
closefeedback.min.js
512 ms
reduce_promotion_oper.png
491 ms
bd_logo.png
496 ms
bg_rb.png
520 ms
55e40d3fN2a01189f.png
80 ms
o.htm
482 ms
wh.js
724 ms
ac.js
480 ms
hm.gif
452 ms
diglog.com accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
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
diglog.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
diglog.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
Tap targets are not sized appropriately
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diglog.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 Diglog.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.
diglog.com
Open Graph description is not detected on the main page of Diglog. 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: