Access underarmour.eu. Change Shipping Location

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value22.4 s

0/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value2,160 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.598

11/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

852 ms

fonts.css

70 ms

normalize.css

77 ms

style.css

84 ms

utag.sync.js

58 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 45% of them (38 requests) were addressed to the original Underarmour.eu, 25% (21 requests) were made to Underarmour.scene7.com and 14% (12 requests) were made to S7d4.scene7.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Underarmour.eu.

Content Size

2.8 MB

After Optimization

2.1 MB

In fact, the total size of Underarmour.eu main page is 2.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 563.6 kB

Original 631.9 kB
After minification 626.1 kB
After compression 68.3 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 563.6 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 26.0 kB

Original 942.5 kB
After minification 916.6 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. Underarmour images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 52.7 kB

Original 1.1 MB
After minification 1.1 MB
After compression 1.1 MB

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.

CSS Optimization

-92%

Potential reduce by 56.7 kB

Original 61.8 kB
After minification 51.8 kB
After compression 5.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Underarmour.eu needs all CSS files to be minified and compressed as it can save up to 56.7 kB or 92% of the original size.

Requests Now

After Optimization

The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Underarmour. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 6 to 1 for CSS 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-*] attributes do not match their roles

High

ARIA IDs are not unique

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

These are opportunities to improve keyboard navigation in your application.

High

Some elements have a [tabindex] value greater than 0

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

DE
Encoding

UTF-8

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

underarmour.eu

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Change Shipping Location

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

fonts.css

normalize.css

style.css

utag.sync.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

fonts.css

normalize.css

style.css

utag.sync.js

ua-4672-120.css

moduleTweaks-348110-124.css

datadog-rum.js

FW24_DTC_BackToSchool_Launch_Site_Nav_1_1_COG_EN

flagSprite42.png

logo.svg

menulogo.svg

flame.png

FW24_DTC_BackToSchool_Launch_NAV_Shoes_1_1

FW24_DTC_BackToSchool_Launch_Site_Nav_1_1_M_EN

FW24_DTC_BackToSchool_Launch_Site_Nav_1_1_W_EN

jquery.min.js

bootstrap.bundle.min.js

main.js

productTile.js

lazysizes.js

site.min.js

lib.js

qualtrics.js

notice

commons-4664-32.js

index-4666-67.js

dwanalytics-22.2.js

dwac-21.7.js

gretel.min.js

applepay.js

Tile_Skeleton_Loader.svg

flame.png

underarmour.svg

mmr.png

eps.svg

mastercard-emea.svg

visa-emea.svg

amex-emea.svg

klarna-emea.svg

apple-pay-emea.svg

pay-pal-emea.svg

ratepay.svg

instagram.svg

outline.svg