Tools & Wizards About Us
neem.ae screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    31% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

neem.ae

Captcha

Page Load Speed

19.5 sec in total

First Response

3.5 sec

Resources Loaded

15.9 sec

Page Rendered

103 ms

neem.ae screenshot

About Website

Click here to check amazing Neem content. Otherwise, check out these important facts you probably never knew about neem.ae

Emirati Restaurant, Neem, Neem Tree Lounge, Chef Musabbeh, Emirati Fusion, Emirati Cuisine, Vintage Land Rover, DIFC Shisha Lounge, Alamin

Visit neem.ae

Key Findings

We analyzed Neem.ae page load time and found that the first response time was 3.5 sec and then it took 16 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

neem.ae performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value21.1 s

0/100

10%

TBT (Total Blocking Time)

Value6,580 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

www.neem.ae

3506 ms

wp-emoji-release.min.js

121 ms

dripicons.min.css

183 ms

elegant-icons.min.css

187 ms

all.min.css

252 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 87% of them (65 requests) were addressed to the original Neem.ae, 8% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Neem.ae.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.1 kB (34%)

Content Size

212.1 kB

After Optimization

139.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Neem.ae main page is 212.1 kB. 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. CSS take 77.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 49.8 kB

  • Original 61.0 kB
  • After minification 60.1 kB
  • After compression 11.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 49.8 kB or 82% of the original size.

JavaScript Optimization

-12%

Potential reduce by 8.6 kB

  • Original 73.9 kB
  • After minification 73.9 kB
  • After compression 65.3 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 8.6 kB or 12% of the original size.

CSS Optimization

-19%

Potential reduce by 14.7 kB

  • Original 77.2 kB
  • After minification 76.8 kB
  • After compression 62.5 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. Neem.ae needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (85%)

Requests Now

66

After Optimization

10

  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Neem. 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 30 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.neem.ae

www.neem.ae

3506 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

121 ms

dripicons.min.css

dripicons.min.css

183 ms

elegant-icons.min.css

elegant-icons.min.css

187 ms

all.min.css

all.min.css

252 ms

ionicons.min.css

ionicons.min.css

191 ms

linea-icons.min.css

linea-icons.min.css

195 ms

linear-icons.min.css

linear-icons.min.css

202 ms

icon

icon

29 ms

simple-line-icons.min.css

simple-line-icons.min.css

241 ms

style.min.css

style.min.css

305 ms

blocks.style.build.css

blocks.style.build.css

256 ms

styles.css

styles.css

256 ms

perfect-scrollbar.css

perfect-scrollbar.css

264 ms

swiper.min.css

swiper.min.css

300 ms

main.min.css

main.min.css

370 ms

drew-core.min.css

drew-core.min.css

399 ms

flatpickr.min.css

flatpickr.min.css

326 ms

jquery.timepicker.min.css

jquery.timepicker.min.css

328 ms

wpc-icon.css

wpc-icon.css

356 ms

wpc-public.css

wpc-public.css

417 ms

css

css

26 ms

style.css

style.css

410 ms

elementor.min.css

elementor.min.css

411 ms

elementor-icons.min.css

elementor-icons.min.css

425 ms

frontend-lite.min.css

frontend-lite.min.css

430 ms

post-5.css

post-5.css

438 ms

global.css

global.css

438 ms

post-244.css

post-244.css

442 ms

css

css

25 ms

jquery.min.js

jquery.min.js

532 ms

jquery-migrate.min.js

jquery-migrate.min.js

481 ms

jquery.multiscroll.css

jquery.multiscroll.css

458 ms

animations.min.css

animations.min.css

459 ms

index.js

index.js

466 ms

index.js

index.js

467 ms

perfect-scrollbar.jquery.min.js

perfect-scrollbar.jquery.min.js

546 ms

hoverIntent.min.js

hoverIntent.min.js

548 ms

core.min.js

core.min.js

549 ms

modernizr.js

modernizr.js

540 ms

jquery.parallax-scroll.js

jquery.parallax-scroll.js

481 ms

main.min.js

main.min.js

427 ms

drew-core.min.js

drew-core.min.js

426 ms

moment.min.js

moment.min.js

433 ms

flatpickr.min.js

flatpickr.min.js

447 ms

jquery.timepicker.min.js

jquery.timepicker.min.js

444 ms

wpc-public.js

wpc-public.js

403 ms

common.js

common.js

415 ms

jquery.waitforimages.js

jquery.waitforimages.js

415 ms

jquery.appear.js

jquery.appear.js

423 ms

swiper.min.js

swiper.min.js

550 ms

effect.min.js

effect.min.js

399 ms

jquery.multiscroll.min.js

jquery.multiscroll.min.js

399 ms

webpack.runtime.min.js

webpack.runtime.min.js

396 ms

frontend-modules.min.js

frontend-modules.min.js

398 ms

waypoints.min.js

waypoints.min.js

381 ms

frontend.min.js

frontend.min.js

362 ms

elementor.min.js

elementor.min.js

352 ms

elementor.js

elementor.js

369 ms

0.0.19.54

0.0.19.54

35 ms

cropped-NEEM-1.png

cropped-NEEM-1.png

274 ms

NEEM.png

NEEM.png

286 ms

p4-img-04.png

p4-img-04.png

316 ms

AR59426-HDR.jpg

AR59426-HDR.jpg

539 ms

AR59238-HDR.jpg

AR59238-HDR.jpg

383 ms

h2-img-10.png

h2-img-10.png

304 ms

cropped-NEEM-300x89.png

cropped-NEEM-300x89.png

333 ms

fullscreen-img.jpg

fullscreen-img.jpg

400 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

31 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

45 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

51 ms

6aey4Ky-Vb8Ew8IfOpc.ttf

6aey4Ky-Vb8Ew8IfOpc.ttf

59 ms

fa-brands-400.woff

fa-brands-400.woff

497 ms

Accessibility Review

neem.ae accessibility score

93

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

neem.ae best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

neem.ae SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neem.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 Neem.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.

Social Sharing Optimization

neem.ae

Open Graph data is detected on the main page of Neem. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: