Tools & Wizards About Us
runstrong.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

runstrong.com

Runstrong: An independent interactive agency based in Los Angeles, California

Page Load Speed

1.4 sec in total

First Response

162 ms

Resources Loaded

919 ms

Page Rendered

270 ms

runstrong.com screenshot

About Website

Click here to check amazing Runstrong content. Otherwise, check out these important facts you probably never knew about runstrong.com

Runstrong is an independent interactive agency based in Los Angeles, California. We design and build creative, memorable experiences backed by solid technology.

Visit runstrong.com

Key Findings

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

Performance Metrics

runstrong.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

runstrong.com

162 ms

reset.css

71 ms

universal.css

137 ms

xqi3oqw.js

185 ms

jquery.min.js

217 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 61% of them (22 requests) were addressed to the original Runstrong.com, 31% (11 requests) were made to Use.typekit.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (567 ms) belongs to the original domain Runstrong.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.3 kB (1%)

Content Size

2.8 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Runstrong.com 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. 35% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 11.4 kB

  • Original 14.9 kB
  • After minification 13.8 kB
  • After compression 3.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 11.4 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.7 MB
  • After minification 2.7 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. Runstrong images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 6.4 kB

  • Original 68.3 kB
  • After minification 68.3 kB
  • After compression 61.9 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

-32%

Potential reduce by 1.5 kB

  • Original 4.9 kB
  • After minification 4.6 kB
  • After compression 3.3 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. Runstrong.com needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 32% of the original size.

Requests Breakdown

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

Requests Now

25

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runstrong. 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

runstrong.com

runstrong.com

162 ms

reset.css

reset.css

71 ms

universal.css

universal.css

137 ms

xqi3oqw.js

xqi3oqw.js

185 ms

jquery.min.js

jquery.min.js

217 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

145 ms

jquery.color-2.1.0.js

jquery.color-2.1.0.js

145 ms

jquery.cycle.all.js

jquery.cycle.all.js

146 ms

header_bg.png

header_bg.png

212 ms

rs_logo.png

rs_logo.png

211 ms

clearcubes.png

clearcubes.png

211 ms

home_carunners_glow.png

home_carunners_glow.png

212 ms

home_hero_carunners.png

home_hero_carunners.png

567 ms

home_roxx_glow.png

home_roxx_glow.png

212 ms

home_hero_roxx.png

home_hero_roxx.png

542 ms

home_ronaldo_glow.png

home_ronaldo_glow.png

212 ms

home_hero_ronaldo.png

home_hero_ronaldo.png

495 ms

interior.jpg

interior.jpg

239 ms

mesh.png

mesh.png

225 ms

ga.js

ga.js

171 ms

icon_gp.png

icon_gp.png

79 ms

icon_li.png

icon_li.png

80 ms

icon_fb.png

icon_fb.png

105 ms

icon_tw.png

icon_tw.png

140 ms

d

d

86 ms

d

d

107 ms

d

d

67 ms

d

d

170 ms

d

d

193 ms

d

d

98 ms

d

d

112 ms

d

d

126 ms

d

d

253 ms

d

d

183 ms

__utm.gif

__utm.gif

16 ms

p.gif

p.gif

20 ms

Accessibility Review

runstrong.com accessibility score

79

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Links do not have a discernible name

Best Practices

runstrong.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

runstrong.com SEO score

89

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runstrong.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 Runstrong.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

runstrong.com

Open Graph data is detected on the main page of Runstrong. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: