Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

dna.run

DNA athletics - Dynamic New Athletics for a digital world

Page Load Speed

14.7 sec in total

First Response

3.9 sec

Resources Loaded

10.4 sec

Page Rendered

449 ms

About Website

Welcome to dna.run homepage info - get ready to check DNA best content right away, or after learning these important things about dna.run

DNA athletics is an unpredictable two hour winner takes all team sport using tactics & competitiveness to be played by anywhere anytime.

Visit dna.run

Key Findings

We analyzed Dna.run page load time and found that the first response time was 3.9 sec and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

dna.run performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value17.8 s

0/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,940 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.836

4/100

15%

TTI (Time to Interactive)

Value25.1 s

0/100

10%

Network Requests Diagram

dna.run

3896 ms

cookie-law-info-public.css

355 ms

cookie-law-info-gdpr.css

319 ms

addtoany.min.css

80 ms

page.js

53 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 22% of them (27 requests) were addressed to the original Dna.run, 31% (38 requests) were made to Fonts.gstatic.com and 20% (24 requests) were made to Static.cdninstagram.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Dna.run.

Page Optimization Overview & Recommendations

Page size can be reduced by 417.5 kB (19%)

Content Size

2.2 MB

After Optimization

1.8 MB

In fact, the total size of Dna.run main page is 2.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. Only a small number of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 163.7 kB

  • Original 198.2 kB
  • After minification 195.4 kB
  • After compression 34.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 163.7 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 11.3 kB

  • Original 1.4 MB
  • After minification 1.4 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. DNA images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 237.5 kB

  • Original 550.9 kB
  • After minification 550.9 kB
  • After compression 313.4 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 237.5 kB or 43% of the original size.

CSS Optimization

-6%

Potential reduce by 5.1 kB

  • Original 87.0 kB
  • After minification 87.0 kB
  • After compression 81.9 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. Dna.run has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 45 (60%)

Requests Now

75

After Optimization

30

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DNA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

dna.run accessibility score

73

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dna.run 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

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

dna.run SEO score

90

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

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

High

Tap targets are not sized appropriately

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 Dna.run 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 Dna.run 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 DNA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: