Tools & Wizards About Us
api.sendible.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

api.sendible.com

Page Load Speed

2.6 sec in total

First Response

158 ms

Resources Loaded

2 sec

Page Rendered

444 ms

api.sendible.com screenshot

About Website

Click here to check amazing Api Sendible content for United States. Otherwise, check out these important facts you probably never knew about api.sendible.com

Sendible is a social media management, monitoring & analytics tool to help businesses find new customers & manage their social media presence. Try it for free.

Visit api.sendible.com

Key Findings

We analyzed Api.sendible.com page load time and found that the first response time was 158 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

api.sendible.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

api.sendible.com

158 ms

1039410109.js

146 ms

system.css

211 ms

facebox.css

234 ms

thickbox.css

388 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 12% of them (13 requests) were addressed to the original Api.sendible.com, 50% (57 requests) were made to S3.amazonaws.com and 10% (11 requests) were made to Sendible-public.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (651 ms) relates to the external source S3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 462.7 kB (33%)

Content Size

1.4 MB

After Optimization

919.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Api.sendible.com main page is 1.4 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. Images take 883.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 34.3 kB

  • Original 43.2 kB
  • After minification 37.9 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 12% 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 34.3 kB or 79% of the original size.

Image Optimization

-14%

Potential reduce by 127.8 kB

  • Original 883.4 kB
  • After minification 755.6 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 Sendible needs image optimization as it can save up to 127.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 149.7 kB

  • Original 274.4 kB
  • After minification 271.3 kB
  • After compression 124.7 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 149.7 kB or 55% of the original size.

CSS Optimization

-83%

Potential reduce by 151.0 kB

  • Original 180.9 kB
  • After minification 166.2 kB
  • After compression 29.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. Api.sendible.com needs all CSS files to be minified and compressed as it can save up to 151.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (47%)

Requests Now

95

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

api.sendible.com

api.sendible.com

158 ms

1039410109.js

1039410109.js

146 ms

system.css

system.css

211 ms

facebox.css

facebox.css

234 ms

thickbox.css

thickbox.css

388 ms

datepicker.css

datepicker.css

213 ms

tooltip.css

tooltip.css

207 ms

nivo-slider.css

nivo-slider.css

234 ms

nivo-sendible.css

nivo-sendible.css

211 ms

bootstrap.min.css

bootstrap.min.css

215 ms

public.min.css

public.min.css

74 ms

jsapi

jsapi

243 ms

thickbox.js

thickbox.js

227 ms

jquery.tooltip.min.js

jquery.tooltip.min.js

229 ms

jquery.validate.min.js

jquery.validate.min.js

251 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

230 ms

jquery.fancybox-1.3.3.css

jquery.fancybox-1.3.3.css

76 ms

jquery.fancybox-1.3.3.pack.js

jquery.fancybox-1.3.3.pack.js

76 ms

facebox.js

facebox.js

23 ms

jquery.timers.js

jquery.timers.js

24 ms

tracker.js

tracker.js

150 ms

ga.js

ga.js

73 ms

quant.js

quant.js

39 ms

jquery.min.js

jquery.min.js

29 ms

sendible_72.png

sendible_72.png

50 ms

insights24.png

insights24.png

163 ms

button_arrow.png

button_arrow.png

151 ms

bg-section.jpg

bg-section.jpg

120 ms

plans-orange.png

plans-orange.png

151 ms

footer-bg.png

footer-bg.png

161 ms

tour_messagebox_450.png

tour_messagebox_450.png

106 ms

tour_inbox_450.png

tour_inbox_450.png

114 ms

tour_mentions_450.png

tour_mentions_450.png

98 ms

tour_scheduling_450.png

tour_scheduling_450.png

98 ms

tour_facebook_450.png

tour_facebook_450.png

114 ms

tour_analytics_450.png

tour_analytics_450.png

147 ms

tour_email_450.png

tour_email_450.png

143 ms

tour_reports_450.png

tour_reports_450.png

338 ms

bg-items1.png

bg-items1.png

240 ms

icon1.png

icon1.png

150 ms

icon2.png

icon2.png

177 ms

icon3.png

icon3.png

177 ms

icon4.png

icon4.png

184 ms

mail32_blue.png

mail32_blue.png

186 ms

bargraph32_blue.png

bargraph32_blue.png

235 ms

commentblack32_blue.png

commentblack32_blue.png

194 ms

risegraph32_blue.png

risegraph32_blue.png

236 ms

clock32_blue.png

clock32_blue.png

209 ms

users32_blue.png

users32_blue.png

236 ms

logo1.gif

logo1.gif

245 ms

logo2.gif

logo2.gif

278 ms

logo3.gif

logo3.gif

251 ms

logo4.gif

logo4.gif

251 ms

logo5.gif

logo5.gif

274 ms

logo6.gif

logo6.gif

268 ms

logo7.gif

logo7.gif

321 ms

icon-zoom.png

icon-zoom.png

296 ms

tour_inbox_400.png

tour_inbox_400.png

302 ms

tour_email_stats_400.png

tour_email_stats_400.png

311 ms

tour_analytics_400.png

tour_analytics_400.png

312 ms

tour_mentions_400.png

tour_mentions_400.png

331 ms

quotes_1.gif

quotes_1.gif

326 ms

quotes_2.gif

quotes_2.gif

353 ms

thumb.png

thumb.png

516 ms

thumb.png

thumb.png

537 ms

loading.gif

loading.gif

45 ms

messages.png

messages.png

44 ms

search.png

search.png

43 ms

chart_up.png

chart_up.png

43 ms

chart.png

chart.png

43 ms

content-bg.jpg

content-bg.jpg

123 ms

big_button_arrow.png

big_button_arrow.png

146 ms

flag_US.png

flag_US.png

129 ms

flag_GB.png

flag_GB.png

123 ms

Flag_AU.png

Flag_AU.png

125 ms

__utm.gif

__utm.gif

55 ms

pixel;r=1122191114;a=p-9bpiFWpUmAL46;fpan=1;fpa=P0-844864458-1456877344347;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456877344346;tzo=-180;ref=;url=http%3A%2F%2Fapi.sendible.com%2F;ogl=

pixel;r=1122191114;a=p-9bpiFWpUmAL46;fpan=1;fpa=P0-844864458-1456877344347;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456877344346;tzo=-180;ref=;url=http%3A%2F%2Fapi.sendible.com%2F;ogl=

28 ms

wc.js

wc.js

121 ms

thumb.jpg

thumb.jpg

600 ms

thumb.png

thumb.png

291 ms

thumb.jpg

thumb.jpg

291 ms

thumb.jpg

thumb.jpg

459 ms

thumb.png

thumb.png

584 ms

thumb.gif

thumb.gif

445 ms

thumb.jpg

thumb.jpg

413 ms

thumb.png

thumb.png

651 ms

bg-block.gif

bg-block.gif

442 ms

loadingAnimation.gif

loadingAnimation.gif

14 ms

fancy_nav_left.png

fancy_nav_left.png

56 ms

roundtrip.js

roundtrip.js

8 ms

1274-343-10-1304.js

1274-343-10-1304.js

39 ms

fancy_nav_right.png

fancy_nav_right.png

49 ms

bullets.png

bullets.png

50 ms

c

c

205 ms

application2.js

application2.js

217 ms

4BJ5JASKSBAEHBETYOEOMR.js

4BJ5JASKSBAEHBETYOEOMR.js

135 ms

out

out

18 ms

tr

tr

60 ms

33 ms

60 ms

tr

tr

59 ms

u.php

u.php

130 ms

125 ms

sync

sync

103 ms

adsct

adsct

193 ms

pixel

pixel

118 ms

95 ms

377928.gif

377928.gif

27 ms

sd

sd

27 ms

tap.php

tap.php

40 ms

in

in

15 ms

storage.html

storage.html

125 ms

storage.js

storage.js

58 ms

Accessibility Review

api.sendible.com accessibility score

79

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

Best Practices

api.sendible.com best practices score

83

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

Page has valid source maps

SEO Factors

api.sendible.com SEO score

81

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.sendible.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Api.sendible.com 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

api.sendible.com

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