Tools & Wizards About Us
i180.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

i180.ru

i180 | Объективы для iPhone, fisheye для iPhone | купить сегодня

Page Load Speed

3.8 sec in total

First Response

696 ms

Resources Loaded

2.8 sec

Page Rendered

292 ms

i180.ru screenshot

About Website

Click here to check amazing I 180 content for Russia. Otherwise, check out these important facts you probably never knew about i180.ru

Объективы и камеры для iPhone, iPad и других телефонов.

Visit i180.ru

Key Findings

We analyzed I180.ru page load time and found that the first response time was 696 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

i180.ru performance score

0

Network Requests Diagram

i180.ru

696 ms

style.css

394 ms

jquery-1.3.1.min.js

773 ms

jquery.dropdownPlain.js

260 ms

jquery.colorbox-min.js

387 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 61% of them (17 requests) were addressed to the original I180.ru, 14% (4 requests) were made to Mc.yandex.ru and 11% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain I180.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 173.9 kB (30%)

Content Size

571.7 kB

After Optimization

397.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I180.ru main page is 571.7 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. 30% of websites need less resources to load. Images take 316.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 13.0 kB

  • Original 17.1 kB
  • After minification 14.0 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 3.0 kB, which is 18% 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 13.0 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 2.1 kB

  • Original 316.2 kB
  • After minification 314.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. I 180 images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 143.2 kB

  • Original 219.0 kB
  • After minification 199.1 kB
  • After compression 75.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 143.2 kB or 65% of the original size.

CSS Optimization

-81%

Potential reduce by 15.7 kB

  • Original 19.4 kB
  • After minification 13.4 kB
  • After compression 3.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. I180.ru needs all CSS files to be minified and compressed as it can save up to 15.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (28%)

Requests Now

25

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

i180.ru

i180.ru

696 ms

style.css

style.css

394 ms

jquery-1.3.1.min.js

jquery-1.3.1.min.js

773 ms

jquery.dropdownPlain.js

jquery.dropdownPlain.js

260 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

387 ms

colorbox.css

colorbox.css

396 ms

share.js

share.js

14 ms

openapi.js

openapi.js

369 ms

watch.js

watch.js

168 ms

watch.js

watch.js

735 ms

bg_home.jpg

bg_home.jpg

1461 ms

fisheye_180_magnet.jpg

fisheye_180_magnet.jpg

265 ms

univer.jpg

univer.jpg

167 ms

corner_5.png

corner_5.png

258 ms

3in1_fisheye.jpg

3in1_fisheye.jpg

387 ms

i180_clipsa.jpg

i180_clipsa.jpg

396 ms

superfisheye.jpg

superfisheye.jpg

269 ms

olloclip_dlya_iphone5.jpg

olloclip_dlya_iphone5.jpg

517 ms

all.js

all.js

69 ms

logo.gif

logo.gif

390 ms

American-Retro.ttf

American-Retro.ttf

616 ms

140 ms

xd_arbiter.php

xd_arbiter.php

64 ms

xd_arbiter.php

xd_arbiter.php

120 ms

overlay.png

overlay.png

352 ms

advert.gif

advert.gif

159 ms

1

1

182 ms

xd_arbiter.php

xd_arbiter.php

41 ms

SEO Factors

i180.ru SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I180.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 I180.ru 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

i180.ru

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