Tools & Wizards About Us
api.ecwid.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

api.ecwid.com

Ecwid Developers API Documentation | Ecwid Developers

Page Load Speed

66.6 sec in total

First Response

15 ms

Resources Loaded

12.9 sec

Page Rendered

53.6 sec

api.ecwid.com screenshot

About Website

Visit api.ecwid.com now to see the best up-to-date API Ecwid content for United States and also check out these interesting facts you probably never knew about api.ecwid.com

With the help of Ecwid API, you can create an application that will extend Ecwid functionality in various ways.

Visit api.ecwid.com

Key Findings

We analyzed Api.ecwid.com page load time and found that the first response time was 15 ms and then it took 66.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

api.ecwid.com performance score

0

Network Requests Diagram

api.ecwid.com

15 ms

api-documentation

111 ms

css

97 ms

style.83bdea2c.css

96 ms

jquery-1.11.3.min.js

73 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Api.ecwid.com, 13% (8 requests) were made to Apis.google.com and 13% (8 requests) were made to Don16obqbay2c.cloudfront.net. The less responsive or slowest element that took the longest time to load (9.4 sec) relates to the external source Sftrack.searchforce.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (73%)

Content Size

1.5 MB

After Optimization

395.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Api.ecwid.com main page is 1.5 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. 55% of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 890.1 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 125.0 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 890.1 kB or 88% of the original size.

Image Optimization

-36%

Potential reduce by 105.1 kB

  • Original 293.4 kB
  • After minification 188.3 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. Obviously, API Ecwid needs image optimization as it can save up to 105.1 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-47%

Potential reduce by 68.1 kB

  • Original 145.7 kB
  • After minification 143.4 kB
  • After compression 77.6 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 68.1 kB or 47% of the original size.

CSS Optimization

-81%

Potential reduce by 21.5 kB

  • Original 26.4 kB
  • After minification 26.2 kB
  • After compression 5.0 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. Api.ecwid.com needs all CSS files to be minified and compressed as it can save up to 21.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (67%)

Requests Now

51

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of API 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 27 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

api.ecwid.com

api.ecwid.com

15 ms

api-documentation

api-documentation

111 ms

css

css

97 ms

style.83bdea2c.css

style.83bdea2c.css

96 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

73 ms

jquery.plugins.a5283b23.js

jquery.plugins.a5283b23.js

151 ms

screen.css

screen.css

147 ms

all_nosearch.js

all_nosearch.js

92 ms

functions.11f8d72a.js

functions.11f8d72a.js

703 ms

wp-embed.min.js

wp-embed.min.js

3 ms

gtm.js

gtm.js

1881 ms

navbar.png

navbar.png

593 ms

ecwid-buttons.png

ecwid-buttons.png

4080 ms

icon.png

icon.png

6875 ms

logo.png

logo.png

1417 ms

gray-app-store.svg

gray-app-store.svg

4042 ms

gray-google.svg

gray-google.svg

1415 ms

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

5233 ms

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

5454 ms

MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf

MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf

7306 ms

icomoon.ttf

icomoon.ttf

2622 ms

xjAJXh38I15wypJXxuGMBpp-63r6doWhTEbsfBIRJ7A.ttf

xjAJXh38I15wypJXxuGMBpp-63r6doWhTEbsfBIRJ7A.ttf

7306 ms

fontIcons.woff

fontIcons.woff

5451 ms

analytics.js

analytics.js

5413 ms

conversion_async.js

conversion_async.js

7266 ms

sfct.js

sfct.js

9437 ms

all.js

all.js

6876 ms

plusone.js

plusone.js

6814 ms

widgets.js

widgets.js

4946 ms

linkid.js

linkid.js

261 ms

101 ms

collect

collect

37 ms

collect

collect

187 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

50 ms

collect

collect

61 ms

collect

collect

96 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

63 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

108 ms

fastbutton

fastbutton

164 ms

156 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

76 ms

168 ms

xd_arbiter.php

xd_arbiter.php

656 ms

postmessageRelay

postmessageRelay

59 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

21 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

16 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

22 ms

rpc:shindig_random.js

rpc:shindig_random.js

31 ms

jot

jot

84 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

fbds.js

fbds.js

283 ms

watch.js

watch.js

728 ms

i.js

i.js

26 ms

12a19b058a28c5db7b722584d59e60e4f080e142.1.js

12a19b058a28c5db7b722584d59e60e4f080e142.1.js

61 ms

like.php

like.php

73 ms

65 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

487 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

550 ms

advert.gif

advert.gif

91 ms

1

1

92 ms

SEO Factors

api.ecwid.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

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

api.ecwid.com

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