Tools & Wizards About Us
nillkin-case.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nillkin-case.com

Nillkin official shop - cases, screen protectors & chargers

Page Load Speed

4.7 sec in total

First Response

427 ms

Resources Loaded

4 sec

Page Rendered

267 ms

nillkin-case.com screenshot

About Website

Welcome to nillkin-case.com homepage info - get ready to check Nillkin Case best content for India right away, or after learning these important things about nillkin-case.com

Nillkin official website, Nillkin shop: cases, screen protectors, chargers, cables

Visit nillkin-case.com

Key Findings

We analyzed Nillkin-case.com page load time and found that the first response time was 427 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

nillkin-case.com performance score

0

Network Requests Diagram

nillkin-case.com

427 ms

www.nillkin-case.com

549 ms

big.css

276 ms

element.js

71 ms

big.js

647 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 84% of them (52 requests) were addressed to the original Nillkin-case.com, 6% (4 requests) were made to Translate.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Nillkin-case.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.6 kB (31%)

Content Size

883.8 kB

After Optimization

613.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nillkin-case.com main page is 883.8 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. 40% of websites need less resources to load. Images take 481.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 48.3 kB

  • Original 56.6 kB
  • After minification 48.8 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 7.8 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 48.3 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 19.2 kB

  • Original 481.3 kB
  • After minification 462.0 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. Nillkin Case images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 32.7 kB

  • Original 135.6 kB
  • After minification 135.6 kB
  • After compression 102.9 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 32.7 kB or 24% of the original size.

CSS Optimization

-81%

Potential reduce by 170.3 kB

  • Original 210.3 kB
  • After minification 206.4 kB
  • After compression 40.0 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. Nillkin-case.com needs all CSS files to be minified and compressed as it can save up to 170.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (25%)

Requests Now

59

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nillkin-case.com

nillkin-case.com

427 ms

www.nillkin-case.com

www.nillkin-case.com

549 ms

big.css

big.css

276 ms

element.js

element.js

71 ms

big.js

big.js

647 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

503 ms

jquery.cookie.js

jquery.cookie.js

259 ms

code.photoswipe.jquery-3.0.5.js

code.photoswipe.jquery-3.0.5.js

397 ms

watch.js

watch.js

0 ms

translateelement.css

translateelement.css

164 ms

main.js

main.js

177 ms

element_main.js

element_main.js

71 ms

logo.png

logo.png

135 ms

footer.gif

footer.gif

132 ms

bg-ul.png

bg-ul.png

133 ms

bg-section.png

bg-section.png

136 ms

up-arrow.png

up-arrow.png

134 ms

paypalx.png

paypalx.png

210 ms

dhl.png

dhl.png

208 ms

dev4520_1-120x120.jpg

dev4520_1-120x120.jpg

213 ms

dev4519_1-120x120.jpg

dev4519_1-120x120.jpg

216 ms

dev4515_1-120x120.jpg

dev4515_1-120x120.jpg

317 ms

dev4514_1-120x120.jpg

dev4514_1-120x120.jpg

213 ms

dev4517_1-120x120.jpg

dev4517_1-120x120.jpg

312 ms

dev4516_1-120x120.jpg

dev4516_1-120x120.jpg

313 ms

dev4518_1-120x120.jpg

dev4518_1-120x120.jpg

318 ms

dev4511_1-120x120.jpg

dev4511_1-120x120.jpg

317 ms

dev4513_1-120x120.jpg

dev4513_1-120x120.jpg

318 ms

dev4512_1-120x120.jpg

dev4512_1-120x120.jpg

430 ms

dev4509_1-120x120.jpg

dev4509_1-120x120.jpg

429 ms

dev4508_1-120x120.jpg

dev4508_1-120x120.jpg

438 ms

dev4510_1-120x120.jpg

dev4510_1-120x120.jpg

439 ms

dev4502_1-120x120.jpg

dev4502_1-120x120.jpg

438 ms

dev4506_1-120x120.jpg

dev4506_1-120x120.jpg

439 ms

dev4501_1-120x120.jpg

dev4501_1-120x120.jpg

530 ms

dev4476_1-40x40.jpg

dev4476_1-40x40.jpg

532 ms

dev2231_1-40x40.jpg

dev2231_1-40x40.jpg

533 ms

dev413_1-40x40.jpg

dev413_1-40x40.jpg

533 ms

dev4063_1-40x40.jpg

dev4063_1-40x40.jpg

536 ms

dev3760_1-40x40.jpg

dev3760_1-40x40.jpg

535 ms

dev446_1-40x40.jpg

dev446_1-40x40.jpg

630 ms

dev3722_1-40x40.jpg

dev3722_1-40x40.jpg

632 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1455 ms

front_banner.php

front_banner.php

623 ms

analytics.js

analytics.js

81 ms

overlay.png

overlay.png

519 ms

collect

collect

42 ms

translate_24dp.png

translate_24dp.png

60 ms

l

l

61 ms

googlelogo_color_42x16dp.png

googlelogo_color_42x16dp.png

45 ms

jquery.bxslider.css

jquery.bxslider.css

798 ms

banner_hermit_charger.png

banner_hermit_charger.png

423 ms

banner_lg_g4_qin.png

banner_lg_g4_qin.png

440 ms

banner_z3_compact2.png

banner_z3_compact2.png

439 ms

banner_lumia_640.png

banner_lumia_640.png

438 ms

banner_nexus5.png

banner_nexus5.png

438 ms

banner_z3_compact.png

banner_z3_compact.png

438 ms

nillkin_sparkle_series.png

nillkin_sparkle_series.png

748 ms

nillkin_fresh_series.png

nillkin_fresh_series.png

641 ms

glass_z1_compact.png

glass_z1_compact.png

642 ms

glass_z2.png

glass_z2.png

647 ms

bx_loader.gif

bx_loader.gif

107 ms

SEO Factors

nillkin-case.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nillkin-case.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nillkin-case.com 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

nillkin-case.com

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