Tools & Wizards About Us
ec1.com.ph screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ec1.com.ph

Loading...

Page Load Speed

4.3 sec in total

First Response

222 ms

Resources Loaded

3.7 sec

Page Rendered

369 ms

ec1.com.ph screenshot

About Website

Welcome to ec1.com.ph homepage info - get ready to check Ec 1 best content right away, or after learning these important things about ec1.com.ph

Visit ec1.com.ph

Key Findings

We analyzed Ec1.com.ph page load time and found that the first response time was 222 ms and then it took 4 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

ec1.com.ph performance score

0

Network Requests Diagram

ec1.com.ph

222 ms

commerceone.ec1.com.ph

2200 ms

flexslider.css

121 ms

font-awesome.min.css

133 ms

font-awesome.css

136 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ec1.com.ph, 78% (36 requests) were made to Commerceone.ec1.com.ph and 11% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Commerceone.ec1.com.ph.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (29%)

Content Size

5.4 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ec1.com.ph main page is 5.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. 50% of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 17.2 kB

  • Original 22.2 kB
  • After minification 18.8 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 3.5 kB, which is 16% 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 17.2 kB or 77% of the original size.

Image Optimization

-24%

Potential reduce by 1.2 MB

  • Original 5.0 MB
  • After minification 3.8 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. Obviously, Ec 1 needs image optimization as it can save up to 1.2 MB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 67.0 kB

  • Original 101.2 kB
  • After minification 99.6 kB
  • After compression 34.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 67.0 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 280.9 kB

  • Original 324.9 kB
  • After minification 281.3 kB
  • After compression 44.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. Ec1.com.ph needs all CSS files to be minified and compressed as it can save up to 280.9 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ec1.com.ph

ec1.com.ph

222 ms

commerceone.ec1.com.ph

commerceone.ec1.com.ph

2200 ms

flexslider.css

flexslider.css

121 ms

font-awesome.min.css

font-awesome.min.css

133 ms

font-awesome.css

font-awesome.css

136 ms

animate.css

animate.css

139 ms

css

css

23 ms

bootstrap.min.css

bootstrap.min.css

203 ms

main.css

main.css

142 ms

custom-styles.css

custom-styles.css

190 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

247 ms

jquery.min.js

jquery.min.js

32 ms

bootstrap.min.js

bootstrap.min.js

200 ms

main.js

main.js

216 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

217 ms

rotate.js

rotate.js

336 ms

logo.png

logo.png

172 ms

icon-livechat.jpg

icon-livechat.jpg

96 ms

icon-fb.jpg

icon-fb.jpg

95 ms

icon-twitter.jpg

icon-twitter.jpg

98 ms

icon-linkdn.jpg

icon-linkdn.jpg

96 ms

header1.jpg

header1.jpg

740 ms

header2.jpg

header2.jpg

584 ms

header3.jpg

header3.jpg

975 ms

header4.jpg

header4.jpg

908 ms

header5.jpg

header5.jpg

848 ms

header7.jpg

header7.jpg

775 ms

glyphicons-halflings.png

glyphicons-halflings.png

705 ms

grid_noise.png

grid_noise.png

772 ms

btn-viewproducts.png

btn-viewproducts.png

804 ms

img-exactglobenext.jpg

img-exactglobenext.jpg

838 ms

img-exactsynergyenterprise.jpg

img-exactsynergyenterprise.jpg

912 ms

img-orisoft.jpg

img-orisoft.jpg

938 ms

img-logo-footer.jpg

img-logo-footer.jpg

917 ms

icon-twitter-footer.png

icon-twitter-footer.png

919 ms

icon-linkdn-footer.png

icon-linkdn-footer.png

974 ms

icon-fb-footer.png

icon-fb-footer.png

979 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

891 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

896 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

27 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

27 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

28 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

26 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

27 ms

analytics.js

analytics.js

13 ms

collect

collect

13 ms

SEO Factors

ec1.com.ph 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 Ec1.com.ph 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 Ec1.com.ph 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

ec1.com.ph

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