Tools & Wizards About Us
phonedo.ru screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

phonedo.ru

Phonedo.ru - Смартфоны по дружелюбным ценам в Смоленске

Page Load Speed

7.7 sec in total

First Response

373 ms

Resources Loaded

6.8 sec

Page Rendered

590 ms

phonedo.ru screenshot

About Website

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

Phonedo.ru - Смартфоны и техника по дружелюбным ценам Смоленске! Только новый, оригинальный и качественный товар, гарантия

Visit phonedo.ru

Key Findings

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

Performance Metrics

phonedo.ru performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value44.1 s

0/100

25%

SI (Speed Index)

Value30.9 s

0/100

10%

TBT (Total Blocking Time)

Value7,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.326

35/100

15%

TTI (Time to Interactive)

Value51.4 s

0/100

10%

Network Requests Diagram

phonedo.ru

373 ms

www.phonedo.ru

2240 ms

295ca2263622942e6ab1644b51de5d4c

1878 ms

bootstrap.min.css

700 ms

popper.min.js

29 ms

Our browser made a total of 167 requests to load all elements on the main page. We found that 93% of them (155 requests) were addressed to the original Phonedo.ru, 2% (4 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Phonedo.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (44%)

Content Size

5.7 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phonedo.ru main page is 5.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 271.4 kB

  • Original 321.1 kB
  • After minification 309.4 kB
  • After compression 49.7 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 271.4 kB or 85% of the original size.

Image Optimization

-13%

Potential reduce by 347.7 kB

  • Original 2.7 MB
  • After minification 2.3 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. Obviously, Phonedo needs image optimization as it can save up to 347.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 1.3 MB

  • Original 2.0 MB
  • After minification 2.0 MB
  • After compression 669.3 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 1.3 MB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 531.7 kB

  • Original 648.4 kB
  • After minification 605.5 kB
  • After compression 116.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. Phonedo.ru needs all CSS files to be minified and compressed as it can save up to 531.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (61%)

Requests Now

157

After Optimization

62

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phonedo.ru

phonedo.ru

373 ms

www.phonedo.ru

www.phonedo.ru

2240 ms

295ca2263622942e6ab1644b51de5d4c

295ca2263622942e6ab1644b51de5d4c

1878 ms

bootstrap.min.css

bootstrap.min.css

700 ms

popper.min.js

popper.min.js

29 ms

bootstrap.min.js

bootstrap.min.js

588 ms

font-awesome.min.css

font-awesome.min.css

470 ms

sgr.css

sgr.css

359 ms

style.min.css

style.min.css

840 ms

frontend.css

frontend.css

516 ms

shortcodes.css

shortcodes.css

588 ms

styles.css

styles.css

633 ms

public.min.css

public.min.css

771 ms

woo-related-products-public.css

woo-related-products-public.css

734 ms

xoo-wsc-fonts.css

xoo-wsc-fonts.css

734 ms

xoo-wsc-style.css

xoo-wsc-style.css

761 ms

slick.css

slick.css

812 ms

style.css

style.css

814 ms

woocommerce.css

woocommerce.css

824 ms

woocommerce-layout.css

woocommerce-layout.css

890 ms

css

css

43 ms

genericons.css

genericons.css

899 ms

style.css

style.css

932 ms

wc_predictive_search.css

wc_predictive_search.css

931 ms

wc_predictive_search.min.css

wc_predictive_search.min.css

941 ms

jquery.min.js

jquery.min.js

1074 ms

jquery-migrate.min.js

jquery-migrate.min.js

1017 ms

sgr.js

sgr.js

1026 ms

md5.js

md5.js

1046 ms

util.js

util.js

1045 ms

public.min.js

public.min.js

1175 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1145 ms

add-to-cart.min.js

add-to-cart.min.js

1152 ms

js.cookie.min.js

js.cookie.min.js

1160 ms

woocommerce.min.js

woocommerce.min.js

1044 ms

xoo-wsc-main.js

xoo-wsc-main.js

1168 ms

css

css

18 ms

font-awesome.css

font-awesome.css

906 ms

load_products.css

load_products.css

906 ms

wc-blocks.css

wc-blocks.css

905 ms

sgr_hide.css

sgr_hide.css

904 ms

rs6.css

rs6.css

918 ms

accounting.min.js

accounting.min.js

892 ms

api.js

api.js

65 ms

selectWoo.full.min.js

selectWoo.full.min.js

1065 ms

yith-wcan-shortcodes.min.js

yith-wcan-shortcodes.min.js

911 ms

index.js

index.js

842 ms

index.js

index.js

840 ms

rbtools.min.js

rbtools.min.js

940 ms

rs6.min.js

rs6.min.js

976 ms

sourcebuster.min.js

sourcebuster.min.js

836 ms

order-attribution.min.js

order-attribution.min.js

838 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

811 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

889 ms

wp-polyfill.min.js

wp-polyfill.min.js

983 ms

react.min.js

react.min.js

848 ms

hooks.min.js

hooks.min.js

839 ms

deprecated.min.js

deprecated.min.js

824 ms

dom.min.js

dom.min.js

921 ms

react-dom.min.js

react-dom.min.js

914 ms

escape-html.min.js

escape-html.min.js

933 ms

element.min.js

element.min.js

933 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

923 ms

i18n.min.js

i18n.min.js

860 ms

keycodes.min.js

keycodes.min.js

853 ms

priority-queue.min.js

priority-queue.min.js

849 ms

compose.min.js

compose.min.js

882 ms

private-apis.min.js

private-apis.min.js

836 ms

redux-routine.min.js

redux-routine.min.js

1262 ms

data.min.js

data.min.js

842 ms

lodash.min.js

lodash.min.js

952 ms

wc-blocks-registry.js

wc-blocks-registry.js

849 ms

url.min.js

url.min.js

770 ms

api-fetch.min.js

api-fetch.min.js

768 ms

wc-settings.js

wc-settings.js

824 ms

data-controls.min.js

data-controls.min.js

838 ms

html-entities.min.js

html-entities.min.js

894 ms

notices.min.js

notices.min.js

884 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

873 ms

wc-blocks-data.js

wc-blocks-data.js

878 ms

dom-ready.min.js

dom-ready.min.js

820 ms

a11y.min.js

a11y.min.js

892 ms

primitives.min.js

primitives.min.js

883 ms

warning.min.js

warning.min.js

782 ms

blocks-components.js

blocks-components.js

791 ms

blocks-checkout.js

blocks-checkout.js

800 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

875 ms

taiPGmVuC4y96PFeqp8sqomI-g.woff

taiPGmVuC4y96PFeqp8sqomI-g.woff

135 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

220 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

239 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

241 ms

imagesloaded.min.js

imagesloaded.min.js

873 ms

masonry.min.js

masonry.min.js

803 ms

jquery.masonry.min.js

jquery.masonry.min.js

819 ms

functions.js

functions.js

813 ms

underscore.min.js

underscore.min.js

825 ms

backbone.min.js

backbone.min.js

868 ms

backbone.localStorage.js

backbone.localStorage.js

764 ms

jquery.autocomplete.js

jquery.autocomplete.js

770 ms

predictive-search.backbone.js

predictive-search.backbone.js

749 ms

predictive-search-popup.backbone.min.js

predictive-search-popup.backbone.min.js

737 ms

load_products.js

load_products.js

785 ms

pfdintextcondpro-light.woff

pfdintextcondpro-light.woff

873 ms

Woo-Side-Cart.woff

Woo-Side-Cart.woff

863 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

864 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

852 ms

logo.png

logo.png

816 ms

basket.png

basket.png

873 ms

p.png

p.png

854 ms

dummy.png

dummy.png

837 ms

1.png

1.png

794 ms

3.png

3.png

794 ms

2.png

2.png

740 ms

90-267x400.png

90-267x400.png

797 ms

89-267x400.png

89-267x400.png

1092 ms

85-267x400.png

85-267x400.png

796 ms

87-267x400.png

87-267x400.png

773 ms

86-267x400.png

86-267x400.png

738 ms

83-267x400.png

83-267x400.png

740 ms

82-267x400.png

82-267x400.png

787 ms

79-267x400.png

79-267x400.png

767 ms

77-267x400.png

77-267x400.png

776 ms

90.png

90.png

774 ms

89-173x260.png

89-173x260.png

761 ms

85-173x260.png

85-173x260.png

782 ms

90-173x260.png

90-173x260.png

775 ms

87-173x260.png

87-173x260.png

767 ms

43-267x400.png

43-267x400.png

815 ms

05-267x400.png

05-267x400.png

784 ms

03-267x400.png

03-267x400.png

824 ms

65-267x400.png

65-267x400.png

819 ms

54-267x400.png

54-267x400.png

799 ms

07-267x400.png

07-267x400.png

779 ms

15-267x400.png

15-267x400.png

799 ms

31-267x400.png

31-267x400.png

813 ms

25-267x400.png

25-267x400.png

817 ms

21-267x400.png

21-267x400.png

849 ms

11-267x400.png

11-267x400.png

753 ms

tag.js

tag.js

945 ms

12-267x400.png

12-267x400.png

746 ms

43.png

43.png

783 ms

05.png

05.png

807 ms

03-173x260.png

03-173x260.png

791 ms

65-173x260.png

65-173x260.png

778 ms

54-173x260.png

54-173x260.png

734 ms

07-173x260.png

07-173x260.png

770 ms

2022-02-21_13-41-42.png

2022-02-21_13-41-42.png

792 ms

2022-02-21_13-42-00.png

2022-02-21_13-42-00.png

932 ms

2022-02-21_13-42-14-1.png

2022-02-21_13-42-14-1.png

931 ms

iphone-12-pro-colors-scaled.jpg

iphone-12-pro-colors-scaled.jpg

896 ms

mi.png

mi.png

872 ms

samsung.png

samsung.png

851 ms

apple.png

apple.png

843 ms

huawei.png

huawei.png

834 ms

oneplus.png

oneplus.png

833 ms

sony.png

sony.png

786 ms

%D0%91%D0%B5%D0%B7-%D0%BD%D0%B0%D0%B7%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F-150x150.png

%D0%91%D0%B5%D0%B7-%D0%BD%D0%B0%D0%B7%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F-150x150.png

744 ms

knowledge_graph_logo-150x150.png

knowledge_graph_logo-150x150.png

780 ms

1_large.png

1_large.png

765 ms

32.jpg

32.jpg

773 ms

LOiz65uEV2I-%E2%80%94-%D0%BA%D0%BE%D0%BF%D0%B8%D1%8F-150x150.jpg

LOiz65uEV2I-%E2%80%94-%D0%BA%D0%BE%D0%BF%D0%B8%D1%8F-150x150.jpg

783 ms

%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5_viber_2019-10-04_15-01-01.jpg

%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5_viber_2019-10-04_15-01-01.jpg

725 ms

dostavka.png

dostavka.png

725 ms

instock1.png

instock1.png

782 ms

polosa-h6.png

polosa-h6.png

751 ms

advert.gif

advert.gif

680 ms

sync_cookie_image_decide

sync_cookie_image_decide

172 ms

Accessibility Review

phonedo.ru accessibility score

88

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

phonedo.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

phonedo.ru SEO score

84

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Phonedo.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 Phonedo.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

phonedo.ru

Open Graph data is detected on the main page of Phonedo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: