Tools & Wizards About Us

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

runpartner.com

RunPartner.com

Page Load Speed

748 ms in total

First Response

38 ms

Resources Loaded

622 ms

Page Rendered

88 ms

About Website

Welcome to runpartner.com homepage info - get ready to check Run Partner best content for United States right away, or after learning these important things about runpartner.com

RunPartner helps coaches provide training programs to athletes.

Visit runpartner.com

Key Findings

We analyzed Runpartner.com page load time and found that the first response time was 38 ms and then it took 710 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

runpartner.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value5.1 s

76/100

10%

Network Requests Diagram

runpartner.com

38 ms

runpartner.com

12 ms

rev_870.css.cgz

78 ms

prototype_170.js.jgz

107 ms

scriptaculous.js

28 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Runpartner.com, 72% (21 requests) were made to Static.runpartner.com and 10% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (228 ms) relates to the external source Static.runpartner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 187.8 kB (17%)

Content Size

1.1 MB

After Optimization

907.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Runpartner.com main page is 1.1 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. 15% of websites need less resources to load. Images take 621.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 15.7 kB

  • Original 20.3 kB
  • After minification 19.2 kB
  • After compression 4.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 15.7 kB or 77% of the original size.

Image Optimization

-26%

Potential reduce by 158.9 kB

  • Original 621.3 kB
  • After minification 462.5 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. Obviously, Run Partner needs image optimization as it can save up to 158.9 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 12.6 kB

  • Original 417.1 kB
  • After minification 416.8 kB
  • After compression 404.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.

CSS Optimization

-2%

Potential reduce by 637 B

  • Original 36.0 kB
  • After minification 36.0 kB
  • After compression 35.4 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. Runpartner.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (48%)

Requests Now

27

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

runpartner.com accessibility score

51

Accessibility Issues

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

Buttons do not have an accessible name

Low

No form fields have multiple labels

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

runpartner.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

runpartner.com SEO score

69

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runpartner.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 Runpartner.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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