13.2 sec in total
1.8 sec
9 sec
2.4 sec
Visit ninive.ae now to see the best up-to-date Ninive content and also check out these interesting facts you probably never knew about ninive.ae
Ninive - Modern urban majlis offering an unparalleled blend of Middle Eastern culinary delights in a spectacular hanging garden setting.
Visit ninive.aeWe analyzed Ninive.ae page load time and found that the first response time was 1.8 sec and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ninive.ae performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value17.1 s
0/100
25%
Value27.7 s
0/100
10%
Value2,690 ms
3/100
30%
Value0
100/100
15%
Value56.2 s
0/100
10%
1824 ms
311 ms
567 ms
287 ms
296 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 62% of them (78 requests) were addressed to the original Ninive.ae, 13% (16 requests) were made to Use.fortawesome.com and 4% (5 requests) were made to Sevenrooms.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Paypage.ngenius-payments.com.
Page size can be reduced by 1.8 MB (13%)
14.0 MB
12.2 MB
In fact, the total size of Ninive.ae main page is 14.0 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. 80% 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 9.0 MB which makes up the majority of the site volume.
Potential reduce by 111.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. 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 111.7 kB or 84% 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. Ninive images are well optimized though.
Potential reduce by 1.2 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 1.2 MB or 28% of the original size.
Potential reduce by 507.4 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. Ninive.ae needs all CSS files to be minified and compressed as it can save up to 507.4 kB or 77% of the original size.
Number of requests can be reduced by 86 (75%)
114
28
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ninive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 44 to 1 for CSS and as a result speed up the page load time.
ninive.ae
1824 ms
custom-color-overrides.css
311 ms
style.css
567 ms
custom-frontend.min.css
287 ms
widget-image.min.css
296 ms
fadeIn.min.css
296 ms
custom-pro-widget-nav-menu.min.css
412 ms
custom-widget-icon-list.min.css
320 ms
widget-heading.min.css
380 ms
widget-text-editor.min.css
392 ms
swiper.min.css
490 ms
e-swiper.min.css
421 ms
post-29.css
473 ms
popup.min.css
489 ms
widget-image-carousel.min.css
513 ms
widget-menu-anchor.min.css
523 ms
post-27.css
570 ms
post-2947.css
585 ms
post-253.css
587 ms
post-51.css
615 ms
post-171.css
727 ms
css
39 ms
jquery.min.js
659 ms
jquery-migrate.min.js
663 ms
common-vendors.css
500 ms
common.css
503 ms
feed.css
535 ms
front-app.css
638 ms
post-3297.css
638 ms
widget-form.min.css
645 ms
flatpickr.min.css
644 ms
motion-fx.min.css
642 ms
sticky.min.css
691 ms
responsive-embeds.js
711 ms
jquery.sticky.min.js
711 ms
jquery.smartmenus.min.js
760 ms
runtime.js
758 ms
react.min.js
757 ms
react-dom.min.js
869 ms
common-vendors.js
782 ms
common.js
697 ms
feed.js
947 ms
front-app.js
726 ms
flatpickr.min.js
672 ms
webpack-pro.runtime.min.js
682 ms
webpack.runtime.min.js
733 ms
frontend-modules.min.js
734 ms
hooks.min.js
691 ms
i18n.min.js
677 ms
frontend.min.js
700 ms
core.min.js
729 ms
frontend.min.js
741 ms
elements-handlers.min.js
688 ms
fbevents.js
85 ms
gtm.js
196 ms
ninive
565 ms
544121
356 ms
logo.svg
482 ms
hero.webp
524 ms
Ninive-Bab-Al-Shams-Switcher-button.svg
959 ms
logo_hero.svg
571 ms
Section.svg
587 ms
button_hover.svg
592 ms
home1.webp
595 ms
DSC06534-Enhanced-NR.jpg
660 ms
home3.webp
681 ms
DSC00370-1.jpg
663 ms
DSC00908-1-1.jpg
758 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf
91 ms
0QI6MX1D_JOuGQbT0gvTJPa787wsuxJBkqg.ttf
119 ms
0QI6MX1D_JOuGQbT0gvTJPa787zAvBJBkqg.ttf
162 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqg.ttf
163 ms
DSC03832-1-1.jpg
875 ms
DSC04744-1-1.jpg
728 ms
DSC04845-1-1.jpg
867 ms
DSC05650-1-1.jpg
759 ms
polyfills.js
764 ms
pattern_new2.svg
894 ms
blob.svg
799 ms
DSC06626-Enhanced-NR-1-1.jpg
925 ms
DSC06769-Enhanced-NR-1-1.jpg
1010 ms
DSC06859-Enhanced-NR-1.jpg
815 ms
logo-footer.svg
795 ms
rikas-logo.svg
791 ms
logo-black-1.svg-1.svg
817 ms
ninive_chef_s_selection_pop_up_sunday.png
813 ms
js
85 ms
fonts.f20f9e2844c5782bc737.css
59 ms
js
47 ms
sdk.js
3181 ms
jquery.min.js
97 ms
110 ms
134 ms
production.crypto.f20f9e2844c5782bc737.js
108 ms
dining.js
300 ms
client
118 ms
client:platform.js
109 ms
a2a676c1.js
134 ms
5c2efbbd.js
162 ms
30510c0d.js
183 ms
cb6d04c8.js
185 ms
gtm.js
104 ms
analytics.js
82 ms
collect
30 ms
print.css
96 ms
sdk.js
127 ms
cb=gapi.loaded_0
43 ms
AMIfv96Y4M_dUB1n0myOZJ3s1MeV3XoDp11zjA3u5aRpuQJlr80-SSZtmoynS08oM58DxhhOc3wQaexVxBYtdStjRyN6VjwoT0B8qfVld0tJ1tM7AOd99s0McGpLTNtZROICAf7-nR3c9RSE0xlws1GmDzK-sZikxuM5A8QkB806tpnOrQnahQoysssPclCbUA-97qQaNjDVxCFiMLJSZ_GQizuilKyJ-qRxJP5Zcn04cvII9XQNte7U56VnG0VPAHXf2lrZfMQi760eXYFwY3vLFc0bJaUpk9ecGpKn6BPJetfgl6s0mxMu99aLzFIZRn0zQNg269EjoXmi_-v8_hoLutap7Poe0H-UWCmPS9oWXregf_8gLPC9gbX0ehdVGXjZTyPe6mW_e6IGWJNaL3yz58-p4pqAVrQKeiq9z5-JU9qrodIXzF_GI8wSr7xJ4MCJuOkHbjT0Y2B15DHkTXMYNQiERpGoSLYEaNkD8HTj7ldoXql2ctpLv73SCfmd81aqLABHThmbn4P6hhpwPIypJne4gew-sCf_Ohpfq7wF7mzU_1QQ7qfLrP_t1oZKGBVOohyZEyk-
479 ms
channel.html
37 ms
sdk.js
44 ms
woff.css
188 ms
woff.css
11 ms
woff.css
11 ms
woff.css
78 ms
8AAnjaY2BgYGQAghu7bvGC6McMrTuh9F4ASr4GwQA=
1 ms
woff.css
13 ms
woff.css
11 ms
woff.css
134 ms
wACeNpjYGBgZACCG7tu8YLox8rlu6D0AQBMDAbvAA==
2 ms
woff.css
27 ms
woff.css
9 ms
woff.css
11 ms
OgdD4ATrkHRAA=
0 ms
woff.css
10 ms
woff.css
9 ms
ninive.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
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
Links do not have a discernible name
ninive.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ninive.ae SEO score
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 Ninive.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 Ninive.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.
ninive.ae
Open Graph data is detected on the main page of Ninive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: