Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

runnersworld.de

Home | RUNNER'S WORLD

Page Load Speed

4.6 sec in total

First Response

201 ms

Resources Loaded

3 sec

Page Rendered

1.5 sec

runnersworld.de screenshot

About Website

Welcome to runnersworld.de homepage info - get ready to check RUNNER S WORLD best content for Germany right away, or after learning these important things about runnersworld.de

RUNNER'S WORLD versorgt dich mit allen Themen rund ums Laufen und Joggen. » Trainingspläne, Lauf- und Ernährungstipps, Events und vieles mehr.

Visit runnersworld.de

Key Findings

We analyzed Runnersworld.de page load time and found that the first response time was 201 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

runnersworld.de performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value3,900 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

runnersworld.de

201 ms

www.runnersworld.de

614 ms

ac23af9e270db93e.css

214 ms

aa179c37317084f0.css

294 ms

polyfills-c67a75d1b6f99dc8.js

458 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 52% of them (65 requests) were addressed to the original Runnersworld.de, 47% (58 requests) were made to Img1.runnersworld.de and 1% (1 request) were made to . The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Img1.runnersworld.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 701.5 kB (30%)

Content Size

2.3 MB

After Optimization

1.6 MB

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

HTML Optimization

-88%

Potential reduce by 688.1 kB

  • Original 780.3 kB
  • After minification 780.1 kB
  • After compression 92.2 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 688.1 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 13.4 kB

  • Original 1.6 MB
  • After minification 1.5 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. RUNNER S WORLD images are well optimized though.

Requests Breakdown

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

Requests Now

121

After Optimization

68

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

Accessibility Review

runnersworld.de accessibility score

95

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.

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

runnersworld.de 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

Missing source maps for large first-party JavaScript

SEO Factors

runnersworld.de 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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runnersworld.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Runnersworld.de 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

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