9.4 sec in total
454 ms
7.9 sec
983 ms
Visit mintleaf.ae now to see the best up-to-date Mintleaf content and also check out these interesting facts you probably never knew about mintleaf.ae
Enjoy a night out with delicious food and drinks at one of the best Indian fine dining restaurants in Dubai – Mint Leaf!
Visit mintleaf.aeWe analyzed Mintleaf.ae page load time and found that the first response time was 454 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
mintleaf.ae performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.9 s
28/100
25%
Value7.7 s
24/100
10%
Value360 ms
72/100
30%
Value0.213
58/100
15%
Value9.0 s
33/100
10%
454 ms
166 ms
82 ms
187 ms
284 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 50% of them (45 requests) were addressed to the original Mintleaf.ae, 13% (12 requests) were made to Maps.googleapis.com and 12% (11 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Google.com.
Page size can be reduced by 244.5 kB (9%)
2.8 MB
2.6 MB
In fact, the total size of Mintleaf.ae main page is 2.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 69.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 69.2 kB or 83% of the original size.
Potential reduce by 39.3 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. Mintleaf images are well optimized though.
Potential reduce by 49.0 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 49.0 kB or 15% of the original size.
Potential reduce by 87.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. Mintleaf.ae needs all CSS files to be minified and compressed as it can save up to 87.0 kB or 55% of the original size.
Number of requests can be reduced by 31 (40%)
78
47
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mintleaf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
mintleaf.ae
454 ms
gtm.js
166 ms
wp-emoji-release.min.js
82 ms
sbi-styles.min.css
187 ms
style.min.css
284 ms
styles.css
297 ms
style.css
283 ms
theme-lib.js
261 ms
theme-fun.js
231 ms
regenerator-runtime.min.js
231 ms
wp-polyfill.min.js
232 ms
index.js
427 ms
jquery.min.js
427 ms
jquery-migrate.min.js
425 ms
sbi-scripts.min.js
444 ms
lazyload.min.js
445 ms
analytics.js
40 ms
collect
209 ms
GreatVibes-Regular.ttf
631 ms
nexa-light.otf
628 ms
nexa-regular.otf
628 ms
nexa-bold.otf
627 ms
fa-solid-900.woff
628 ms
fa-regular-400.woff
623 ms
fa-brands-400.woff
628 ms
logo.png
72 ms
pattern.jpg
174 ms
bar.png
169 ms
b8.jpg
167 ms
b2.jpg
159 ms
b3.jpg
160 ms
abtpattern.jpg
361 ms
res06.jpg
163 ms
res09.jpg
364 ms
burgericon.png
160 ms
mapbg-1.jpg
322 ms
placeholder.png
151 ms
tr01.png
348 ms
310354432_473755534682984_6482650269458353281_n.webpfull.jpg
82 ms
310121304_495578922426023_6731737087640502660_n.webpfull.jpg
83 ms
310328378_3273391242948668_2094253214925642329_nfull.jpg
98 ms
310168504_620587469622952_2228238612036472187_n.webpfull.jpg
81 ms
309616527_696675181883079_2522855216750931022_n.webpfull.jpg
81 ms
308999317_1757987704546335_3292448448009208790_n.webpfull.jpg
76 ms
309231512_765877234700652_6656915348634749133_n.webpfull.jpg
198 ms
308839213_645957390576799_9013842877926211969_n.webpfull.jpg
144 ms
309112241_818682262497830_7120214583134629257_nfull.jpg
143 ms
308589802_3022717268018342_4503515207425421949_n.webpfull.jpg
141 ms
17275
1546 ms
embed
349 ms
js
54 ms
gen_204
36 ms
init_embed.js
31 ms
common.js
188 ms
util.js
183 ms
map.js
170 ms
overlay.js
24 ms
StaticMapService.GetMapImage
562 ms
onion.js
522 ms
search_impl.js
520 ms
openhand_8_8.cur
186 ms
fixedsizewidget.css
488 ms
local.css
457 ms
17275.css
805 ms
newwidgetlogo3.svg
771 ms
widget-jquery.js
656 ms
warning.svg
651 ms
ViewportInfoService.GetViewportInfo
418 ms
AuthenticationService.Authenticate
51 ms
vt
1745 ms
vt
1711 ms
vt
1713 ms
vt
1716 ms
vt
1714 ms
vt
1712 ms
vt
1715 ms
vt
1716 ms
vt
1721 ms
QuotaService.RecordEvent
57 ms
vt
1673 ms
Setup
1103 ms
newwidgetlogo1.svg
850 ms
349 ms
20006f5fc2784cd0a7c9fcd5ef2c50b1
276 ms
Lato-Regular.ttf
120 ms
glyphicons-halflings-regular.woff
212 ms
OpenSans-Regular.ttf
29 ms
m-outer-e7de605ddb82ddd9dd0b0d0d7c06b7d6.html
16 ms
m-outer-01936564b57cfdef4da595dd64c150b4.js
5 ms
inner.html
43 ms
mintleaf.ae accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
mintleaf.ae best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
mintleaf.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mintleaf.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 Mintleaf.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.
mintleaf.ae
Open Graph data is detected on the main page of Mintleaf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: