Tools & Wizards About Us
runkeeper.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

runkeeper.com

Track your Run - ASICS Runkeeper Running Tracker App

Page Load Speed

45.7 sec in total

First Response

609 ms

Resources Loaded

16.4 sec

Page Rendered

28.7 sec

runkeeper.com screenshot

About Website

Visit runkeeper.com now to see the best up-to-date Runkeeper content for United States and also check out these interesting facts you probably never knew about runkeeper.com

Just like a real-life coach, the ASICS Runkeeper app will help you set your goals, train for them, and track your progress along the way.

Visit runkeeper.com

Key Findings

We analyzed Runkeeper.com page load time and found that the first response time was 609 ms and then it took 45.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

runkeeper.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value800 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

index

609 ms

ga.js

634 ms

2855482612.js

3338 ms

cookieconsent.min.css

2399 ms

cookieconsent.min.js

3176 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Runkeeper.com, 46% (19 requests) were made to Static-web.runkeeper.com and 7% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (5.7 sec) relates to the external source Stats.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (22%)

Content Size

5.7 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Runkeeper.com main page is 5.7 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. 55% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 24.2 kB

  • Original 34.9 kB
  • After minification 33.6 kB
  • After compression 10.6 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 24.2 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 47.1 kB

  • Original 3.8 MB
  • After minification 3.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. Runkeeper images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 721.7 kB

  • Original 991.2 kB
  • After minification 973.0 kB
  • After compression 269.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 721.7 kB or 73% of the original size.

CSS Optimization

-55%

Potential reduce by 474.9 kB

  • Original 862.0 kB
  • After minification 792.9 kB
  • After compression 387.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. Runkeeper.com needs all CSS files to be minified and compressed as it can save up to 474.9 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (44%)

Requests Now

36

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index

index

609 ms

ga.js

ga.js

634 ms

2855482612.js

2855482612.js

3338 ms

cookieconsent.min.css

cookieconsent.min.css

2399 ms

cookieconsent.min.js

cookieconsent.min.js

3176 ms

shared.header.min.js

shared.header.min.js

2402 ms

grunticon.loader.js

grunticon.loader.js

2545 ms

normalize.min.css

normalize.min.css

3175 ms

homepage.min.css

homepage.min.css

3175 ms

jquery.min.js

jquery.min.js

2397 ms

homepage.min.js

homepage.min.js

2497 ms

collect

collect

5737 ms

2ecc0c

2ecc0c

5047 ms

undefined

undefined

887 ms

analytics.js

analytics.js

4152 ms

fbevents.js

fbevents.js

4777 ms

localytics.min.js

localytics.min.js

4778 ms

header-bg.jpg

header-bg.jpg

2345 ms

Screens.png

Screens.png

3265 ms

community-reviewer-1.png

community-reviewer-1.png

2343 ms

community-reviewer-2.png

community-reviewer-2.png

2344 ms

community-reviewer-3.png

community-reviewer-3.png

3847 ms

track_workouts.png

track_workouts.png

5204 ms

set_goals.png

set_goals.png

5202 ms

follow_plan.png

follow_plan.png

5113 ms

stay_motivated.png

stay_motivated.png

5203 ms

see_progress.png

see_progress.png

5200 ms

make-it-fun-600x1230.png

make-it-fun-600x1230.png

5112 ms

press-review-bg.jpg

press-review-bg.jpg

5238 ms

ga-audiences

ga-audiences

5086 ms

hotjar-42341.js

hotjar-42341.js

3906 ms

625777927503265

625777927503265

354 ms

image.gif

image.gif

2764 ms

collect

collect

125 ms

ga-audiences

ga-audiences

813 ms

icons.data.svg.css

icons.data.svg.css

812 ms

2629 ms

image.gif

image.gif

2479 ms

modules-f524bccd859bfc7e394e1123f7f90405.js

modules-f524bccd859bfc7e394e1123f7f90405.js

2432 ms

rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html

rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html

2424 ms

icons.data.svg.css

icons.data.svg.css

1271 ms

Accessibility Review

runkeeper.com accessibility score

89

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

runkeeper.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

runkeeper.com SEO score

93

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

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 Runkeeper.com 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 Runkeeper.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.

Social Sharing Optimization

runkeeper.com

Open Graph description is not detected on the main page of Runkeeper. 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: