2.7 sec in total
616 ms
1.6 sec
431 ms
Welcome to nike.in homepage info - get ready to check Nike best content right away, or after learning these important things about nike.in
Inspiring the world's athletes, Nike delivers innovative products, experiences and services.
Visit nike.inWe analyzed Nike.in page load time and found that the first response time was 616 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
nike.in performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value23.8 s
0/100
25%
Value12.2 s
3/100
10%
Value12,200 ms
0/100
30%
Value0.017
100/100
15%
Value32.9 s
0/100
10%
616 ms
21 ms
129 ms
83 ms
48 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Nike.in, 3% (1 request) were made to S.go-mpulse.net and 3% (1 request) were made to C.go-mpulse.net. The less responsive or slowest element that took the longest time to load (616 ms) relates to the external source Nike.com.
Page size can be reduced by 1.5 MB (62%)
2.3 MB
890.9 kB
In fact, the total size of Nike.in 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. 55% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 674.0 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 674.0 kB or 85% of the original size.
Potential reduce by 650.6 kB
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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 650.6 kB or 47% of the original size.
Potential reduce by 131.7 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. Nike.in needs all CSS files to be minified and compressed as it can save up to 131.7 kB or 81% of the original size.
Number of requests can be reduced by 27 (82%)
33
6
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nike. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
616 ms
glyphs.min.css
21 ms
ncss.en-gb.min.css
129 ms
privacy-core.js
83 ms
analytics-client.min.js
48 ms
bundle.umd.js
74 ms
lcp-image-loader.js
51 ms
at.js
27 ms
bundle.js
35 ms
bundle.js
47 ms
6aa740ca2ac73a8e.css
54 ms
polyfills-c67a75d1b6f99dc8.js
53 ms
webpack-2b244731541d6870.js
56 ms
main-bb0fb08cc5703d73.js
94 ms
framework-f5bac9606c6cb942.js
71 ms
_app-807e2f3d62277c78.js
70 ms
942-25de57bf583f77e5.js
80 ms
%5B%5B...page%5D%5D-de7ffb8470c2cc10.js
122 ms
_buildManifest.js
77 ms
_ssgManifest.js
83 ms
p.js
87 ms
react.production.min.js
96 ms
react-dom.production.min.js
88 ms
core.umd.min.js
113 ms
styled.umd.min.js
114 ms
styled-base.umd.min.js
104 ms
header.clientBundle.0e54801afcbb79c4b8a1.js
362 ms
commons.clientBundle.0e54801afcbb79c4b8a1.js
106 ms
footer.clientBundle.0e54801afcbb79c4b8a1.js
114 ms
s8HypWZX4
353 ms
AERUL-JUD3H-8RUDQ-SABVF-2UCEG
248 ms
index.html
325 ms
HelveticaNowText.woff
72 ms
HelveticaNowTextMedium.woff
17 ms
config.json
185 ms
nike-shop-client.js
304 ms
nike.in 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-hidden="true"] elements contain focusable descendents
[role] values are not valid
nike.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
nike.in SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nike.in 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 Nike.in 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.
nike.in
Open Graph data is detected on the main page of Nike. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: