Tools & Wizards About Us
rnnr.us screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

rnnr.us

Page Load Speed

5.7 sec in total

First Response

1.6 sec

Resources Loaded

3.7 sec

Page Rendered

422 ms

rnnr.us screenshot

About Website

Click here to check amazing Rnnr content. Otherwise, check out these important facts you probably never knew about rnnr.us

The heath and fitness blog by Chris Abraham focusing mainly on my seven obsessions: running, rowing, erging, biking, cooking, TRX straps, and kettlebells.

Visit rnnr.us

Key Findings

We analyzed Rnnr.us page load time and found that the first response time was 1.6 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

rnnr.us performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

87/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value4,850 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.056

98/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

rnnr.us

1602 ms

pEPtGrbhC2mNZCFBg3id_aNkW64.js

242 ms

header-bb4927ca.min.js

318 ms

adsbygoogle.js

86 ms

widget_2.js

575 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 15% of them (9 requests) were addressed to the original Rnnr.us, 10% (6 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Aax-us-east.amazon-adsystem.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Rnnr.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 569.2 kB (60%)

Content Size

947.7 kB

After Optimization

378.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Rnnr.us main page is 947.7 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. 55% of websites need less resources to load. Javascripts take 541.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 272.0 kB

  • Original 339.3 kB
  • After minification 339.3 kB
  • After compression 67.4 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 272.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 123 B

  • Original 66.5 kB
  • After minification 66.3 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. Rnnr images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 297.1 kB

  • Original 541.9 kB
  • After minification 541.9 kB
  • After compression 244.8 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 297.1 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (67%)

Requests Now

51

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rnnr.us

rnnr.us

1602 ms

pEPtGrbhC2mNZCFBg3id_aNkW64.js

pEPtGrbhC2mNZCFBg3id_aNkW64.js

242 ms

header-bb4927ca.min.js

header-bb4927ca.min.js

318 ms

adsbygoogle.js

adsbygoogle.js

86 ms

widget_2.js

widget_2.js

575 ms

onejs

onejs

60 ms

q

q

98 ms

121317X1581636.skimlinks.js

121317X1581636.skimlinks.js

111 ms

footer-298e0532.min.js

footer-298e0532.min.js

72 ms

api.js

api.js

89 ms

footer-87811686.min.js

footer-87811686.min.js

133 ms

widgets.js

widgets.js

61 ms

analytics.js

analytics.js

64 ms

collect

collect

127 ms

mem8YaGs126MiZpBA-UFVZ0d.woff

mem8YaGs126MiZpBA-UFVZ0d.woff

165 ms

mem5YaGs126MiZpBA-UNirkOUuhv.woff

mem5YaGs126MiZpBA-UNirkOUuhv.woff

174 ms

mem5YaGs126MiZpBA-UN7rgOUuhv.woff

mem5YaGs126MiZpBA-UN7rgOUuhv.woff

228 ms

mem5YaGs126MiZpBA-UN8rsOUuhv.woff

mem5YaGs126MiZpBA-UN8rsOUuhv.woff

245 ms

css

css

45 ms

rnnr_logo500x101.jpg

rnnr_logo500x101.jpg

124 ms

rnnrus

rnnrus

418 ms

logo-strava.png

logo-strava.png

355 ms

menu-icon-large.png

menu-icon-large.png

325 ms

stage-7-photography-bVcoKBD2mcs-unsplash-1-scaled-765x400.jpg

stage-7-photography-bVcoKBD2mcs-unsplash-1-scaled-765x400.jpg

354 ms

integrator.js

integrator.js

332 ms

show_ads_impl.js

show_ads_impl.js

147 ms

zrt_lookup.html

zrt_lookup.html

317 ms

css

css

243 ms

cup-border.png

cup-border.png

219 ms

ga-audiences

ga-audiences

185 ms

ads

ads

465 ms

osd.js

osd.js

278 ms

logo-strava-echelon.png

logo-strava-echelon.png

35 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

445 ms

minified_logic.js

minified_logic.js

738 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xw.ttf

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xw.ttf

26 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf

27 ms

getad

getad

567 ms

getad

getad

572 ms

px.gif

px.gif

550 ms

643 ms

vglnk.js

vglnk.js

644 ms

recaptcha__en.js

recaptcha__en.js

543 ms

px.gif

px.gif

523 ms

widget_iframe.6a44a9d26983bbb5b04ae399f9e496fe.html

widget_iframe.6a44a9d26983bbb5b04ae399f9e496fe.html

263 ms

ads

ads

562 ms

settings

settings

255 ms

q

q

136 ms

123 ms

ir

ir

204 ms

100 ms

V3czWBCcTgLGUiYckFiRvtMyOKFmuZGb

V3czWBCcTgLGUiYckFiRvtMyOKFmuZGb

143 ms

V3czWBCcTgLGUiYckFiRvtMyOKFmuZGb

V3czWBCcTgLGUiYckFiRvtMyOKFmuZGb

399 ms

36 ms

pixel.gif

pixel.gif

24 ms

pixel.gif

pixel.gif

28 ms

button.9a57558490548c2dde66afe19af6c010.js

button.9a57558490548c2dde66afe19af6c010.js

28 ms

tweet_button.6a44a9d26983bbb5b04ae399f9e496fe.en.html

tweet_button.6a44a9d26983bbb5b04ae399f9e496fe.en.html

125 ms

transparent.png

transparent.png

213 ms

osd_listener.js

osd_listener.js

149 ms

icon.png

icon.png

148 ms

Accessibility Review

rnnr.us accessibility score

84

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

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

Form elements do not have associated labels

Best Practices

rnnr.us 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

rnnr.us SEO score

64

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Rnnr.us 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 Rnnr.us 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

rnnr.us

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