Tools & Wizards About Us
blog.runtastic.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

blog.runtastic.com

adidas Runtastic Blog: running, fitness & health

Page Load Speed

4.1 sec in total

First Response

249 ms

Resources Loaded

2.8 sec

Page Rendered

1.1 sec

blog.runtastic.com screenshot

About Website

Click here to check amazing Blog Runtastic content for United States. Otherwise, check out these important facts you probably never knew about blog.runtastic.com

Everything you need to know about running, strength & nutrition. Boost your health and fitness level with tips from experts.

Visit blog.runtastic.com

Key Findings

We analyzed Blog.runtastic.com page load time and found that the first response time was 249 ms and then it took 3.9 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

blog.runtastic.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.9

3/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

blog.runtastic.com

249 ms

blog.runtastic.com

433 ms

www.runtastic.com

925 ms

a80fe192528c813b.css

216 ms

29a4fe12012567be.css

321 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Blog.runtastic.com, 58% (28 requests) were made to Runtastic.com and 38% (18 requests) were made to Res.cloudinary.com. The less responsive or slowest element that took the longest time to load (925 ms) relates to the external source Runtastic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.6 kB (10%)

Content Size

2.3 MB

After Optimization

2.0 MB

  • HTML
  • Images

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

HTML Optimization

-82%

Potential reduce by 223.9 kB

  • Original 274.6 kB
  • After minification 274.6 kB
  • After compression 50.7 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 223.9 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 10.7 kB

  • Original 2.0 MB
  • After minification 2.0 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. Blog Runtastic images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 24 (60%)

Requests Now

40

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

blog.runtastic.com

blog.runtastic.com

249 ms

blog.runtastic.com

blog.runtastic.com

433 ms

www.runtastic.com

www.runtastic.com

925 ms

a80fe192528c813b.css

a80fe192528c813b.css

216 ms

29a4fe12012567be.css

29a4fe12012567be.css

321 ms

6ef33578c76bd321.css

6ef33578c76bd321.css

435 ms

07e28f267100c3a0.css

07e28f267100c3a0.css

322 ms

1f99ac48667a5b38.css

1f99ac48667a5b38.css

325 ms

1dd3208c-ac90d6887fc5a4ba.js

1dd3208c-ac90d6887fc5a4ba.js

541 ms

286-9f9d45af5ecf4185.js

286-9f9d45af5ecf4185.js

332 ms

main-app-7cd6b0625fd43ccd.js

main-app-7cd6b0625fd43ccd.js

431 ms

layout-e13ce1035426af82.js

layout-e13ce1035426af82.js

431 ms

658-08cb4ce6c5f12580.js

658-08cb4ce6c5f12580.js

443 ms

980-e0a99b11ef38efc4.js

980-e0a99b11ef38efc4.js

556 ms

848-734ad95e36cda3c5.js

848-734ad95e36cda3c5.js

549 ms

layout-ba564c163645ebf9.js

layout-ba564c163645ebf9.js

549 ms

50e4e0f8-98aaa51840283d9b.js

50e4e0f8-98aaa51840283d9b.js

550 ms

73-ec6cea065a8943fb.js

73-ec6cea065a8943fb.js

874 ms

page-4f9f8056e08ca35c.js

page-4f9f8056e08ca35c.js

653 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

756 ms

webpack-dea2b999a17fd094.js

webpack-dea2b999a17fd094.js

652 ms

xjcqpvj52ftepppgd8rg.png

xjcqpvj52ftepppgd8rg.png

149 ms

menu-icon.5394f0cd.svg

menu-icon.5394f0cd.svg

116 ms

image

image

117 ms

profile-icon.b7909526.svg

profile-icon.b7909526.svg

110 ms

image

image

175 ms

cs8xeoozkj8qdm6pzmiz.jpeg

cs8xeoozkj8qdm6pzmiz.jpeg

90 ms

rocpquzvsecvne1wyn9n.png

rocpquzvsecvne1wyn9n.png

83 ms

d0zzzmqv0n2lq8y72iud.png

d0zzzmqv0n2lq8y72iud.png

84 ms

nmsz1ztuovsvbxypjtni.jpeg

nmsz1ztuovsvbxypjtni.jpeg

76 ms

upsysvjqqehperxqygf9.png

upsysvjqqehperxqygf9.png

87 ms

pnmsofxtovr21drskgao.jpeg

pnmsofxtovr21drskgao.jpeg

115 ms

w6nvrdijxj4qsbvsfklx.jpeg

w6nvrdijxj4qsbvsfklx.jpeg

129 ms

etung5udwcfv7jczv5iw.jpeg

etung5udwcfv7jczv5iw.jpeg

121 ms

icixmd8mxbs961tfqimk.jpeg

icixmd8mxbs961tfqimk.jpeg

123 ms

akub2mfjn0rpc2ado4xd.jpeg

akub2mfjn0rpc2ado4xd.jpeg

233 ms

z4tpxuyh82pmifq0ozuf.jpeg

z4tpxuyh82pmifq0ozuf.jpeg

144 ms

u1m5fkiyxo2rl3xupclv.gif

u1m5fkiyxo2rl3xupclv.gif

155 ms

lg5bakbjywhnkviqznhp.png

lg5bakbjywhnkviqznhp.png

166 ms

ky8j4ummlz8m4qqhmsw9.jpeg

ky8j4ummlz8m4qqhmsw9.jpeg

257 ms

xjdyymet57zeo09aehs0.png

xjdyymet57zeo09aehs0.png

172 ms

tpmephbq7rei3qds9rud.png

tpmephbq7rei3qds9rud.png

247 ms

gwdqfkqqyywbbwrr5nvs.png

gwdqfkqqyywbbwrr5nvs.png

198 ms

adineuePROCondTT-Bold.20f79afd.ttf

adineuePROCondTT-Bold.20f79afd.ttf

234 ms

adi_neue_pro_bold.0d8881e8.ttf

adi_neue_pro_bold.0d8881e8.ttf

353 ms

adi_haus_din_regular.e8dd9aae.ttf

adi_haus_din_regular.e8dd9aae.ttf

406 ms

adi_haus_din_con_medium_italic.5ca2f4ce.ttf

adi_haus_din_con_medium_italic.5ca2f4ce.ttf

461 ms

adi_haus_din_bold.f3e8d555.ttf

adi_haus_din_bold.f3e8d555.ttf

416 ms

Accessibility Review

blog.runtastic.com accessibility score

94

Accessibility Issues

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

blog.runtastic.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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

SEO Factors

blog.runtastic.com SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

blog.runtastic.com

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