Tools & Wizards About Us
onphones.ru screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

onphones.ru

Срок регистрации домена истек

Page Load Speed

5.2 sec in total

First Response

1.1 sec

Resources Loaded

3.7 sec

Page Rendered

413 ms

onphones.ru screenshot

About Website

Visit onphones.ru now to see the best up-to-date Onphones content for Russia and also check out these interesting facts you probably never knew about onphones.ru

Срок регистрации домена истек. Требуется продление, чтобы возобновить работу домена и его сервисов

Visit onphones.ru

Key Findings

We analyzed Onphones.ru page load time and found that the first response time was 1.1 sec and then it took 4.1 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

onphones.ru performance score

0

Network Requests Diagram

onphones.ru

1050 ms

style.css

231 ms

pagenavi-css.css

226 ms

css

72 ms

superfish.css

242 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 43% of them (33 requests) were addressed to the original Onphones.ru, 8% (6 requests) were made to Pagead2.googlesyndication.com and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Onphones.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 288.5 kB (18%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onphones.ru main page is 1.6 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 67.8 kB

  • Original 84.3 kB
  • After minification 82.3 kB
  • After compression 16.5 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 67.8 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 6.4 kB

  • Original 1.1 MB
  • After minification 1.1 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. Onphones images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 119.5 kB

  • Original 267.7 kB
  • After minification 252.1 kB
  • After compression 148.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 119.5 kB or 45% of the original size.

CSS Optimization

-85%

Potential reduce by 94.8 kB

  • Original 111.8 kB
  • After minification 80.0 kB
  • After compression 16.9 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. Onphones.ru needs all CSS files to be minified and compressed as it can save up to 94.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (58%)

Requests Now

66

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onphones.ru

onphones.ru

1050 ms

style.css

style.css

231 ms

pagenavi-css.css

pagenavi-css.css

226 ms

css

css

72 ms

superfish.css

superfish.css

242 ms

tabber.css

tabber.css

241 ms

font-awesome.css

font-awesome.css

243 ms

jquery.js

jquery.js

437 ms

jquery-migrate.min.js

jquery-migrate.min.js

514 ms

loader.js

loader.js

173 ms

momma.css

momma.css

532 ms

tw-sack.min.js

tw-sack.min.js

526 ms

wp-ds-blogmap.css

wp-ds-blogmap.css

527 ms

adsbygoogle.js

adsbygoogle.js

64 ms

hoverIntent.min.js

hoverIntent.min.js

524 ms

modernizr.js

modernizr.js

675 ms

tabber.js

tabber.js

807 ms

superfish.js

superfish.js

825 ms

supersubs.js

supersubs.js

825 ms

custom.js

custom.js

804 ms

aff_i

aff_i

77 ms

aff_i

aff_i

155 ms

e763ddd0d9a5fe1_20141002070508.jpg

e763ddd0d9a5fe1_20141002070508.jpg

592 ms

%D0%A4%D0%BE%D0%BD-%D0%B0%D0%BD%D0%B4%D1%80%D0%BE%D0%B8%D0%B42.jpg

%D0%A4%D0%BE%D0%BD-%D0%B0%D0%BD%D0%B4%D1%80%D0%BE%D0%B8%D0%B42.jpg

1434 ms

tn_mesocolumn_header_logo.jpg

tn_mesocolumn_header_logo.jpg

489 ms

%D0%B2%D0%B0%D1%80-%D1%84%D0%B0%D0%BD%D0%B4%D0%B5%D1%80-%D0%B4%D0%BB%D1%8F-%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D1%85-300x182.jpg

%D0%B2%D0%B0%D1%80-%D1%84%D0%B0%D0%BD%D0%B4%D0%B5%D1%80-%D0%B4%D0%BB%D1%8F-%D0%BC%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D1%85-300x182.jpg

494 ms

%D0%BF%D0%BE%D0%BF%D1%83%D0%BB%D1%8F%D1%80%D0%BD%D0%BE%D1%81%D1%82%D1%8C-%D0%B0%D0%B9%D1%84%D0%BE%D0%BD-300x169.jpg

%D0%BF%D0%BE%D0%BF%D1%83%D0%BB%D1%8F%D1%80%D0%BD%D0%BE%D1%81%D1%82%D1%8C-%D0%B0%D0%B9%D1%84%D0%BE%D0%BD-300x169.jpg

386 ms

%D0%B0%D0%BC%D0%B0%D0%B7%D0%BE%D0%BD-300x158.jpg

%D0%B0%D0%BC%D0%B0%D0%B7%D0%BE%D0%BD-300x158.jpg

695 ms

%D0%B0%D0%B9%D1%84%D0%BE%D0%BD%D1%8B-5-%D0%B8-6-300x215.jpg

%D0%B0%D0%B9%D1%84%D0%BE%D0%BD%D1%8B-5-%D0%B8-6-300x215.jpg

583 ms

Magic-Wars1-300x170.jpg

Magic-Wars1-300x170.jpg

699 ms

%D0%9D%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B0-iPhone-300x221.jpg

%D0%9D%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B0-iPhone-300x221.jpg

728 ms

Last-Empire-War-Z-300x50.jpg

Last-Empire-War-Z-300x50.jpg

728 ms

Mob_300-50-1.jpg

Mob_300-50-1.jpg

765 ms

1.jpg

1.jpg

961 ms

Mu-Origin.jpg

Mu-Origin.jpg

966 ms

War-Thunder.jpg

War-Thunder.jpg

987 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

54 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

55 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

90 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

90 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1016 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1030 ms

ca-pub-5065310916003050.js

ca-pub-5065310916003050.js

177 ms

zrt_lookup.html

zrt_lookup.html

275 ms

show_ads_impl.js

show_ads_impl.js

216 ms

pluso-like.js

pluso-like.js

305 ms

hit

hit

307 ms

watch.js

watch.js

9 ms

code.js

code.js

373 ms

arrows-000000.png

arrows-000000.png

822 ms

ads

ads

310 ms

osd.js

osd.js

14 ms

hit

hit

150 ms

counter

counter

179 ms

18035180652361037506

18035180652361037506

79 ms

abg.js

abg.js

83 ms

m_js_controller.js

m_js_controller.js

95 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

72 ms

x_button_blue2.png

x_button_blue2.png

30 ms

s

s

28 ms

Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js

Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js

5 ms

03.png

03.png

432 ms

process

process

308 ms

hit;PLUSO

hit;PLUSO

304 ms

tracker

tracker

163 ms

plus.png

plus.png

303 ms

ui

ui

44 ms

kb.js

kb.js

328 ms

collect_pluso.js

collect_pluso.js

293 ms

hit;PLUSO

hit;PLUSO

151 ms

dct.js

dct.js

248 ms

h.gif

h.gif

140 ms

s.js

s.js

290 ms

crossdnf_pluso_iframe.html

crossdnf_pluso_iframe.html

144 ms

3696d9c5412d7dbcbaf1f52aba44c40f

3696d9c5412d7dbcbaf1f52aba44c40f

85 ms

activeview

activeview

28 ms

SEO Factors

onphones.ru SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onphones.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Onphones.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

onphones.ru

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