Access shop.on-running.com.

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value9.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

shop.on-running.com

42 ms

client

70 ms

consent-newrelic-snippet-csr.js

26 ms

global-58a2ca4efae5.css

40 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 11% of them (1 request) were addressed to the original Shop.on-running.com, 67% (6 requests) were made to On.com and 11% (1 request) were made to Accounts.google.com. The less responsive or slowest element that took the longest time to load (101 ms) relates to the external source On.com.

Content Size

12.7 kB

After Optimization

3.2 kB

In fact, the total size of Shop.on-running.com main page is 12.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. Only 5% of websites need less resources to load. HTML takes 12.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 9.5 kB

Original 12.7 kB
After minification 12.7 kB
After compression 3.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 9.5 kB or 75% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-hidden="true"] elements contain focusable descendents

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shop.on-running.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Shop.on-running.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

Open Graph description is not detected on the main page of Shop On Running. 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: