Tools & Wizards About Us
i-life.us screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

i-life.us

Laptops | All in one | Tablets | Smart Phones | Virtual Reality | Life Digital

Page Load Speed

5.6 sec in total

First Response

1.3 sec

Resources Loaded

3.8 sec

Page Rendered

527 ms

i-life.us screenshot

About Website

Welcome to i-life.us homepage info - get ready to check I Life best content for Iran right away, or after learning these important things about i-life.us

I-Life Technologies Inc creates extraordinary products like Laptops, All in one PC, Desktops, 2 in 1, Tablets, Smart Phones, Smart Watches, Virtual Reality and much more.

Visit i-life.us

Key Findings

We analyzed I-life.us page load time and found that the first response time was 1.3 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

i-life.us performance score

0

Network Requests Diagram

i-life.us

1299 ms

style.css

214 ms

css

35 ms

styles.css

84 ms

jquery-ui.min.css

30 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 91% of them (94 requests) were addressed to the original I-life.us, 3% (3 requests) were made to Fonts.googleapis.com and 2% (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 I-life.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (23%)

Content Size

5.2 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I-life.us main page is 5.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. Only a small number of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 34.5 kB

  • Original 44.1 kB
  • After minification 42.4 kB
  • After compression 9.6 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 34.5 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 116.0 kB

  • Original 3.9 MB
  • After minification 3.8 MB

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. I Life images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 514.1 kB

  • Original 721.2 kB
  • After minification 668.9 kB
  • After compression 207.1 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 514.1 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 517.0 kB

  • Original 595.1 kB
  • After minification 482.2 kB
  • After compression 78.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. I-life.us needs all CSS files to be minified and compressed as it can save up to 517.0 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (65%)

Requests Now

101

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

i-life.us

i-life.us

1299 ms

style.css

style.css

214 ms

css

css

35 ms

styles.css

styles.css

84 ms

jquery-ui.min.css

jquery-ui.min.css

30 ms

jquery-ui-timepicker-addon.min.css

jquery-ui-timepicker-addon.min.css

88 ms

font-awesome.min.css

font-awesome.min.css

129 ms

bootstrap.css

bootstrap.css

288 ms

front.css

front.css

155 ms

tab.min.css

tab.min.css

117 ms

jquery.autocomplete.css

jquery.autocomplete.css

134 ms

woocommerce-layout.css

woocommerce-layout.css

186 ms

woocommerce.css

woocommerce.css

252 ms

layout.css

layout.css

178 ms

prdctfltr.css

prdctfltr.css

238 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

304 ms

ion.rangeSlider.css

ion.rangeSlider.css

230 ms

template-assets.php

template-assets.php

297 ms

jquery.js

jquery.js

360 ms

jquery-migrate.min.js

jquery-migrate.min.js

281 ms

bootstrap.min.js

bootstrap.min.js

332 ms

front.js

front.js

324 ms

chosen.jquery.min.js

chosen.jquery.min.js

326 ms

ion.rangeSlider.min.js

ion.rangeSlider.min.js

330 ms

cyclone-slider.min.js

cyclone-slider.min.js

346 ms

template-assets.php

template-assets.php

425 ms

superfish.js

superfish.js

368 ms

woo_tabs.js

woo_tabs.js

373 ms

general.js

general.js

376 ms

jquery.uniform.min.js

jquery.uniform.min.js

387 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

392 ms

css

css

26 ms

default.css

default.css

409 ms

shortcodes.css

shortcodes.css

407 ms

custom.css

custom.css

419 ms

jquery.form.min.js

jquery.form.min.js

402 ms

scripts.js

scripts.js

411 ms

core.min.js

core.min.js

415 ms

datepicker.min.js

datepicker.min.js

426 ms

jquery-ui-timepicker-addon.min.js

jquery-ui-timepicker-addon.min.js

451 ms

widget.min.js

widget.min.js

401 ms

mouse.min.js

mouse.min.js

396 ms

slider.min.js

slider.min.js

369 ms

button.min.js

button.min.js

362 ms

jquery-ui-sliderAccess.js

jquery-ui-sliderAccess.js

372 ms

underscore.min.js

underscore.min.js

371 ms

backbone.min.js

backbone.min.js

348 ms

backbone.localStorage.js

backbone.localStorage.js

335 ms

reset.css

reset.css

296 ms

jquery.autocomplete.js

jquery.autocomplete.js

395 ms

predictive-search.backbone.js

predictive-search.backbone.js

392 ms

predictive-search-popup.backbone.min.js

predictive-search-popup.backbone.min.js

375 ms

add-to-cart.min.js

add-to-cart.min.js

349 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

348 ms

woocommerce.min.js

woocommerce.min.js

329 ms

jquery.cookie.min.js

jquery.cookie.min.js

331 ms

cart-fragments.min.js

cart-fragments.min.js

309 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

307 ms

isotope.js

isotope.js

316 ms

hoverIntent.min.js

hoverIntent.min.js

301 ms

prdctfltr_main.js

prdctfltr_main.js

411 ms

thickbox.js

thickbox.js

467 ms

wp-embed.min.js

wp-embed.min.js

456 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

113 ms

css

css

75 ms

styles.css

styles.css

77 ms

logo.png

logo.png

230 ms

ico-search.png

ico-search.png

230 ms

i-cruise-banner.jpg

i-cruise-banner.jpg

276 ms

itell-K4700-banner.jpg

itell-K4700-banner.jpg

281 ms

NEW-Smart-Phone-Banner-2000.jpg

NEW-Smart-Phone-Banner-2000.jpg

278 ms

Zedwatch-banner-.jpg

Zedwatch-banner-.jpg

279 ms

banner-new-1.jpg

banner-new-1.jpg

494 ms

Intel-Banner-for-Web.jpg

Intel-Banner-for-Web.jpg

496 ms

s501-slider.jpg

s501-slider.jpg

297 ms

rnd-1.png

rnd-1.png

287 ms

rnd-2.png

rnd-2.png

287 ms

rnd-7.png

rnd-7.png

288 ms

rnd-6.png

rnd-6.png

287 ms

rnd-5.png

rnd-5.png

289 ms

rnd-8.png

rnd-8.png

300 ms

featured-bg2.jpg

featured-bg2.jpg

495 ms

S501-W1.png

S501-W1.png

486 ms

K4700.png

K4700.png

492 ms

ZED-book.png

ZED-book.png

488 ms

Kids-tab-7.png

Kids-tab-7.png

497 ms

ZED-watch.png

ZED-watch.png

495 ms

WTAB-800.png

WTAB-800.png

522 ms

S500.png

S500.png

494 ms

feat-1-1.png

feat-1-1.png

496 ms

feat-1-2.png

feat-1-2.png

497 ms

feat-1-3.png

feat-1-3.png

499 ms

feat-1-4.png

feat-1-4.png

497 ms

feat-1-5.png

feat-1-5.png

499 ms

feat-1-6.png

feat-1-6.png

499 ms

analytics.js

analytics.js

196 ms

i-life.us

i-life.us

1514 ms

loadingAnimation.gif

loadingAnimation.gif

304 ms

widget_v2.134.js

widget_v2.134.js

76 ms

collect

collect

219 ms

avatar_simple_visitor.png

avatar_simple_visitor.png

101 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

46 ms

aL63HcygAAVYuCCsAAA==

aL63HcygAAVYuCCsAAA==

1 ms

SEO Factors

i-life.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 I-life.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 I-life.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

i-life.us

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