Tools & Wizards About Us
nike-free-run.us screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nike-free-run.us

Page Load Speed

10.7 sec in total

First Response

260 ms

Resources Loaded

10.1 sec

Page Rendered

322 ms

nike-free-run.us screenshot

About Website

Welcome to nike-free-run.us homepage info - get ready to check Nike Free Run best content right away, or after learning these important things about nike-free-run.us

Free Run,Nike Free,nike free sko,nike free tilbud,billig nike free,nike free run,nike free 3.0,nike free 5.0,nike free 7.0,nike free 2011,nike free dame,nike free sale,nike free sort,Billige! 50% off....

Visit nike-free-run.us

Key Findings

We analyzed Nike-free-run.us page load time and found that the first response time was 260 ms and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

nike-free-run.us performance score

0

Network Requests Diagram

nike-free-run.us

260 ms

css.css

265 ms

jquery-1.4.2.js

456 ms

images.js

147 ms

jquery-ui.min.js

674 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 89% of them (17 requests) were addressed to the original Nike-free-run.us, 5% (1 request) were made to Js.users.51.la and 5% (1 request) were made to Icon.51.la. The less responsive or slowest element that took the longest time to load (944 ms) belongs to the original domain Nike-free-run.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 235.7 kB (25%)

Content Size

938.6 kB

After Optimization

703.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nike-free-run.us main page is 938.6 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. Images take 651.1 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 10.7 kB

  • Original 15.8 kB
  • After minification 15.5 kB
  • After compression 5.1 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 10.7 kB or 68% of the original size.

Image Optimization

-4%

Potential reduce by 23.1 kB

  • Original 651.1 kB
  • After minification 628.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. Nike Free Run images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 191.5 kB

  • Original 258.7 kB
  • After minification 258.5 kB
  • After compression 67.2 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 191.5 kB or 74% of the original size.

CSS Optimization

-80%

Potential reduce by 10.4 kB

  • Original 13.0 kB
  • After minification 10.9 kB
  • After compression 2.6 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-free-run.us needs all CSS files to be minified and compressed as it can save up to 10.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (17%)

Requests Now

18

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nike-free-run.us

nike-free-run.us

260 ms

css.css

css.css

265 ms

jquery-1.4.2.js

jquery-1.4.2.js

456 ms

images.js

images.js

147 ms

jquery-ui.min.js

jquery-ui.min.js

674 ms

5788075.js

5788075.js

897 ms

bg.png

bg.png

939 ms

logo.png

logo.png

125 ms

cart.gif

cart.gif

145 ms

search.gif

search.gif

127 ms

xian.jpg

xian.jpg

310 ms

bannerbottom.jpg

bannerbottom.jpg

373 ms

payment.jpg

payment.jpg

310 ms

mcaffee.gif

mcaffee.gif

263 ms

banner01.jpg

banner01.jpg

759 ms

nike-free-run.us

nike-free-run.us

450 ms

banner02.jpg

banner02.jpg

858 ms

banner03.jpg

banner03.jpg

944 ms

icon_0.gif

icon_0.gif

517 ms

SEO Factors

nike-free-run.us SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nike-free-run.us 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-free-run.us 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

nike-free-run.us

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