7.9 sec in total
982 ms
6.2 sec
793 ms
Welcome to underarmour.co.nz homepage info - get ready to check Under Armour best content for New Zealand right away, or after learning these important things about underarmour.co.nz
Under Armour
Visit underarmour.co.nzWe analyzed Underarmour.co.nz page load time and found that the first response time was 982 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
underarmour.co.nz performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value9.5 s
0/100
25%
Value44.2 s
0/100
10%
Value56,540 ms
0/100
30%
Value0.495
16/100
15%
Value77.2 s
0/100
10%
982 ms
56 ms
156 ms
64 ms
50 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 49% of them (34 requests) were addressed to the original Underarmour.co.nz, 32% (22 requests) were made to Underarmour.scene7.com and 6% (4 requests) were made to Sitegenesis.production.ua.coremedia.cloud. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Underarmour.co.nz.
Page size can be reduced by 319.2 kB (15%)
2.2 MB
1.8 MB
In fact, the total size of Underarmour.co.nz main page is 2.2 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 314.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 314.4 kB or 87% of the original size.
Potential reduce by 3.1 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. Under Armour images are well optimized though.
Potential reduce by 460 B
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.
Potential reduce by 1.2 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.co.nz has all CSS files already compressed.
Number of requests can be reduced by 23 (37%)
63
40
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Under Armour. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
982 ms
fonts.css
56 ms
normalize.css
156 ms
style.css
64 ms
utag.sync.js
50 ms
ua-4672-110.css
142 ms
moduleTweaks-348110-114.css
144 ms
SS22_TRN_RUSH_HeatGear_Site_1_1
242 ms
SS22_WMN_Infinity_Q2_Site_1_1_2
312 ms
SS22_TRN_ProjectRock_Q2_CLP_Site_1_1_3
310 ms
SS22_RUN_Flow_Synchronicity_Site_1_1_3
340 ms
FW20_GLF_SweaterFleece_Site_1_1_M
308 ms
SS22_RUN_HOVR_Machina3_Q2_Site_1_1_M
282 ms
SS22_EasterPromo_Site_1_1_Nav_M
241 ms
flagSprite42.png
1119 ms
logo.svg
197 ms
menulogo.svg
194 ms
flame.png
968 ms
SS22_RUN_RunAnywhere_Site_2_1_2
245 ms
SS22_RUN_RunAnywhere_Site_5_4
276 ms
FW21_TRN_WinterTrain_Q4_Site_1_1
263 ms
FW21_TRN_WinterTrain_Q4_Site_1_1_6
348 ms
FW21_YTH_Q4_CG_Armour_Site_1_1
406 ms
SS22_Run_Phantom_Site_1_1_W
715 ms
FW22_TRN_ProjectRock_Q3_Site_2_1_M
357 ms
FW22_TRN_ProjectRock_Q3_Site_1_1_M
373 ms
RFS_MACHIN_Desktop_Hero_7_5
383 ms
SS22_RFS_Desktop_Hero_GIF_4x5
461 ms
SS22_RFS_Desktop_Hero_GIF_4x5
464 ms
flame.png
129 ms
Tile_Skeleton_Loader.svg
208 ms
NeuePlakUA-SemiBold.woff
1048 ms
NeuePlakUA-Regular.woff
1295 ms
NeuePlakUA-Bold.woff
1318 ms
NeuePlakUA-CompBlack.woff
1208 ms
icomoon.ttf
1797 ms
jquery.min.js
1949 ms
bootstrap.bundle.min.js
1008 ms
productTile.js
1981 ms
main.js
2683 ms
custom.js
1238 ms
lazysizes.js
2038 ms
qualtrics.js
1254 ms
notice
212 ms
viewer.js
185 ms
commons-4664-31.js
38 ms
index-4666-61.js
53 ms
dwanalytics-22.2.js
1277 ms
dwac-21.7.js
1284 ms
gretel.min.js
151 ms
applepay.js
1317 ms
underarmour.svg
1351 ms
mmr.png
1358 ms
Mastercard_150px.svg
1388 ms
Visa_150px.svg
1402 ms
PayPal_150px.svg
1419 ms
instagram.svg
1438 ms
outline.svg
1451 ms
outline%20%281%29.svg
1478 ms
outline%20%282%29.svg
1493 ms
FW22_BTS_Hustle_Site_8_5_M
297 ms
FW22_BTS_Hustle_Site_1_1_M
406 ms
SS22_WMN_Meridian_Q2_Site_8_5
405 ms
SS22_WMN_BetterBook_Site_1_1_4
360 ms
site.min.js
168 ms
73MKS-MSXL9-ZDN3K-2546H-SMFGK
63 ms
utag.js
38 ms
config.json
50 ms
pebble
19 ms
underarmour.co.nz accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
underarmour.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
underarmour.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Underarmour.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Underarmour.co.nz 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.
underarmour.co.nz
Open Graph description is not detected on the main page of Under Armour. 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: