3.1 sec in total
78 ms
2.7 sec
300 ms
Click here to check amazing Duo Project content for United States. Otherwise, check out these important facts you probably never knew about duoduoproject.org
Help DuoDuo Project stop the dog meat trade in China, and end the Yulin dog meat festival altogether. Help us to stop backward dog eating practices in China.
Visit duoduoproject.orgWe analyzed Duoduoproject.org page load time and found that the first response time was 78 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
duoduoproject.org performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value6.0 s
13/100
25%
Value5.0 s
64/100
10%
Value880 ms
32/100
30%
Value0.006
100/100
15%
Value11.4 s
19/100
10%
78 ms
55 ms
80 ms
53 ms
60 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Duoduoproject.org, 26% (37 requests) were made to Static.parastorage.com and 21% (30 requests) were made to Eclincher.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 3.1 MB (49%)
6.3 MB
3.2 MB
In fact, the total size of Duoduoproject.org main page is 6.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 83.3 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 83.3 kB or 82% of the original size.
Potential reduce by 368.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. Obviously, Duo Project needs image optimization as it can save up to 368.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.1 MB
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 2.1 MB or 74% of the original size.
Potential reduce by 501.4 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. Duoduoproject.org needs all CSS files to be minified and compressed as it can save up to 501.4 kB or 81% of the original size.
Number of requests can be reduced by 85 (65%)
131
46
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duo Project. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
duoduoproject.org
78 ms
www.duoduoproject.org
55 ms
bt
80 ms
require.min.js
53 ms
main-r.min.js
60 ms
viewer.css
93 ms
dynamicmodel
24 ms
50fcc2_8930f9dc394c966f4da8ba7324626100_951.json.z
200 ms
50fcc2_29a83a8819d2e1f70e545e308e3d7fc4_951.json.z
195 ms
ugc-viewer
64 ms
bt
191 ms
skins.min.js
58 ms
components.min.js
26 ms
utils.min.js
179 ms
core.min.js
186 ms
react-with-addons.min.js
56 ms
lodash.min.js
54 ms
TweenMax.min.js
57 ms
layout.min.js
54 ms
tpa.min.js
57 ms
fonts.min.js
55 ms
animations.min.js
54 ms
swfobject.min.js
174 ms
mousetrap.min.js
182 ms
tweenEngine.min.js
181 ms
DrawSVGPlugin.min.js
172 ms
react-dom.min.js
173 ms
ScrollToPlugin.min.js
172 ms
widgets.min.js
173 ms
experiment.js
172 ms
render.min.js
173 ms
wixappsCore.min.js
173 ms
wixappsBuilder.min.js
176 ms
zepto.min.js
168 ms
color.min.js
169 ms
react-dom-server.min.js
131 ms
latin.css
125 ms
bt
88 ms
bt
262 ms
dc.js
257 ms
50fcc2_9d9db6ee9a1949dda8d604b308666802.png
373 ms
css
126 ms
widget-new
139 ms
widget.php
226 ms
e316f544f9094143b9eac01f1f19e697.png
92 ms
9c4b521dd2404cd5a05ed6115f3a0dc8.png
106 ms
a1b09fe8b7f04378a9fe076748ad4a6a.png
105 ms
c090bd269d424abf8f035befe86158de.png
231 ms
50fcc2_9a36162eaff049d5bdd16e616a14561f.png
391 ms
50fcc2_fed4154fa8104e2892233c9e8334f5fa.jpg
206 ms
50fcc2_0de95dda098546a6a4f471e10d3ddafc.png
205 ms
50fcc2_da9da0b63620424588ff0ade877d81d0.jpg
229 ms
bt
92 ms
bt
91 ms
bt
204 ms
fonts.css
71 ms
font-awesome.min.css
80 ms
widget-vendor.6fed0379.css
82 ms
css
78 ms
main_widget.4d0e3f28.css
193 ms
style.css
93 ms
widget-vendor-after.57764994.css
94 ms
jquery.min.js
190 ms
wix.min.js
76 ms
angular.min.js
261 ms
lodash.compat.min.js
76 ms
angular-translate.min.js
169 ms
angular-translate-loader-static-files.min.js
168 ms
angular-local-storage.min.js
167 ms
restangular.min.js
168 ms
widget-vendor.20c278bd.js
180 ms
widget-scripts.cdbf6eb2.js
167 ms
__utm.gif
116 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
106 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
126 ms
80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff
29 ms
20323430-24f4-4767-9d4d-060d1e89758a.woff
30 ms
ae844b11-5158-4caf-90b4-7ace49ac3440.woff
104 ms
d3bbaa1b-d5e3-431f-93a7-9cea63601bb6.woff
300 ms
bc176270-17fa-4c78-a343-9fe52824e501.woff
29 ms
font-awesome.css
285 ms
widget.css
96 ms
post_manager.css
277 ms
jquery.min.js
351 ms
ui-lib.min.js
260 ms
common.js
151 ms
jquery.scrollstop.js
278 ms
jquery.scrollsnap.js
279 ms
jquery.dragscroll.js
278 ms
hammer.min.js
279 ms
masonry.pkgd.min.js
286 ms
jquery.sortable.min.js
288 ms
widget.js
287 ms
widgets.js
411 ms
ga-audiences
333 ms
mixpanel-2.2.min.js
261 ms
ugc-viewer
180 ms
en_v3.new.json
32 ms
widget_v9.html
32 ms
loading.gif
101 ms
240beabaa3f211e38a6712c2a60883a9_6.jpg
99 ms
ec-wix-square-logo.png
100 ms
926369_1396067027327741_343096849_a.jpg
100 ms
1740980_483490438444362_2004093555_a.jpg
100 ms
925163_538580186240959_1749328479_a.jpg
62 ms
1740391_1408562132730528_1961662739_a.jpg
137 ms
1688265_374859745990567_701740506_a.jpg
138 ms
fb1.jpeg
128 ms
10502765_456662334470539_456662227803883_22646_1559_b.jpg
140 ms
10478111_456548941148545_4986373120857747686_n.png
136 ms
fb4.jpeg
136 ms
fb5.jpeg
139 ms
forbes_1200x1200.jpg
235 ms
BssNajPIgAAZECd.png
321 ms
BssBCoGIAAAseXI.png
235 ms
Bsr9YtWIYAIsSgK.png
241 ms
BsrtXfWIIAAcU6x.png
334 ms
settings
88 ms
wix_demo_preview.d4d66702.png
81 ms
50fcc2_fed4154fa8104e2892233c9e8334f5fa.jpg
550 ms
50fcc2_0de95dda098546a6a4f471e10d3ddafc.png
1396 ms
50fcc2_da9da0b63620424588ff0ade877d81d0.jpg
641 ms
ga.js
68 ms
28 ms
widget_below_v9.html
72 ms
css
126 ms
__utm.gif
66 ms
__utm.gif
40 ms
__utm.gif
51 ms
__utm.gif
118 ms
__utm.gif
117 ms
__utm.gif
80 ms
__utm.gif
116 ms
__utm.gif
116 ms
__utm.gif
130 ms
__utm.gif
131 ms
__utm.gif
131 ms
phone_v9.html
56 ms
newWidgetTitles_v9.html
33 ms
newWidgetValidations_v9.html
27 ms
poweredByShoutout_v9.html
83 ms
e56ecb6d-da41-4bd9-982d-2d295bec9ab0.woff
10 ms
duoduoproject.org 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
Links do not have a discernible name
duoduoproject.org 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
Page has valid source maps
duoduoproject.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duoduoproject.org 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 Duoduoproject.org 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.
duoduoproject.org
Open Graph description is not detected on the main page of Duo Project. 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: