2.6 sec in total
281 ms
1.9 sec
408 ms
Click here to check amazing Ecorp content. Otherwise, check out these important facts you probably never knew about ecorp.com
Join our exclusive community of like minded people on ecorp.com
Visit ecorp.comWe analyzed Ecorp.com page load time and found that the first response time was 281 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ecorp.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value3.6 s
60/100
25%
Value7.7 s
25/100
10%
Value190 ms
91/100
30%
Value0.009
100/100
15%
Value15.8 s
6/100
10%
281 ms
108 ms
136 ms
58 ms
43 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 59% of them (41 requests) were addressed to the original Ecorp.com, 7% (5 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (591 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 1.2 MB (34%)
3.5 MB
2.3 MB
In fact, the total size of Ecorp.com main page is 3.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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 27.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. This page needs HTML code to be minified as it can gain 7.9 kB, which is 22% 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 27.7 kB or 79% of the original size.
Potential reduce by 15.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. Ecorp images are well optimized though.
Potential reduce by 586.5 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 586.5 kB or 74% of the original size.
Potential reduce by 571.2 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. Ecorp.com needs all CSS files to be minified and compressed as it can save up to 571.2 kB or 88% of the original size.
Number of requests can be reduced by 47 (78%)
60
13
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecorp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
ecorp.com
281 ms
animate.css
108 ms
bootstrap.css
136 ms
et-line-icons.css
58 ms
font-awesome.min.css
43 ms
extralayers.css
103 ms
settings.css
187 ms
magnific-popup.css
58 ms
owl.carousel.css
74 ms
owl.transitions.css
75 ms
full-slider.css
95 ms
text-effect.css
108 ms
style.css
208 ms
style-ver2.css
115 ms
responsive.css
152 ms
jquery.min.js
105 ms
bootstrap.min.js
48 ms
jquery.counter-analog.css
121 ms
jquery.counter-analog2.css
141 ms
widgets.js
18 ms
modernizr.js
103 ms
bootstrap.js
128 ms
bootstrap-hover-dropdown.js
115 ms
jquery.easing.1.3.js
119 ms
skrollr.min.js
127 ms
jquery.viewport.mini.js
127 ms
smooth-scroll.js
135 ms
wow.min.js
148 ms
page-scroll.js
145 ms
jquery.easypiechart.js
148 ms
jquery.parallax-1.1.3.js
149 ms
jquery.isotope.min.js
195 ms
owl.carousel.min.js
158 ms
jquery.magnific-popup.min.js
177 ms
popup-gallery.js
174 ms
text-effect.js
175 ms
jquery.tools.min.js
195 ms
jquery.revolution.js
353 ms
counter.js
183 ms
jquery.fitvids.js
184 ms
imagesloaded.pkgd.min.js
187 ms
one-page-main.js
194 ms
main.js
344 ms
css
30 ms
css
39 ms
css
49 ms
ga.js
81 ms
piwik.js
133 ms
logo-ecorp2-2.png
80 ms
Rackspace_Cloud_Company_Logo_clr_300x109.jpg
168 ms
desc-eshares-lander-3.jpg
58 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
45 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
46 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
46 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
46 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
47 ms
et-line.woff
47 ms
fontawesome-webfont.woff
41 ms
__utm.gif
69 ms
like.php
189 ms
icon-move-light.png
64 ms
building3.jpg
224 ms
skyscrapers_blue_sky-wallpaper.jpg
154 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
42 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
25 ms
qeKvIRsJabD.js
524 ms
LVx-xkvaJ0b.png
591 ms
jot
102 ms
qeKvIRsJabD.js
203 ms
ecorp.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
ecorp.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ecorp.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecorp.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 Ecorp.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.
ecorp.com
Open Graph description is not detected on the main page of Ecorp. 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: