89 nike.com Last Updated: 2 years

Success 62% of passed verification steps
Warning 15% of total warning
Errors 23% of total errors, require fast action

Desktop Speed Score

Mobile Speed Score

Performance Desktop Score 33%
Best Practices Desktop Score 77%
SEO Desktop Score 100%
PWA Desktop Score 33%
Performance Mobile Score 17%
Best Practices Mobile Score 77%
SEO Mobile Score 93%
PWA Mobile Score 40%
Page Authority Authority 71%
Domain Authority Domain Authority 91%
Moz Rank 7.1/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 27 Characters
NIKE OFFICIAL SITE. NIKE DE
Meta Description 92 Characters
Inspiring the world's athletes, Nike delivers innovative products, experiences and services.
Effective URL 20 Characters
https://www.nike.com
Excerpt Page content
Nike Official Site. Nike DE Deine Cookie-EinstellungenFür eine bessere Performance, die Nutzung sozialer Medien und für Werbezwecke empfiehlt Nike, Cookies zu akzeptieren. Social-Media-Funktionen und speziell auf dich zugeschnittene Werbung sind nur mit den jeweiligen Cookies möglich. Für mehr Informationen dazu oder um deine Einstellungen zu ändern, klicke auf die Schaltfläche "Mehr Informationen" oder gehe zu den "Cookie-E...
Keywords Cloud Density
nike51 english37 kinder26 schuhe23 alle20 bekleidung18 produkte17 damen14 sale13 herren13
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
nike 51
english 37
kinder 26
schuhe 23
alle 20
bekleidung 18
produkte 17
damen 14
sale 13
herren 13
Google Preview Your look like this in google search result
NIKE OFFICIAL SITE. NIKE DE
https://www.nike.com
Inspiring the world's athletes, Nike delivers innovative products, experiences and services.
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~748.95 KB
Code Size: ~306.6 KB
Text Size: ~442.35 KB Ratio: 59.06%

nike.com Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop Speed Score

Desktop Screenshot
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Keep request counts low and transfer sizes small 130 requests • 2,030 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Time to Interactive 4.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid long main-thread tasks 13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Speed Index 4.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce JavaScript execution time 4.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid serving legacy JavaScript to modern browsers Potential savings of 17 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Avoids enormous network payloads Total size was 2,030 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve images in next-gen formats Potential savings of 26 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Reduce unused JavaScript Potential savings of 495 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Eliminate render-blocking resources Potential savings of 490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minify JavaScript Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Avoid non-composited animations 46 animated elements found
Animations which are not composited can be janky and increase CLS
Avoid chaining critical requests 13 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Reduce unused CSS Potential savings of 18 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Largest Contentful Paint 4.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove duplicate modules in JavaScript bundles Potential savings of 58 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Total Blocking Time 2,010 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy 21 resources found
A long cache lifetime can speed up repeat visits to your page
Defer offscreen images Potential savings of 101 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid multiple page redirects Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded
Avoid an excessive DOM size 2,110 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Initial server response time was short Root document took 350 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 530 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimize main-thread work 5.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

Mobile Speed Score

Mobile Screenshot
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
User Timing marks and measures 7 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Document uses legible font sizes 99.94% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Avoid an excessive DOM size 2,145 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First Meaningful Paint 4.8 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce unused CSS Potential savings of 19 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid non-composited animations 8 animated elements found
Animations which are not composited can be janky and increase CLS
Total Blocking Time 9,420 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests 15 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Reduce initial server response time Root document took 610 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
First Contentful Paint 4.8 s
First Contentful Paint marks the time at which the first text or image is painted
Defer offscreen images Potential savings of 435 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Reduce JavaScript execution time 15.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Eliminate render-blocking resources Potential savings of 1,730 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minify JavaScript Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve images in next-gen formats Potential savings of 13 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Links do not have descriptive text 4 links found
Descriptive link text helps search engines understand your content
Time to Interactive 23.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid serving legacy JavaScript to modern browsers Potential savings of 22 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Reduce unused JavaScript Potential savings of 652 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
First Contentful Paint (3G) 9916 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minimize main-thread work 20.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Serve static assets with an efficient cache policy 23 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid enormous network payloads Total size was 5,006 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize third-party usage Third-party code blocked the main thread for 150 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Enable text compression Potential savings of 4 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Largest Contentful Paint 12.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Keep request counts low and transfer sizes small 149 requests • 5,006 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Speed Index 12.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Remove duplicate modules in JavaScript bundles Potential savings of 58 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Max Potential First Input Delay 1,780 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

nike.com Alexa Rank

99,999,999

Global Rank

99,999,999

-

Domain Available

Domain (TDL) and Typo Status
nike.co Available Buy Now!
nike.us Available Buy Now!
nike.com Available Buy Now!
nike.org Available Buy Now!
nike.net Available Buy Now!
nke.com Available Buy Now!
hike.com Available Buy Now!
uike.com Available Buy Now!

Information Server nike.com

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 302 
server: AkamaiGHost
content-length: 0
location: https://www.nike.com/de/
date: Thu, 30 Dec 2021 13:12:53 GMT
set-cookie: AnalysisUserId=184.86.102.18.8171640869973637; expires=Mon, 31-Dec-2038 23:59:59 GMT; path=/; domain=.nike.com
set-cookie: geoloc=cc=DE,rc=NW,tp=vhigh,tz=GMT+1,la=51.22,lo=6.77; path=/; domain=.nike.com
set-cookie: anonymousId=4263FBCAD1DE3117BD6C5978E1ACF7EA; expires=Thu, 13-Jan-2022 13:12:53 GMT
set-cookie: _abck=74CC2C75F3C5D63CA9562566F50F8A1E~-1~YAAQEmZWuMe6HKF9AQAAhc54Cwd/UhJKldZO8VlSDhBI5razsFAHTEtFSA4yuWXbwQd5s6NAH78HCpmjMIrtEiCi+CeBtfXqrWt0gZMn4FOurnsKHDmITzT1A3W6qhG9bqBhQJja8g+R32kujpYrK5qaBU9opWQze5E0R+C0NxihEYMXawNJv2Al1QDyR3M82pttRKiB3ZHUApYBczN2KfK/xBOSEti+pg7gPVhIL+zDA0AOwkD5BJLm8AG/D8Od+DvxCe6t6L0xLpdNsKFF9ZHIw8dautUAJsxiaWGIr4olZtOk0oGvA3Up2ZItU/qjz45e/A7JyWXaoDHsUC0NGCpfRxgYTWanDtbZ+LbMKbNTWzg2j6Me20mReEjbQ7E0ogRgSpDY8RfHwyF5dkRQFuXjr2k9Jn6v0m0ZHjFGAJfuY19To20crC8K~-1~-1~-1; Domain=.nike.com; Path=/; Expires=Fri, 30 Dec 2022 13:12:53 GMT; Max-Age=31536000; Secure
set-cookie: bm_sz=BAAE68DF374CF21AC681AF394811C6E0~YAAQEmZWuMi6HKF9AQAAhc54Cw5DuCS4pdtUlUCIpnU7hTfiFpvhNSjFIHk0o5P82zlM4JDILRJ9z2EEhn8qgbvLIkY4scDIyGJx0PTNyhke+OHJ7KUdBwhcI9H+6KHn4fXCYZ8Ur5Vj5YDYrEdqHIcPgL+wELZ4P3Ku/txb2VVMJXPsLsWd1JTrpdXiam/uZmmHt8/+ObIbL2qrpX75fsCb5NTw70zQBxrhCc4vXpGxCDR0oYk9PjNivntOcwyGETO73sQbiUa15GHWCzi15iD3sCO29wvD6D1vcsrU2k4rWC67jDH+wxEi1B/n6hDnxnE8sbNvXmnRPqjkEeXvnkhBrBXJq1mwT6iMrC9uTfxKsK+yE77C980ETVfELTg=~3228997~4604983; Domain=.nike.com; Path=/; Expires=Thu, 30 Dec 2021 17:12:53 GMT; Max-Age=14400
DNS Records DNS Resource Records associated with a hostname
nike.com View DNS Records

Social Data