3.3 sec in total
350 ms
2.3 sec
692 ms
Click here to check amazing Runtastic content for United States. Otherwise, check out these important facts you probably never knew about runtastic.com
Track your runs, bodyweight training sessions, and other fitness & sports activities with adidas Runtastic apps. Stay motivated with your friends, set new goals, start a training plan, and live a heal...
Visit runtastic.comWe analyzed Runtastic.com page load time and found that the first response time was 350 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
runtastic.com performance score
name
value
score
weighting
Value9.8 s
0/100
10%
Value21.6 s
0/100
25%
Value10.7 s
7/100
10%
Value1,350 ms
17/100
30%
Value0.074
95/100
15%
Value21.0 s
1/100
10%
350 ms
828 ms
60 ms
452 ms
99 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Runtastic.com, 55% (17 requests) were made to D2d69lvc7tiwu6.cloudfront.net and 26% (8 requests) were made to D1ki59phkeobjj.cloudfront.net. The less responsive or slowest element that took the longest time to load (828 ms) belongs to the original domain Runtastic.com.
Page size can be reduced by 1.4 MB (44%)
3.2 MB
1.8 MB
In fact, the total size of Runtastic.com 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. 45% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 38.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 38.5 kB or 73% of the original size.
Potential reduce by 16.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. Runtastic images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 76% of the original size.
Potential reduce by 86.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. Runtastic.com needs all CSS files to be minified and compressed as it can save up to 86.9 kB or 81% of the original size.
Number of requests can be reduced by 6 (21%)
29
23
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runtastic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
runtastic.com
350 ms
www.runtastic.com
828 ms
bugsnag-2.min.js
60 ms
lp-8bb9b28841f9642c5bf21f7c37314cca.css
452 ms
vendor-05b12ba5bfaf4db8e4b176359beb9f7d.js
99 ms
vendor-287f008181e64f212632290979044cb1.js
81 ms
ember-cli-runtastic-landingpage-0f4433fff823fd269142812a652b448a.js
84 ms
runtastic-logo-62ccb93b58fe91f5faaa7713bf3987ba.png
15 ms
vendor-1cd0b63e5715451c9a8b18f1641f0d39.css
6 ms
ember-cli-runtastic-landingpage-031d837984d65c8de3b3576e9fb930a0.css
11 ms
key-visual-c9da6ef54027329fc14ed83a7383d2f8.jpg
225 ms
step_1-b2ca819629f8fa0ed0a5d6d6ce178400.jpg
220 ms
step_2-00ac654adf06702107c5d6de714fc1ac.jpg
243 ms
step_3-45350fa50692ca185629343a30d322e7.jpg
242 ms
app-info-5740cf1936279ae63f30801ef6757888.jpg
503 ms
runtastic-c18b608b00aab945bf02ad3ca9372846.png
503 ms
bttn_apple_appstore_official-80cdcfe5a0c1b7e975caaf540c92e2d4.png
241 ms
bttn_google_playstore_official-3db92bdee59c481cf5c9c3e8d0efaec0.png
501 ms
bttn_windowsphone_appstore_official-54ebf462f49a7751ca7c4a95cb82d93c.png
503 ms
apps-d91f409404268adba8979b9ececee47e.png
515 ms
hardware-info-dcb8419af26297012fad0ee7aeb6a765.jpg
514 ms
hardware-d7f882f89edd64a9944ba9d708472d2c.png
512 ms
gold-info-08f92a6658f2ddca323b332dac49ae49.jpg
513 ms
website-d6a703fe0aa4d277bc5423ae8002e199.png
514 ms
homepage-sfdd119b3ba-65e7a2760ebfb5420ecbf46e4b291e6f.png
517 ms
translations-en-13d1f5691bccc90401d30493cd062a07.js
61 ms
analytics.js
369 ms
sdk.js
444 ms
runtastic-logo-94c0762613338e4cc487a9110dfcf504.png
204 ms
footer_sprite-7b530246e3847f214b9e42b6be4fd044.png
34 ms
collect
12 ms
runtastic.com 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.
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
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
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
runtastic.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
runtastic.com 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runtastic.com 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 Runtastic.com 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.
runtastic.com
Open Graph description is not detected on the main page of Runtastic. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: