Tools & Wizards About Us
4zte.ru screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

4zte.ru

4ZTE.ru - все про смартфоны и планшеты ZTE: прошивки, обзоры, отзывы и инструкции (ROOT, CWM и т.д.)

Page Load Speed

4.5 sec in total

First Response

1 sec

Resources Loaded

3 sec

Page Rendered

477 ms

4zte.ru screenshot

About Website

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

Все для смартфонов и планшетов от компании ZTE - прошивки, обзоры, инструкции и отзывы владельцев.

Visit 4zte.ru

Key Findings

We analyzed 4zte.ru page load time and found that the first response time was 1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

4zte.ru performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value2,710 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value33.9 s

0/100

10%

Network Requests Diagram

4zte.ru

1042 ms

style.css

129 ms

styles.css

245 ms

css

60 ms

style.css

246 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 52% of them (39 requests) were addressed to the original 4zte.ru, 17% (13 requests) were made to Vk.com and 4% (3 requests) were made to Loader.topadvert.ru. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain 4zte.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 609.3 kB (49%)

Content Size

1.3 MB

After Optimization

641.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 4zte.ru main page is 1.3 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. 60% of websites need less resources to load. Javascripts take 629.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 43.6 kB

  • Original 52.4 kB
  • After minification 45.3 kB
  • After compression 8.8 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.2 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 43.6 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 39.4 kB

  • Original 487.3 kB
  • After minification 447.9 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. 4ZTE images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 461.1 kB

  • Original 629.6 kB
  • After minification 506.6 kB
  • After compression 168.5 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 461.1 kB or 73% of the original size.

CSS Optimization

-80%

Potential reduce by 65.2 kB

  • Original 81.2 kB
  • After minification 64.9 kB
  • After compression 15.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. 4zte.ru needs all CSS files to be minified and compressed as it can save up to 65.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (49%)

Requests Now

74

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

4zte.ru

4zte.ru

1042 ms

style.css

style.css

129 ms

styles.css

styles.css

245 ms

css

css

60 ms

style.css

style.css

246 ms

lightbox.min.ru_RU.css

lightbox.min.ru_RU.css

246 ms

openapi.js

openapi.js

382 ms

jquery.js

jquery.js

380 ms

openapi.js

openapi.js

633 ms

callback.js

callback.js

255 ms

share.js

share.js

262 ms

plusone.js

plusone.js

66 ms

load.js

load.js

43 ms

openapi.js

openapi.js

518 ms

jquery.form.min.js

jquery.form.min.js

241 ms

scripts.js

scripts.js

355 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

358 ms

simplecatch_slider.js

simplecatch_slider.js

358 ms

simplecatch_search.js

simplecatch_search.js

363 ms

wp-lightbox-2.min.js

wp-lightbox-2.min.js

370 ms

978.css

978.css

363 ms

zte.png

zte.png

250 ms

zte-blade-s7-210x210.jpg

zte-blade-s7-210x210.jpg

123 ms

zte-blade-x9-210x210.jpg

zte-blade-x9-210x210.jpg

125 ms

DSC02002-210x210.jpg

DSC02002-210x210.jpg

124 ms

%D0%B2-%D1%80%D1%83%D0%BA%D0%B5-210x210.jpg

%D0%B2-%D1%80%D1%83%D0%BA%D0%B5-210x210.jpg

125 ms

4-1-210x210.jpg

4-1-210x210.jpg

126 ms

%D0%92%D0%BD%D0%B5%D1%88%D0%BD%D0%B5-1-210x210.jpg

%D0%92%D0%BD%D0%B5%D1%88%D0%BD%D0%B5-1-210x210.jpg

247 ms

zte-nubia-z9-2-210x210.jpg

zte-nubia-z9-2-210x210.jpg

247 ms

ZTE-Sports-Camera-210x210.jpg

ZTE-Sports-Camera-210x210.jpg

251 ms

ZTE-Venus-Business-Intelligence-210x210.jpg

ZTE-Venus-Business-Intelligence-210x210.jpg

248 ms

ZTE-V790-mini.jpg

ZTE-V790-mini.jpg

250 ms

ZTE-V880E-mini.jpg

ZTE-V880E-mini.jpg

486 ms

ZTE-Blade-mini.jpg

ZTE-Blade-mini.jpg

487 ms

ZTE-V889M-mini.jpg

ZTE-V889M-mini.jpg

366 ms

ZTE-Grand-Era-mini.jpg

ZTE-Grand-Era-mini.jpg

487 ms

ZTE-Nubia-Z5-mini.jpg

ZTE-Nubia-Z5-mini.jpg

521 ms

ZTE-V970-mini.jpg

ZTE-V970-mini.jpg

369 ms

ZTE-V881-mini.jpg

ZTE-V881-mini.jpg

497 ms

ZTE-V880G-mini.jpg

ZTE-V880G-mini.jpg

498 ms

zte-footer.png

zte-footer.png

607 ms

openapi.js

openapi.js

388 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

22 ms

header-bg.jpg

header-bg.jpg

575 ms

header-top-footer-bg.jpg

header-top-footer-bg.jpg

905 ms

post-by-seperator.jpg

post-by-seperator.jpg

445 ms

ul-bg.png

ul-bg.png

448 ms

ul-bg-prev.png

ul-bg-prev.png

474 ms

px.gif

px.gif

19 ms

cnt

cnt

392 ms

pixel;r=933220126;a=p-WCeJmPS5E7cR4;fpan=1;fpa=P0-980398655-1456819050252;ns=0;ce=1;je=0;sr=1024x768x32;enc=n;dst=0;et=1456819050252;tzo=-180;ref=;url=http%3A%2F%2F4zte.ru%2F;ogl=

pixel;r=933220126;a=p-WCeJmPS5E7cR4;fpan=1;fpa=P0-980398655-1456819050252;ns=0;ce=1;je=0;sr=1024x768x32;enc=n;dst=0;et=1456819050252;tzo=-180;ref=;url=http%3A%2F%2F4zte.ru%2F;ogl=

16 ms

px.gif

px.gif

3 ms

upload.gif

upload.gif

131 ms

widget_community.php

widget_community.php

292 ms

ga.js

ga.js

15 ms

feed

feed

297 ms

__utm.gif

__utm.gif

15 ms

loader_nav19127_3.js

loader_nav19127_3.js

137 ms

lite.css

lite.css

128 ms

lite.js

lite.js

505 ms

lang3_0.js

lang3_0.js

253 ms

widget_community.css

widget_community.css

253 ms

xdm.js

xdm.js

260 ms

al_community.js

al_community.js

259 ms

feed

feed

185 ms

mJKzmCwtk-s.jpg

mJKzmCwtk-s.jpg

397 ms

MgDJx8fllI0.jpg

MgDJx8fllI0.jpg

391 ms

Mx9B_gixGt0.jpg

Mx9B_gixGt0.jpg

388 ms

yeYRK6cJGvc.jpg

yeYRK6cJGvc.jpg

397 ms

06t6fGuH5vk.jpg

06t6fGuH5vk.jpg

388 ms

nKTAtuFnWs0.jpg

nKTAtuFnWs0.jpg

395 ms

4_DW1o6EJDY.jpg

4_DW1o6EJDY.jpg

391 ms

53oSE0iYavU.jpg

53oSE0iYavU.jpg

408 ms

camera_50.png

camera_50.png

132 ms

w_logo.png

w_logo.png

127 ms

Accessibility Review

4zte.ru accessibility score

92

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

Best Practices

4zte.ru best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

4zte.ru SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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

4zte.ru

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