14.7 sec in total
3.9 sec
10.4 sec
449 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 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.
dna.run performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value17.8 s
0/100
25%
Value17.8 s
0/100
10%
Value3,940 ms
1/100
30%
Value0.836
4/100
15%
Value25.1 s
0/100
10%
3896 ms
355 ms
319 ms
80 ms
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 size can be reduced by 417.5 kB (19%)
2.2 MB
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.
Potential reduce by 163.7 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.
Potential reduce by 11.3 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 237.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. 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.
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 45 (60%)
75
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.
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
jquery.min.js
235 ms
jquery-migrate.min.js
232 ms
addtoany.min.js
160 ms
cookie-law-info-public.js
316 ms
js
69 ms
embed.js
85 ms
cookie-law-info-table.css
176 ms
scripts.min.js
802 ms
jquery.fitvids.js
175 ms
jquery.mobile.js
364 ms
common.js
300 ms
-ByAzFB_ryQ
141 ms
ktZL8zfCkrw
466 ms
dna-header-bg.jpg
157 ms
dna-logo-header.png
161 ms
clash-of-the-clubs-iii-portugal-dna.jpg
919 ms
clash-of-the-clubs-iii-portugal-dna-mob.jpg
817 ms
dna-pombal-full-event-details.jpg
465 ms
dna-divider.png
464 ms
grassroots-development.jpg
575 ms
dna-top-clubs-competition.jpg
613 ms
dynamic-new-athletics-showcase-events.jpg
602 ms
sparta-atletik-win-clash-of-clubs-iii.jpg
1278 ms
dna-footer-background.jpg
587 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ0q2cjnj8Q.woff
30 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ0q2cjnj8g.ttf
35 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy22cjnj8Q.woff
85 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy22cjnj8g.ttf
33 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ3O2cjnj8Q.woff
62 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ3O2cjnj8g.ttf
34 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ5-xcjnj8Q.woff
35 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ5-xcjnj8g.ttf
45 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ62xcjnj8Q.woff
114 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ62xcjnj8g.ttf
46 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ_Oxcjnj8Q.woff
114 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZ_Oxcjnj8g.ttf
46 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy2xcjnj8Q.woff
107 ms
2-c79JNi2YuVOUcOarRPgnNGooxCZy2xcjnj8g.ttf
46 ms
modules.woff
617 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
51 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
51 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
60 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
60 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
67 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
67 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
68 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
68 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
78 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
79 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
79 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
80 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
80 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
81 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff
81 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
88 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
88 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
89 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff
88 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
89 ms
www-player.css
29 ms
www-embed-player.js
48 ms
base.js
70 ms
id
270 ms
ad_status.js
266 ms
Create
244 ms
qoe
222 ms
Uo_dhVY9o5gWds10f-QE3r7w2DYPAY7ZjhqsbDUx1y0.js
220 ms
embed.js
178 ms
qoe
80 ms
sm.25.html
47 ms
eso.m4v434v2.js
52 ms
469 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
11 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
10 ms
-ByAzFB_ryQ
267 ms
ktZL8zfCkrw
139 ms
ad_status.js
130 ms
Uo_dhVY9o5gWds10f-QE3r7w2DYPAY7ZjhqsbDUx1y0.js
107 ms
embed.js
103 ms
id
55 ms
Create
116 ms
Create
291 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
14 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
15 ms
_VAc-w5pLLP.css
174 ms
biWcl-2AazR.css
182 ms
er1zco9CbrP.css
279 ms
7TXvrmQm8c5.js
284 ms
GenerateIT
80 ms
GenerateIT
81 ms
style.min.css
163 ms
448737179_789832573278185_9062939875731817267_n.jpg
48 ms
289402805_2178656852315089_4623118884095947049_n.jpg
85 ms
460976401_539926825087375_2434633372924884816_n.jpg
144 ms
461694342_1610624126545252_5558007407873188858_n.jpg
106 ms
461009954_1189469358933763_7012220783034390909_n.jpg
149 ms
Kq06toTJMFl.png
25 ms
szSrDf3yAfN.js
10 ms
SxSCS_2EM_D.js
6 ms
i2yEVh-cs27.js
10 ms
UDFCsXtDquD.js
18 ms
o4gjb2QTWOc.js
18 ms
YOdxXwd2SPx.js
17 ms
lNInKxOqejp.js
19 ms
db_RQLQYjko.js
34 ms
XFEPK2Ku-0b.js
42 ms
GJ_1fTPMh38.js
34 ms
cBmLqZhej__.js
32 ms
gAw_9LUyzWL.js
34 ms
aRS1ewpYUAP.js
42 ms
GhZEvSLVF3e.js
42 ms
ylyTmy7Tpht.js
50 ms
-7SoqkOoiBI.js
53 ms
R8ZTLxqI2uK.js
52 ms
O_3se-VPkdK.js
53 ms
8jiWhI0V9t8.js
54 ms
style.min.css
199 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.
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
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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: