Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

2.7 sec in total

First Response

143 ms

Resources Loaded

2.1 sec

Page Rendered

437 ms

sending.io screenshot

About Website

Click here to check amazing Sending content for Spain. Otherwise, check out these important facts you probably never knew about sending.io

Visit sending.io

Key Findings

We analyzed Sending.io page load time and found that the first response time was 143 ms and then it took 2.6 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

sending.io performance score

0

Network Requests Diagram

sending.io

143 ms

www.sending.io

367 ms

css

102 ms

main_show-65e4560203fc7c41400111243191df1f.css

43 ms

jquery.min.js

156 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Sending.io, 33% (26 requests) were made to Assets.strikingly.com and 10% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (597 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (57%)

Content Size

2.3 MB

After Optimization

979.2 kB

In fact, the total size of Sending.io main page is 2.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. 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. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 96.6 kB

  • Original 120.3 kB
  • After minification 120.2 kB
  • After compression 23.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 96.6 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 9.5 kB

  • Original 677.5 kB
  • After minification 668.0 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. Sending images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 907.1 kB

  • Original 1.2 MB
  • After minification 798.3 kB
  • After compression 244.8 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 907.1 kB or 79% of the original size.

CSS Optimization

-88%

Potential reduce by 301.7 kB

  • Original 344.4 kB
  • After minification 344.1 kB
  • After compression 42.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. Sending.io needs all CSS files to be minified and compressed as it can save up to 301.7 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (52%)

Requests Now

62

After Optimization

30

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

SEO Factors

sending.io SEO score

0

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 Sending.io 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 Sending.io 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

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