Tools & Wizards About Us
runningco.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

runningco.com

South Jersey Running Company

Page Load Speed

1.3 sec in total

First Response

127 ms

Resources Loaded

997 ms

Page Rendered

169 ms

runningco.com screenshot

About Website

Welcome to runningco.com homepage info - get ready to check Running Co best content right away, or after learning these important things about runningco.com

The South Jersey Running Co. is an independent and locally owned specialty running company!

Visit runningco.com

Key Findings

We analyzed Runningco.com page load time and found that the first response time was 127 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

runningco.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

runningco.com

127 ms

runningco.com

186 ms

js

84 ms

spectrum.css

39 ms

bootstrap.css

106 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 71% of them (53 requests) were addressed to the original Runningco.com, 11% (8 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Cdn.userway.org. The less responsive or slowest element that took the longest time to load (433 ms) belongs to the original domain Runningco.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.3 kB (11%)

Content Size

223.1 kB

After Optimization

197.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Runningco.com main page is 223.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 187.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 24.7 kB

  • Original 32.8 kB
  • After minification 30.1 kB
  • After compression 8.0 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.7 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.2 kB
  • After minification 3.2 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. Running Co images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 541 B

  • Original 187.1 kB
  • After minification 187.1 kB
  • After compression 186.6 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.

Requests Breakdown

Number of requests can be reduced by 52 (83%)

Requests Now

63

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

runningco.com

runningco.com

127 ms

runningco.com

runningco.com

186 ms

js

js

84 ms

spectrum.css

spectrum.css

39 ms

bootstrap.css

bootstrap.css

106 ms

themify-icons.css

themify-icons.css

135 ms

flexslider.css

flexslider.css

159 ms

theme.css

theme.css

185 ms

custom.css

custom.css

156 ms

runfree.css

runfree.css

153 ms

modal.css

modal.css

155 ms

font-awesome.min.css

font-awesome.min.css

170 ms

tooltips.css

tooltips.css

195 ms

runfreefont.css

runfreefont.css

192 ms

branding.css

branding.css

195 ms

jquery.min.js

jquery.min.js

101 ms

home.css

home.css

233 ms

platform.js

platform.js

109 ms

widget.js

widget.js

176 ms

bootstrap.min.js

bootstrap.min.js

99 ms

flexslider.min.js

flexslider.min.js

303 ms

masonry.min.js

masonry.min.js

304 ms

smooth-scroll.min.js

smooth-scroll.min.js

304 ms

moment.min.js

moment.min.js

98 ms

spectrum.js

spectrum.js

305 ms

css

css

99 ms

products.js

products.js

304 ms

category.js

category.js

303 ms

brand.js

brand.js

312 ms

discounts.js

discounts.js

312 ms

orders.js

orders.js

312 ms

taxes.js

taxes.js

312 ms

states.js

states.js

311 ms

country.js

country.js

311 ms

homepage.js

homepage.js

356 ms

customers.js

customers.js

355 ms

site.js

site.js

357 ms

user.js

user.js

354 ms

address.js

address.js

356 ms

contents.js

contents.js

355 ms

socials.js

socials.js

431 ms

merchant.js

merchant.js

432 ms

store.js

store.js

431 ms

settings.js

settings.js

433 ms

platform.js

platform.js

96 ms

context.js

context.js

432 ms

growler.js

growler.js

405 ms

modal.js

modal.js

332 ms

service.js

service.js

310 ms

cart.js

cart.js

290 ms

store.js

store.js

287 ms

scripts.js

scripts.js

289 ms

fbevents.js

fbevents.js

146 ms

blueshift.js

blueshift.js

146 ms

logo.png

logo.png

296 ms

85_207429_1707175452368.png

85_207429_1707175452368.png

297 ms

85_207429_1687184121530.jpeg

85_207429_1687184121530.jpeg

379 ms

85_207429_1691591547851.jpg

85_207429_1691591547851.jpg

379 ms

85_207429_1691591670439.JPG

85_207429_1691591670439.JPG

379 ms

85_207429_1691679585895.jpg

85_207429_1691679585895.jpg

304 ms

85_207429_1691591926879.jpg

85_207429_1691591926879.jpg

339 ms

proud.webp

proud.webp

243 ms

icomoon.ttf

icomoon.ttf

303 ms

widget_app_base_1725874918757.js

widget_app_base_1725874918757.js

72 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3iQ.woff

80 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3iQ.woff

81 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3iQ.woff

135 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3iQ.woff

143 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3iQ.woff

160 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

160 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

160 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

159 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

optin

optin

83 ms

googlelogo_color_150x54dp.png

googlelogo_color_150x54dp.png

7 ms

Accessibility Review

runningco.com accessibility score

96

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

Best Practices

runningco.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

High

Page has valid source maps

SEO Factors

runningco.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Runningco.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 Runningco.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

runningco.com

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