12.7 sec in total
5 sec
7.2 sec
542 ms
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.runWe analyzed Dna.run page load time and found that the first response time was 5 sec and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dna.run performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value8.4 s
2/100
25%
Value20.5 s
0/100
10%
Value2,010 ms
7/100
30%
Value0.16
73/100
15%
Value25.2 s
0/100
10%
4999 ms
248 ms
328 ms
82 ms
52 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 41% of them (36 requests) were addressed to the original Dna.run, 41% (36 requests) were made to Fonts.gstatic.com and 7% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Dna.run.
Page size can be reduced by 214.9 kB (8%)
2.8 MB
2.5 MB
In fact, the total size of Dna.run main page is 2.8 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. 85% 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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 172.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 172.9 kB or 82% of the original size.
Potential reduce by 20.4 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. DNA images are well optimized though.
Potential reduce by 16.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 5.1 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.
Number of requests can be reduced by 21 (43%)
49
28
The browser has sent 49 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 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
dna.run
4999 ms
cookie-law-info-public.css
248 ms
cookie-law-info-gdpr.css
328 ms
addtoany.min.css
82 ms
page.js
52 ms
jquery.min.js
328 ms
jquery-migrate.min.js
162 ms
addtoany.min.js
174 ms
cookie-law-info-public.js
321 ms
js
89 ms
cookie-law-info-table.css
244 ms
scripts.min.js
507 ms
jquery.fitvids.js
248 ms
jquery.mobile.js
254 ms
common.js
325 ms
eso.Ep5bSEmr.js
19 ms
9Y6wP8gi05w
230 ms
dna-header-bg.jpg
277 ms
dna-logo-header.png
276 ms
dna-u20-clubs-rome.png
636 ms
rome-congratulations-2.png
737 ms
rome-rewatch-300x199.png
364 ms
european-athletics-youtube-300x43.jpg
275 ms
rome-results.jpg
340 ms
full-event-details.jpg
637 ms
dna-rome-clash-of-the-clubs-ii.jpg
1136 ms
viktorie-janska-1-1.jpg
779 ms
jacopo-capasso-1-1.jpg
819 ms
hannah-clark.jpg
943 ms
marion-bosle-1-1.jpg
819 ms
katie-doherty-1-1.jpg
1050 ms
joel-frederik-von-de-ahe.jpg
1110 ms
moritz-muhlpointer.jpg
1140 ms
dna-divider.png
943 ms
grassroots-development.jpg
1060 ms
dna-top-clubs-competition.jpg
1145 ms
dynamic-new-athletics-showcase-events.jpg
1287 ms
dna-footer-background.jpg
1224 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ0q2cjnj8Q.woff
23 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ0q2cjnj8g.ttf
135 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy22cjnj8Q.woff
138 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy22cjnj8g.ttf
136 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ3O2cjnj8Q.woff
138 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ3O2cjnj8g.ttf
137 ms
font
167 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ5-xcjnj8g.ttf
166 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ62xcjnj8Q.woff
167 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ62xcjnj8g.ttf
166 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ_Oxcjnj8Q.woff
167 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ_Oxcjnj8g.ttf
167 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy2xcjnj8Q.woff
214 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy2xcjnj8g.ttf
214 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
167 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
168 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
168 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
169 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
169 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
170 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
170 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
170 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
171 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
174 ms
modules.woff
1088 ms
font
172 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
171 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
170 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
172 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff
172 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
174 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
207 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
207 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff
209 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
208 ms
sm.25.html
96 ms
icons.37.svg.js
99 ms
9Y6wP8gi05w
149 ms
www-player.css
6 ms
www-embed-player.js
27 ms
base.js
61 ms
ad_status.js
174 ms
ToQOEX5gn9COOYOZ9__C9da2xlIrCzMPflL2asQoGhw.js
121 ms
embed.js
43 ms
id
31 ms
KFOmCnqEu92Fr1Mu4mxM.woff
30 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
31 ms
Create
129 ms
GenerateIT
15 ms
style.min.css
168 ms
dna.run 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
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.
dna.run 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
dna.run 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
Tap targets are not sized appropriately
EN
EN
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.
dna.run
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: