21.2 sec in total
2.7 sec
17.1 sec
1.4 sec
Visit ecap.ae now to see the best up-to-date Ecap content and also check out these interesting facts you probably never knew about ecap.ae
Leadership Development and Executive Appointments Contact us Meet the team Board Advisory Strategic advice for new market entry and expansion Board placement and Board Formation Board Evaluation and...
Visit ecap.aeWe analyzed Ecap.ae page load time and found that the first response time was 2.7 sec and then it took 18.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
ecap.ae performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value9.9 s
0/100
25%
Value10.6 s
7/100
10%
Value770 ms
38/100
30%
Value0
100/100
15%
Value9.3 s
31/100
10%
2709 ms
845 ms
826 ms
1378 ms
878 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ecap.ae, 9% (9 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7.1 sec) relates to the external source Teamecap.com.
Page size can be reduced by 343.3 kB (11%)
3.2 MB
2.8 MB
In fact, the total size of Ecap.ae main page is 3.2 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. 60% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 149.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. 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 149.2 kB or 85% of the original size.
Potential reduce by 191.7 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. Ecap images are well optimized though.
Potential reduce by 150 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Ecap.ae has all CSS files already compressed.
Number of requests can be reduced by 50 (59%)
85
35
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecap. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
teamecap.com
2709 ms
style.min.css
845 ms
theme.min.css
826 ms
frontend-lite.min.css
1378 ms
post-5.css
878 ms
elementor-icons.min.css
1047 ms
swiper.min.css
841 ms
frontend-lite.min.css
1648 ms
global.css
1664 ms
post-47.css
1668 ms
post-7.css
1696 ms
post-49.css
1902 ms
css
37 ms
fontawesome.min.css
2228 ms
solid.min.css
2433 ms
brands.min.css
2465 ms
jquery.min.js
2502 ms
jquery-migrate.min.js
2516 ms
widget-nav-menu.min.css
2927 ms
widget-icon-list.min.css
3034 ms
widget-carousel.min.css
3251 ms
widget-loop-builder.min.css
3483 ms
widget-theme-elements.min.css
3344 ms
post-7391.css
3346 ms
animations.min.css
3988 ms
css
33 ms
wpforms-full.min.css
4230 ms
hello-frontend.min.js
4095 ms
premium-wrapper-link.min.js
4168 ms
jquery.smartmenus.min.js
4184 ms
jquery-numerator.min.js
4349 ms
imagesloaded.min.js
4795 ms
webpack-pro.runtime.min.js
4924 ms
webpack.runtime.min.js
5016 ms
frontend-modules.min.js
5027 ms
wp-polyfill-inert.min.js
5017 ms
regenerator-runtime.min.js
5124 ms
wp-polyfill.min.js
6226 ms
hooks.min.js
5709 ms
i18n.min.js
5041 ms
frontend.min.js
5176 ms
waypoints.min.js
5014 ms
core.min.js
5084 ms
frontend.min.js
5518 ms
elements-handlers.min.js
5484 ms
underscore.min.js
5023 ms
wp-util.min.js
5145 ms
frontend.min.js
5153 ms
jquery.validate.min.js
5557 ms
mailcheck.min.js
5447 ms
punycode.min.js
5253 ms
utils.min.js
5227 ms
wpforms.min.js
5174 ms
ecap_black.png
5140 ms
why_ecap.jpg
6181 ms
Thinking-patterns.png
5206 ms
Engagement.png
5301 ms
Variations.png
5206 ms
Image1.jpg
5521 ms
Image1-1.jpg
5334 ms
Image1-2.jpg
5481 ms
Image1-3.jpg
5533 ms
Image1-4.jpg
5504 ms
Image1-5.jpg
5730 ms
unsplash_K0c8ko3e6AA.jpg
5723 ms
Image1.jpg
5129 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf
23 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf
61 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf
107 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf
91 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf
106 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf
109 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf
106 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf
107 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf
105 ms
fa-solid-900.woff
6073 ms
fa-brands-400.woff
5858 ms
Image1-1.jpg
5830 ms
image-1.jpg
5795 ms
global.png
6504 ms
Client.png
6254 ms
homepage-map.png
6359 ms
pin.png
5770 ms
1700568175005.png
6333 ms
Aaron-new.png
6468 ms
1697653282513.jpeg
6757 ms
Damian.png
6816 ms
Frame-180-1.png
6046 ms
favicon-1.png
5788 ms
submit-spin.svg
6358 ms
Rectangle-165.png
6341 ms
icon-button.png
6336 ms
Group-149.png
6269 ms
Rectangle-104.png
7108 ms
Rectangle-105.png
6903 ms
Rectangle-107.png
6537 ms
bg_service.png
6309 ms
ecap.ae accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
ecap.ae best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ecap.ae SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecap.ae can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ecap.ae 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.
ecap.ae
Open Graph data is detected on the main page of Ecap. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: