28.8 sec in total
5.4 sec
22.4 sec
1.1 sec
Click here to check amazing Ecepost content for Thailand. Otherwise, check out these important facts you probably never knew about ecepost.com
Visit ecepost.comWe analyzed Ecepost.com page load time and found that the first response time was 5.4 sec and then it took 23.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
ecepost.com performance score
5359 ms
878 ms
1024 ms
1217 ms
3459 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 86% of them (24 requests) were addressed to the original Ecepost.com, 7% (2 requests) were made to Staticxx.facebook.com and 4% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (16.9 sec) belongs to the original domain Ecepost.com.
Page size can be reduced by 142.3 kB (8%)
1.7 MB
1.6 MB
In fact, the total size of Ecepost.com main page is 1.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. 30% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 31.2 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 4.3 kB, which is 11% 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 31.2 kB or 80% of the original size.
Potential reduce by 107.8 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. Ecepost images are well optimized though.
Potential reduce by 3.3 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. Ecepost.com needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 78% of the original size.
We found no issues to fix!
27
27
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecepost. According to our analytics all requests are already optimized.
ecepost.com
5359 ms
research.css
878 ms
sdk.js
1024 ms
bgheader.jpg
1217 ms
header.jpg
3459 ms
702077017.jpg
4234 ms
702077016.jpg
16919 ms
702077015.jpg
5236 ms
702077014.jpg
5682 ms
702077013.jpg
5552 ms
702110008.jpg
4969 ms
702116001.jpg
6027 ms
30035018.jpg
7431 ms
702134004.jpg
5579 ms
702134003.jpg
8149 ms
11005189.jpg
8805 ms
702134002.jpg
5988 ms
702077012.jpg
12771 ms
702077011.jpg
7581 ms
702077010.jpg
9587 ms
702077009.jpg
8884 ms
702077008.jpg
9783 ms
30208035.jpg
11679 ms
30208034.jpg
10808 ms
30208033.jpg
11756 ms
150 ms
xd_arbiter.php
351 ms
xd_arbiter.php
597 ms
ecepost.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecepost.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ecepost.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.
ecepost.com
Open Graph description is not detected on the main page of Ecepost. 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: