25.8 sec in total
779 ms
24.2 sec
836 ms
Visit economy.ae now to see the best up-to-date Economy content for United Arab Emirates and also check out these interesting facts you probably never knew about economy.ae
وزارة الاقتصاد - الإمارات العربية المتحدة, وزارة الاقتصاد أبوظبي ، وزارة الاقتصاد ، الإمارات العربية المتحدة, وزارة الاقتصاد الإمارات العربية المتحدة, وزارة الاقتصاد دبي
Visit economy.aeWe analyzed Economy.ae page load time and found that the first response time was 779 ms and then it took 25 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
economy.ae performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value31.4 s
0/100
25%
Value23.5 s
0/100
10%
Value7,630 ms
0/100
30%
Value0.071
96/100
15%
Value74.8 s
0/100
10%
779 ms
1872 ms
53 ms
602 ms
995 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Economy.ae, 49% (45 requests) were made to Moec.gov.ae and 14% (13 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Moec.gov.ae.
Page size can be reduced by 2.5 MB (72%)
3.5 MB
979.6 kB
In fact, the total size of Economy.ae 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. 65% of websites need less resources to load. Javascripts take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 334.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 89.9 kB, which is 24% 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 334.2 kB or 88% of the original size.
Potential reduce by 0 B
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. Economy images are well optimized though.
Potential reduce by 2.1 MB
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 2.1 MB or 70% of the original size.
Potential reduce by 76.1 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. Economy.ae needs all CSS files to be minified and compressed as it can save up to 76.1 kB or 85% of the original size.
Number of requests can be reduced by 50 (62%)
81
31
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Economy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
economy.ae
779 ms
www.moec.gov.ae
1872 ms
css2
53 ms
main.css
602 ms
combo
995 ms
clay.css
1189 ms
main.css
802 ms
combo
607 ms
js_loader_config
607 ms
combo
1021 ms
js_bundle_config
818 ms
main.css
1436 ms
lightgallery.min.css
55 ms
sharethis.js
38 ms
webReader.js
160 ms
api.js
55 ms
bootstrap-tourist.js
1028 ms
element.js
64 ms
gsap.min.js
64 ms
ScrollTrigger.min.js
72 ms
TweenMax.min.js
73 ms
slick.min.js
70 ms
aos.js
89 ms
jquery.simple-calendar.min.js
1017 ms
jquery.lazy.min.js
73 ms
highcharts.min.js
285 ms
timeline.min.js
216 ms
highcharts-more.min.js
345 ms
solid-gauge.min.js
244 ms
variable-pie.min.js
84 ms
jquery.autocomplete.min.js
12 ms
main.css
876 ms
main.css
875 ms
main.css
877 ms
main.css
877 ms
main.css
1048 ms
main.js
1048 ms
validatescript
875 ms
analytics.js
19 ms
collect
12 ms
js
63 ms
gtm.js
75 ms
0b47591f-892a-9d2b-f793-68ab282d4d11
211 ms
e65ecd5c-b002-0a3a-86a7-c1461c7cfd21
598 ms
75e95bfa-0c0e-acce-73e3-9560de7f8d91
211 ms
45a00930-eb39-d3da-74db-eb7164aed3a9
2187 ms
fdf8e9b4-6ea2-5a67-f536-8ac70ba0c5b8
794 ms
691938a3-4066-c166-cd8b-064a730c884e
14560 ms
1467ae68-6d1c-8f93-1aab-b4e1ec7b7149
19733 ms
5d79f4c8-e21d-6607-0afe-0dce73a9fa90
12124 ms
2bb76443-caa9-37df-267c-879b9fec1386
1421 ms
1c1035e1-8499-7d97-2853-2f58b21ae749
995 ms
fd41f05c-e85f-d244-7ac3-8b9b3214bb7e
1201 ms
ea351344-c031-3813-1814-17451e469ad4
1405 ms
56f06080-faf7-3ee1-ee22-789758e6e64d
1605 ms
news_default.jpg
1621 ms
11f3943c-7d00-bc4f-84bc-b633a6972f5c
1803 ms
customer-puls-white.svg
1822 ms
9aa1d696-06ab-84fd-7aba-912acf5760f4
2002 ms
739366c7-0774-f7eb-05b8-5c3ea395ab93
2031 ms
bbc79a65-608b-1279-0bec-1fda7cdadea7
2199 ms
23cdc63b-1b77-957b-2900-274d6cd9109d
2233 ms
recaptcha__en.js
40 ms
SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-W1ToLQ-GokM.ttf
500 ms
SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hL4-W1ToLQ-GokM.ttf
575 ms
SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hD45W1ToLQ-GokM.ttf
608 ms
SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5W1ToLQ-GokM.ttf
641 ms
moeicon.woff
2881 ms
personas.png
2229 ms
fontawesome-webfont.woff
2240 ms
2346 ms
205 ms
200 ms
399 ms
cxinfinity.webchat.fonts.css
198 ms
styles.78d3b70a40393864.css
781 ms
577 ms
runtime.e4c00ac033765e06.js
578 ms
polyfills.d7cd6a79e741a700.js
580 ms
scripts.4c32cb05ebfdcec7.js
1182 ms
main.3202d2685a9419eb.js
1954 ms
fallback
32 ms
fallback
61 ms
fallback__ltr.css
4 ms
css
28 ms
logo_48.png
38 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
13 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
11 ms
customerChatConfig.json
198 ms
tafseel
199 ms
tafseel
246 ms
tafseel
201 ms
economy.ae accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
economy.ae best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
economy.ae SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
AR
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Economy.ae can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it matches the claimed language. Our system also found out that Economy.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.
economy.ae
Open Graph description is not detected on the main page of Economy. 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: