89.5 sec in total
91 ms
88.4 sec
1.1 sec
Visit duier.me now to see the best up-to-date DUIER content and also check out these interesting facts you probably never knew about duier.me
Visit duier.meWe analyzed Duier.me page load time and found that the first response time was 91 ms and then it took 89.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 15 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
duier.me performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.002
100/100
15%
Value0
0/100
10%
91 ms
11394 ms
3024 ms
859 ms
857 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Duier.me, 78% (89 requests) were made to Duier.cc and 11% (12 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Duier.cc.
Page size can be reduced by 516.4 kB (41%)
1.3 MB
746.5 kB
In fact, the total size of Duier.me main page is 1.3 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. Images take 590.3 kB which makes up the majority of the site volume.
Potential reduce by 29.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 29.9 kB or 80% of the original size.
Potential reduce by 19.1 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. DUIER images are well optimized though.
Potential reduce by 333.8 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 333.8 kB or 70% of the original size.
Potential reduce by 133.7 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. Duier.me needs all CSS files to be minified and compressed as it can save up to 133.7 kB or 85% of the original size.
Number of requests can be reduced by 71 (78%)
91
20
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DUIER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
duier.me
91 ms
www.duier.cc
11394 ms
system.base.css
3024 ms
system.menus.css
859 ms
system.messages.css
857 ms
system.theme.css
3077 ms
comment.css
896 ms
date.css
1676 ms
field.css
1780 ms
node.css
2525 ms
search.css
2642 ms
user.css
4060 ms
views.css
3357 ms
tm_lazyload.css
3874 ms
colorbox.css
7539 ms
ctools.css
4415 ms
panels.css
4696 ms
animate.css
6408 ms
font-awesome.css
5927 ms
shCoreDefault.css
7226 ms
tm_follow.css
10804 ms
tm_block_bg.css
6560 ms
superfish.css
6723 ms
boilerplate.css
7276 ms
style.css
17242 ms
maintenance-page.css
7959 ms
skeleton.css
8198 ms
jquery.min.js
18776 ms
jquery.once.js
9043 ms
drupal.js
9913 ms
jquery.lazyloader.js
10227 ms
shCore.js
20016 ms
jquery.colorbox-min.js
12293 ms
colorbox.js
10207 ms
wow.js
14190 ms
tm-parallax.js
16378 ms
jquery.mb.YTPlayer.js
17750 ms
tm_block_bg_video.js
14873 ms
jquery.hoverIntent.minified.js
15660 ms
sftouchscreen.js
15556 ms
superfish.js
16143 ms
supersubs.js
15383 ms
superfish.js
15473 ms
theme986.core.js
15504 ms
jquery.loader.js
15467 ms
style-mobile.css
15399 ms
skeleton-mobile.css
15333 ms
jquery.mobilemenu.js
15148 ms
jquery.debouncedresize.js
15162 ms
jquery.easing.js
15109 ms
jquery.ui.totop.js
15132 ms
jquery.cookie.js
13910 ms
tm-stick-up.js
13494 ms
tformer.js
14661 ms
device.min.js
13684 ms
jquery.mousewheel.min.js
13271 ms
jquery.simplr.smoothscroll.min.js
13336 ms
migrate.js
13149 ms
tm-parallax.js
12801 ms
addthis.js
12948 ms
css
44 ms
css
62 ms
css
71 ms
logo.png
19783 ms
bg03.jpg
19790 ms
01.png
13761 ms
shadow-top.png
2315 ms
shadow-bottom.png
2325 ms
img-border-274-black-1.png
3988 ms
DUIER_Deepbrow_FOURTOGRAB%20%284%29.jpg
7663 ms
img-border-274-black-2.png
5851 ms
11888626_680701475362653_4176368980227220406_o.jpg
9260 ms
img-border-274-black-3.png
9770 ms
1445406711513792.jpg
16465 ms
02.png
15239 ms
1692399951.jpg
10957 ms
1782491629.jpg
14467 ms
bg01.png
15064 ms
03.png
19782 ms
img-border-246-white.png
18057 ms
IMG_5720.JPG
18853 ms
04.png
19785 ms
icon-mail.png
19785 ms
erweima.jpg
19787 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
123 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
160 ms
187TYb8ysVvxar86IcDsZ_esZW2xOQ-xsNqO47m55DA.ttf
231 ms
K6ngFdK5haaaRGBV8waDwA.ttf
269 ms
nHiQo1BypvYzt95zlPq1TvesZW2xOQ-xsNqO47m55DA.ttf
239 ms
fontawesome-webfont.woff
19745 ms
share.js
4535 ms
overlay.png
19674 ms
IMG_0181_2.jpg
19673 ms
110893555_3.jpg
19674 ms
404660798_0.jpg
19672 ms
bg05.jpg
19673 ms
widget_v2.139.js
217 ms
__$$__stringtable_lang_zh_CN.js
28 ms
avatar_simple_visitor.png
130 ms
aL63HcygAAVYuCCsAAA==
1 ms
share_api.js
6366 ms
share_view.js
907 ms
image_api.js
3700 ms
image_view.js
911 ms
tangram.js
10493 ms
view_base.js
358 ms
logger.js
356 ms
api_base.js
402 ms
partners.js
417 ms
share_style1_16.css
419 ms
icons_1_16.png
11607 ms
fontawesome-webfont.ttf
19944 ms
totop.png
2140 ms
fontawesome-webfont.svg
19950 ms
duier.me accessibility score
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
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
duier.me 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
duier.me SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duier.me 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), while the claimed language is English. Our system also found out that Duier.me 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.
duier.me
Open Graph description is not detected on the main page of DUIER. 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: