6.6 sec in total
1.1 sec
4.8 sec
733 ms
Visit dyne.org now to see the best up-to-date Dyne content for India and also check out these interesting facts you probably never knew about dyne.org
Dyne.org is a software foundry and research organization dedicated to share the benefits of freedom in the digital world. We share our ideas and inventions to promote horizontal access to technology, ...
Visit dyne.orgWe analyzed Dyne.org page load time and found that the first response time was 1.1 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
dyne.org performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value14.9 s
0/100
25%
Value22.6 s
0/100
10%
Value890 ms
32/100
30%
Value0.451
20/100
15%
Value17.9 s
4/100
10%
1052 ms
73 ms
118 ms
60 ms
220 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 73% of them (77 requests) were addressed to the original Dyne.org, 15% (16 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Dyne.org.
Page size can be reduced by 1.2 MB (36%)
3.2 MB
2.1 MB
In fact, the total size of Dyne.org main page is 3.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. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 92.0 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 15.9 kB, which is 14% 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 92.0 kB or 81% of the original size.
Potential reduce by 71.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. Dyne images are well optimized though.
Potential reduce by 373.6 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 373.6 kB or 74% of the original size.
Potential reduce by 619.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. Dyne.org needs all CSS files to be minified and compressed as it can save up to 619.4 kB or 89% of the original size.
Number of requests can be reduced by 47 (55%)
86
39
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dyne. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.dyne.org
1052 ms
wp-emoji-release.min.js
73 ms
style.css
118 ms
css
60 ms
style.css
220 ms
styles.css
119 ms
colorbox.css
123 ms
style3.css
120 ms
responsive.css
124 ms
style.css
259 ms
wp-syntax.css
153 ms
style.css
395 ms
style.css
156 ms
css
69 ms
css
82 ms
css
93 ms
shortcodes.css
227 ms
shortcodes_responsive.css
189 ms
magnific_popup.css
190 ms
surbma-divi-extras.css
225 ms
wp-cat-list-theme.css
230 ms
wp-cat-list-light.css
253 ms
jquery.js
369 ms
jquery-migrate.min.js
264 ms
scripts.js
263 ms
script.js
287 ms
geo-selects.js
292 ms
paypalstd-script.js
332 ms
seamless-donations.js
334 ms
timeline.min.js
321 ms
colorbox.js
328 ms
7.js
415 ms
core.min.js
357 ms
frontend-builder-global-functions.js
364 ms
idle-timer.min.js
366 ms
custom.js
369 ms
qppr_frontend_script.min.js
411 ms
jquery.uniform.min.js
410 ms
custom.js
434 ms
idle-timer.min.js
412 ms
jquery.mobile.custom.min.js
413 ms
custom.js
425 ms
jquery.fitvids.js
360 ms
waypoints.min.js
327 ms
jquery.magnific-popup.js
362 ms
frontend-builder-scripts.js
401 ms
wp-embed.min.js
346 ms
jquery.hashchange.js
360 ms
Divi
1123 ms
moebius-band.png
60 ms
lion-rastasoft1.png
68 ms
cafudda.jpg
61 ms
heart_and_stars.png
59 ms
Dyne-bolic-141-logo.png
602 ms
shinobi-180x120.png
592 ms
freecoin_logo-425.png
603 ms
D-CENT-small.jpg
601 ms
dowse-logo.png
602 ms
entropical-ennecromasse-leafskeleton-positive.jpg
907 ms
Frederick_Noronha.jpg
727 ms
gnu_hornedword.png
675 ms
TheGrugq.jpeg
681 ms
cafudda-thinkdotank.jpg
781 ms
timeline-line-bg.gif
675 ms
timeline_decade_tick-dot-left.gif
732 ms
timeline_decade_tick-dot-right.gif
728 ms
baobabconnections-400x284.jpg
779 ms
shot-141-1-400x284.jpg
837 ms
grab_apr2004-2-400x284.jpg
874 ms
dyne-at-wintercamp.jpg
913 ms
dancing-tux.gif
849 ms
libre-35444_140x140.png
849 ms
nyanmailcat-circle-512.png
940 ms
ipernav-trans.png
927 ms
foster_privacy.png
926 ms
hasciicam_eye.png
958 ms
dyndy-banner.jpg
994 ms
lower-border-serial-2500.png
993 ms
premade-image-10.png
969 ms
bMbHEMwSUmkzcK2x_74QbA.ttf
595 ms
lhhB5ZCwEkBRbHMSnYuKyA.ttf
634 ms
7-wH0j2QCTHKgp7vLh9-sQ.ttf
721 ms
B7BtHjNYwAp3HgLNagENOQ.ttf
719 ms
9LpJGtNuM1D8FAZ2BkJH2Q.ttf
695 ms
b9hP8wd30SygxZjGGk4DCQ.ttf
719 ms
NWdMogIO7U6AtEM4dDdf_aCWcynf_cDxXwCLxiixG1c.ttf
695 ms
j-TYDdXcC_eQzhhp386SjaCWcynf_cDxXwCLxiixG1c.ttf
673 ms
pqisLQoeO9YTDCNnlQ9bf6CWcynf_cDxXwCLxiixG1c.ttf
718 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
718 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
719 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
721 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
721 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
721 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
719 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
721 ms
ETmonarch_2.ttf
923 ms
ETmodules_v2_4.ttf
948 ms
c.php
531 ms
r.php
654 ms
analytics.js
545 ms
overlay.png
419 ms
a.php
217 ms
linkid.js
11 ms
collect
13 ms
collect
92 ms
dyne.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
dyne.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
dyne.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dyne.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 Dyne.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.
dyne.org
Open Graph data is detected on the main page of Dyne. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: