Tools & Wizards About Us
ecwid.ru screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

ecwid.ru

#1 Free Ecommerce Shopping Cart & Free Online Store - Try Ecwid!

Page Load Speed

3.8 sec in total

First Response

30 ms

Resources Loaded

3.1 sec

Page Rendered

649 ms

ecwid.ru screenshot

About Website

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

We’re putting free trials on trial. With Ecwid, you get free FOREVER. Set up your free account once, and keep it as long as you like. Seriously.

Visit ecwid.ru

Key Findings

We analyzed Ecwid.ru page load time and found that the first response time was 30 ms and then it took 3.8 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

ecwid.ru performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value5,000 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value29.8 s

0/100

10%

Network Requests Diagram

ecwid.ru

30 ms

www.ecwid.ru

56 ms

css

63 ms

css

75 ms

style.15d68afe.css

819 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Ecwid.ru, 35% (31 requests) were made to Ecwid-site-ru.r.worldssl.net and 8% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Ecwid-site-ru.r.worldssl.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 143.1 kB (7%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ecwid.ru main page is 2.0 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. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 49.6 kB

  • Original 65.6 kB
  • After minification 65.6 kB
  • After compression 15.9 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 49.6 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 5.6 kB

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

JavaScript Optimization

-48%

Potential reduce by 87.2 kB

  • Original 181.4 kB
  • After minification 181.4 kB
  • After compression 94.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 87.2 kB or 48% of the original size.

CSS Optimization

-58%

Potential reduce by 694 B

  • Original 1.2 kB
  • After minification 1.1 kB
  • After compression 508 B

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. Ecwid.ru needs all CSS files to be minified and compressed as it can save up to 694 B or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (51%)

Requests Now

80

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ecwid.ru

ecwid.ru

30 ms

www.ecwid.ru

www.ecwid.ru

56 ms

css

css

63 ms

css

css

75 ms

style.15d68afe.css

style.15d68afe.css

819 ms

abtesting.4e151553.js

abtesting.4e151553.js

588 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

26 ms

showcases.block.179985e3.js

showcases.block.179985e3.js

583 ms

functions.95730cb1.js

functions.95730cb1.js

584 ms

functions.6bc77514.js

functions.6bc77514.js

588 ms

wp-embed.min.js

wp-embed.min.js

19 ms

logo_ecwid_named.svg

logo_ecwid_named.svg

182 ms

ipad-store-mobile2.png

ipad-store-mobile2.png

684 ms

ipad-store2.png

ipad-store2.png

789 ms

sell-everywhere-mobile.svg

sell-everywhere-mobile.svg

180 ms

sell-everywhere-ru.png

sell-everywhere-ru.png

395 ms

vk-icon.svg

vk-icon.svg

311 ms

fbstore-icons.png

fbstore-icons.png

310 ms

vkstore.png

vkstore.png

814 ms

responsive-grow-mobile.svg

responsive-grow-mobile.svg

454 ms

iphone7.png

iphone7.png

849 ms

ru-services-mobile.svg

ru-services-mobile.svg

525 ms

ru-services.svg

ru-services.svg

583 ms

vk-icon.svg

vk-icon.svg

653 ms

gtm.js

gtm.js

132 ms

store-background.jpg

store-background.jpg

1094 ms

shelf-background.jpg

shelf-background.jpg

891 ms

belolapk.jpg

belolapk.jpg

1025 ms

wishnya.jpg

wishnya.jpg

1023 ms

tbt.jpg

tbt.jpg

1046 ms

AFOUR.jpg

AFOUR.jpg

1092 ms

nastol.jpg

nastol.jpg

1409 ms

kokosina1.jpg

kokosina1.jpg

1541 ms

shaltai.jpg

shaltai.jpg

1153 ms

kinfolk.jpg

kinfolk.jpg

1173 ms

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

130 ms

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

176 ms

MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf

MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf

177 ms

fontIcons.woff

fontIcons.woff

127 ms

global_map.svg

global_map.svg

1153 ms

coffee_background.jpg

coffee_background.jpg

1419 ms

flags.1.png

flags.1.png

1334 ms

kama_postviews.php

kama_postviews.php

175 ms

analytics.js

analytics.js

121 ms

conversion_async.js

conversion_async.js

74 ms

sfct.js

sfct.js

338 ms

watch.js

watch.js

448 ms

58 ms

linkid.js

linkid.js

13 ms

collect

collect

23 ms

collect

collect

57 ms

37 ms

fbds.js

fbds.js

44 ms

103 ms

advert.gif

advert.gif

84 ms

1

1

84 ms

all.js

all.js

32 ms

plusone.js

plusone.js

151 ms

widgets.js

widgets.js

192 ms

44 ms

tracking-source.214c9ba7.js

tracking-source.214c9ba7.js

123 ms

tracking-test.074f1a60.js

tracking-test.074f1a60.js

145 ms

64 ms

i.js

i.js

81 ms

12a19b058a28c5db7b722584d59e60e4f080e142.1.js

12a19b058a28c5db7b722584d59e60e4f080e142.1.js

142 ms

87 ms

xd_arbiter.php

xd_arbiter.php

128 ms

like.php

like.php

91 ms

collect

collect

25 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

35 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

90 ms

fastbutton

fastbutton

114 ms

MFCZDR38nxn.js

MFCZDR38nxn.js

149 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

156 ms

tracking-source

tracking-source

255 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

67 ms

postmessageRelay

postmessageRelay

105 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

29 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

29 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

40 ms

follow_button.6a78875565a912489e9aef879c881358.ru.html

follow_button.6a78875565a912489e9aef879c881358.ru.html

48 ms

api.js

api.js

28 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

73 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

58 ms

tracking-source.59902e81.js

tracking-source.59902e81.js

34 ms

jot

jot

104 ms

tracking-test

tracking-test

92 ms

tracking-test.83d5319d.js

tracking-test.83d5319d.js

12 ms

Accessibility Review

ecwid.ru accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ecwid.ru best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

High

Page is blocked from indexing

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecwid.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 Ecwid.ru main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ecwid.ru

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