Report Summary

  • 83

    Performance

    Renders faster than
    87% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

dyne.org

Digital Community and Free Software Foundry

Page Load Speed

2.3 sec in total

First Response

117 ms

Resources Loaded

1.1 sec

Page Rendered

1.1 sec

dyne.org screenshot

About Website

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

🚀 Empowering artists, creatives and citizens for more than 20 years.

Visit dyne.org

Key Findings

We analyzed Dyne.org page load time and found that the first response time was 117 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

dyne.org performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

dyne.org

117 ms

dyne.org

39 ms

99mq.387d9c76.css

13 ms

donate.39ffb122.css

23 ms

colors.5b5ebce6.css

23 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 82% of them (31 requests) were addressed to the original Dyne.org, 5% (2 requests) were made to Cdn.jsdelivr.net and 3% (1 request) were made to Zenroom.org. The less responsive or slowest element that took the longest time to load (940 ms) relates to the external source Openresearch.amsterdam.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (21%)

Content Size

7.4 MB

After Optimization

5.9 MB

In fact, the total size of Dyne.org main page is 7.4 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. 30% of websites need less resources to load. Images take 7.1 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 206.0 kB

  • Original 293.8 kB
  • After minification 283.9 kB
  • After compression 87.8 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 206.0 kB or 70% of the original size.

Image Optimization

-19%

Potential reduce by 1.3 MB

  • Original 7.1 MB
  • After minification 5.8 MB

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, Dyne needs image optimization as it can save up to 1.3 MB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 3 (13%)

Requests Now

24

After Optimization

21

The browser has sent 24 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 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

dyne.org accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

dyne.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

dyne.org SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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 it matches the claimed language. 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.

Social Sharing Optimization

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: